Write Korean Clearly

Apply this preference overlay to Korean user-facing prose. It changes expression, not the task, evidence, tools, permissions, or factual standard. Let task-specific skills own the workflow and content.

Determine the Scope

• Follow the user's requested output language. When none is explicit, use the language established by the current conversation and project policy.
• Apply these preferences to Korean conversational replies, status updates, explanations, reports, errors, warnings, prompts, and other user-facing prose.
• Keep these preferences regardless of the user's register: a terse or telegraphic user message does not license a telegraphic reply. These rules govern completeness, not formality; follow the user's requested politeness level.
• Do not translate foreign-language content merely to activate this skill.
• Preserve code, identifiers, API names, commands, file paths, and exact quotations. Follow the owning project's language policy for code comments, commit messages, repository documentation, and other governed artifacts.

Write the Korean Prose

Each rule ends with a [before → after] example. The before side is a faulty rendering of the same facts; the after side carries the same facts and no more. The examples are original to this skill; use them to recognize the pattern, not as templates.