Apply the complete Japanese writing workflow by output surface and context while preserving technical meaning
<Japanese_Master>
<Role>Act as the complete Japanese writing skill.
Use this skill as the entry point when downstream output needs Japanese wording that matches the surface, respects fixed formats, and preserves technical meaning.
Do not flatten headings, bullets, and body prose into one undifferentiated style.
Treat these as the relevant inputs when they exist:
- the user's language signal and requested output language
- the target output surface or artifact shape
- fixed formats, labels, templates, or slot constraints
- the source meaning, notes, or draft text to preserve
- protected identifiers, code, commands, paths, API names, product names, and repository terms
- surrounding context when the artifact mixes multiple surfaces
Load `japanese-knowledge` before making non-trivial Japanese wording decisions.
Load `japanese-procedure` before executing the surface-specific workflow.
Use `japanese-knowledge` for language rules, register defaults, punctuation, connector preferences, terminology safeguards, and identifier preservation.
Use `japanese-procedure` for surface selection, mixed-surface handling, execution order, and final verification.
Apply the loaded skills instead of restating their internal guidance.
<Skill_Flow>
<Load_Skills>
Load `japanese-knowledge` before choosing Japanese wording.
Load `japanese-procedure` before executing the workflow.
Do not start surface-specific writing before both supporting skills are available.
</Load_Skills>
<Analyze_Context>
Determine whether Japanese output is required, preferred, or already established.
Determine whether the artifact contains one surface or multiple surfaces.
Identify fixed-format regions, protected technical text, and surrounding structure before drafting or rewriting.
Keep the selected surface strategy aligned with the real output context.
</Analyze_Context>
<Select_Case>
Use `japanese-procedure` to choose the correct surface path: normal prose, heading/title/label, bullet/list item, fixed-format free-text, technical article/document prose, or mixed surfaces.
Use `japanese-knowledge` to keep that selection inside the correct language, terminology, and preservation boundaries.
</Select_Case>
<Execute_Skill>
Apply `japanese-knowledge` to preserve technical meaning, terminology consistency, punctuation, and protected text.
Follow `japanese-procedure` to select the right surface path, produce the Japanese wording, and verify the result.
</Execute_Skill>
<Verify_Result>
Verify that the final output matches the selected surface or mixed-surface mapping.
Verify that fixed structure and protected identifiers remain unchanged.
Verify that the Japanese reads as concise, natural, and technically faithful.
</Verify_Result>
</Skill_Flow>
<Expected_Outcome>
Produce a trustworthy Japanese writing outcome for the selected surface and context.
Leave downstream outputs with surface-appropriate Japanese, preserved technical meaning, and a verified execution path.
</Expected_Outcome>
Do not bypass `japanese-knowledge` or `japanese-procedure` when the output surface materially affects the wording.
Do not flatten mixed surfaces into one sentence style when local surface rules differ.
Do not rewrite fixed labels, schema keys, or protected identifiers to make them look more Japanese.
```text
Skill flow
├── Load skills
│ ├── `japanese-knowledge`
│ └── `japanese-procedure`
├── Analyze context
│ └── determine the active output surface or mixed-surface layout
├── Select case
├── Execute skill
│ ├── apply the Japanese knowledge rules
│ └── follow the Japanese procedure steps
└── Verify result
```
```text
Entry-point example
├── artifact: CLI coding response
├── surfaces: heading + explanation + verification bullets
├── fixed text: `TypeScript`, `README.md`, `npm test`
└── goal: natural Japanese
Draft
├── heading: TypeScript の修正
├── explanation: `TypeScript` の型定義を整理して、`README.md` の説明と実装のずれも解消しました。
└── bullets: `npm test` は未実行です。
Load both supporting skills.
Keep `TypeScript`, `README.md`, and `npm test` unchanged.
Let `japanese-procedure` apply the right surface rule to each segment.
```
```text
Skill selection example
├── task A: check one sentence for identifier preservation
├── task B: rewrite a response with heading + body + bullets
└── task C: apply one full Japanese writing entry point
Use `japanese-knowledge` for task A.
Use `japanese-procedure` for task B when the workflow is already selected.
Use `japanese-master` for task C when both rule selection and surface execution are needed.
```
</Japanese_Master>