Markdown File Synchronization Rules

Naming Convention

Each markdown file must include a link to its counterpart at the top:

English version (*.md): Add > 🇯🇵 [日本語版](./filename.ja.md) at the top
Japanese version (*.ja.md): Add > 🇺🇸 [English](./filename.md) at the top

When creating or modifying markdown files, ensure both language versions are kept in sync:

Creating a new file: If you create example.md, also create example.ja.md with Japanese translation
Modifying content: When updating example.md, also update example.ja.md to reflect the same changes
Structural consistency: Both versions must have the same structure (headings, sections, lists)
Cross-language links: Both versions must have links to each other at the top

When creating diagrams, prefer Mermaid over ASCII art / box-drawing characters:

Prefer Mermaid: Use Mermaid syntax for flowcharts, sequence diagrams, class diagrams, etc.
- Renders consistently across platforms
- No alignment issues with different character widths
- Easier to maintain and modify
When to use ASCII art: Only use box-drawing characters when Mermaid cannot express the diagram (e.g., file tree structures)
- Keep text labels in English to maintain alignment
- Add a separate explanation table below for translations

Mermaid example:

flowchart TD
    A[Application Code] --> B[AppContext]
    B --> C[Runtime Interface]
    C --> D[Deno Runtime]
    C --> E[Node.js Runtime]

Translate content naturally, not word-for-word
Keep code blocks, file paths, and technical terms unchanged
Dates: English uses YYYY-MM-DD, Japanese uses YYYY年M月D日
Diagrams: Keep Mermaid diagrams identical in both versions (node labels can be translated if needed). For ASCII art diagrams, keep text in English and provide translations in a separate table below

The following files are excluded from this rule: