name	term-decision
description	Use when selecting terminology and applying consistent replacements across documentation.
user-invocable	true
disable-model-invocation	true

Terminology Decision

Overview

Decide contested terms, record rationale, apply replacements, and verify consistency.

Core principle: No global replacement without explicit term decision and verification.

The Process

Step 1: Resolve Decision Scope

If $ARGUMENTS exists, focus on that term.
Otherwise collect candidates from:

term_read.py inconsistency output
term_generate.py missing candidates
user-flagged terminology

Create TodoWrite items per term.

Step 2: Prepare Decision Brief

For each term, present:

source term
current variants and usage locations
2-3 candidate translations with short rationale
related conventions from style-decisions.json

Step 3: Ask User Decision (Traditional Chinese)

Collect:

chosen translation
allowed context-specific variants (if any)
rationale note

Step 4: Persist Decision

Record in style-decisions.json and update glossary.json:

uv run python scripts/term_edit.py --term "<TERM>" --set-zh "<ZH>" --status approved --mark-term --notes "<REASON>"

Step 5: Apply and Verify

Preview replacement impact across docs.
Apply approved replacements.
Verify:

uv run python scripts/term_read.py --fail-on-forbidden

Progress Sync Contract (Required)

One TodoWrite item per term decision.
Mark replacement item complete only after verification passes.

When to Stop and Ask for Help

Stop when:

term choice changes mechanics interpretation
user preference conflicts with existing glossary policy
replacement scope is ambiguous

When to Revisit Earlier Steps

Return to Step 2 when:

new conflicting evidence appears
user changes proper noun policy

Red Flags

Never:

apply unapproved term variants globally
skip post-edit glossary validation
skip post-replacement verification

Next Step

After term decisions are stable, continue with /translate or /super-translate.

Example Usage

/term-decision
/term-decision Move
/term-decision "Basic Move"

Más de este repositorio

mismo repositorio

optimized-translating

wayne930242/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

2026-04-107

super-translate

wayne930242/game-doc-template

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

2026-03-297

md-review

wayne930242/game-doc-template

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

2026-03-297

super-translate

wayne930242/game-doc-template

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

2026-03-297

chapter-split

wayne930242/game-doc-template

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.

2026-03-297

final-proofread

wayne930242/game-doc-template

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.

2026-03-107

name	term-decision
description	Use when selecting terminology and applying consistent replacements across documentation.
user-invocable	true
disable-model-invocation	true

Terminology Decision

Overview

Decide contested terms, record rationale, apply replacements, and verify consistency.

Core principle: No global replacement without explicit term decision and verification.

The Process

Step 1: Resolve Decision Scope

If $ARGUMENTS exists, focus on that term.
Otherwise collect candidates from:

term_read.py inconsistency output
term_generate.py missing candidates
user-flagged terminology

Create TodoWrite items per term.

Step 2: Prepare Decision Brief

For each term, present:

source term
current variants and usage locations
2-3 candidate translations with short rationale
related conventions from style-decisions.json

Step 3: Ask User Decision (Traditional Chinese)

Collect:

chosen translation
allowed context-specific variants (if any)
rationale note

Step 4: Persist Decision

Record in style-decisions.json and update glossary.json:

uv run python scripts/term_edit.py --term "<TERM>" --set-zh "<ZH>" --status approved --mark-term --notes "<REASON>"

Step 5: Apply and Verify

Preview replacement impact across docs.
Apply approved replacements.
Verify:

uv run python scripts/term_read.py --fail-on-forbidden

Progress Sync Contract (Required)

One TodoWrite item per term decision.
Mark replacement item complete only after verification passes.

When to Stop and Ask for Help

Stop when:

term choice changes mechanics interpretation
user preference conflicts with existing glossary policy
replacement scope is ambiguous

When to Revisit Earlier Steps

Return to Step 2 when:

new conflicting evidence appears
user changes proper noun policy

Red Flags

Never:

apply unapproved term variants globally
skip post-edit glossary validation
skip post-replacement verification

Next Step

After term decisions are stable, continue with /translate or /super-translate.

Example Usage

/term-decision
/term-decision Move
/term-decision "Basic Move"