game-doc-template

Use when translating game content that requires cost-optimized model routing, linear workflow efficiency, and immediate formatting to avoid multi-loop review cycles

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when a markdown draft or docs page must be checked for structural validity and documentation style compliance before writeback or publishing.

Use when high-quality translation is needed with multi-agent review and quality gates before overwriting source files.

Use when extracted rulebook markdown needs to be split into semantic documentation files and navigation. Trigger this skill from `init-doc`, future append/add-document flows, or whenever regenerated `_pages.md` source invalidates the existing chapter map. Do not use this skill for temporary translation chunking; that belongs to a separate draft-only translation workflow.

Use when performing final quality checks before publishing the documentation site. Use when all translation is complete and you need to verify titles/descriptions are translated, check for misplaced or erroneous content, and run page-reference link checks.

Use when translating in bilingual mode — produces Chinese primary + English blockquote markdown. Single-pass, no multi-round review. Requires translation_mode=bilingual in style-decisions.json.

Use when translating one file, one section, or all docs with glossary and style constraints.

Use when initializing a translation project from extraction through glossary, chapter mapping, and progress tracking.

Use when initializing a translation project from extraction through glossary, chapter mapping, and progress tracking.

Use when creating a new translation project from template and preparing repository metadata.

Use when translating one file, one section, or all docs with glossary and style constraints.

Use when creating a new translation project from template and preparing repository metadata.

Use when extracted rulebook markdown needs to be split into semantic documentation files and navigation. Trigger this skill from `init-doc`, future append/add-document flows, or whenever regenerated `_pages.md` source invalidates the existing chapter map. Do not use this skill for temporary translation chunking; that belongs to a separate draft-only translation workflow.

Use when processing PDF rulebooks, extracting raw markdown and image artifacts, or preparing source materials before `chapter-split`, `init-doc`, or translation setup.

Convert page-number references in Markdown documentation into link-based cross references. Use when docs contain patterns such as "第 12 頁", "見 12 頁", "page 12", "pages 12-13", "p. 12", or similar page-based wording that should point to real routes or anchors instead of printed page numbers.

Use when validating translated documentation for missing rule content.

Use when auditing terminology consistency across translated documentation.

Use when selecting terminology and applying consistent replacements across documentation.

Use when creating, editing, validating, or enforcing glossary-driven terminology.

Use when selecting terminology and applying consistent replacements across documentation.

Use when creating, editing, validating, or enforcing glossary-driven terminology.