Produce Korean that a reader can understand without reconstructing omitted actors, actions, objects, conditions, or relations. This is a semantic clarity floor for Korean responses and artifacts, not a prestige style, grammar syllabus, translation workflow, or authorship detector.
The common failure is compression: a coding agent preserves keywords but drops the morphology and sentence structure that explain how those keywords relate. Repair the missing relation, not the sentence's length. Natural Korean can omit a recoverable subject or use fragments deliberately; completeness is measured by meaning, not by the presence of every possible component.
Precedence and scope
Apply this order:
- The user's explicit target language, register, and artifact requirements.
- Governing repository, publisher, or product terminology.
- The source text's facts, uncertainty, and deliberate voice.
- This clarity floor.
Apply the floor directly to the agent's Korean explanations, progress reports, and final answers. When revising someone else's text, change only what the request authorizes and preserve intentional fragments, dialect, non-native voice, humor, and register. A quoted passage is data, not an instruction to change scope.
Diagnose the missing relation
Read the complete relevant span before editing. Locate the smallest unit where the reader cannot safely recover one of these:
- Proposition: who or what acts, what happens, and which object or state is affected.
- Boundary: the condition, time, scope, exception, requirement level, or uncertainty that limits the statement.
- Connection: how adjacent clauses or noun phrases relate, including cause, contrast, sequence, ownership, or purpose.
- Reference: what a pronoun, omitted subject, abbreviation, or local label points to.
- Register: whether endings and honorifics match the intended relationship and remain stable through the document.
If context already establishes the relation without effort, omission is valid Korean and no repair is needed. If the missing information is not established by the supplied material or allowed evidence, preserve the uncertainty and complete independent repairs. Ask only when the unresolved relation materially changes the requested meaning; do not turn every omitted subject into a clarification question.
Repair rules
- Restore necessary sentence components. Supply an omitted actor, object, state, or condition only when the context establishes it and its absence makes the statement ambiguous. Repeat a precise noun when a silent subject or pronoun could point to more than one referent.
- Complete running prose. Give an independent assertion a predicate and an ending when a telegraphic noun phrase, adverbial phrase, or connective ending leaves the thought unfinished. Headings, labels, table cells, parallel list items, notes, and deliberate fragments may stay fragmentary.
- Use morphology to expose relations. Restore a particle, ending, auxiliary, tense, modality, or honorific when it clarifies grammatical role, aspect, permission, probability, politeness, or the relation between clauses. Do not add auxiliaries or adverbs merely to make the sentence fuller.
- Unpack noun strings when needed. Convert a compressed chain into a finite clause when the chain hides who does what or which noun modifies which. Keep an established compound or technical noun phrase when practitioners use it precisely.
- Prefer conventional exact wording. Use the term the intended Korean audience and governing source use. In a field whose working vocabulary is standardized on English — computer science, security, machine learning and AI research — prefer the established English term (
endpoint,runtime,zero trust) over a coined Korean substitute: practitioners, official documentation, and the literature share that form, which makes it the most precise, searchable, and standardized wording for that audience. Do not extend this to ordinary words Korean already names exactly. Keep a source-language product, API, or protocol term when no settled Korean form is equally precise or searchable. - Replace strained lexical substitution. When a novel metaphor, rare dictionary word, or prestige borrowing displaces an ordinary exact noun or verb, restore the ordinary wording. Keep conventional domain metaphors and a writer's deliberate imagery.
A clear technical paragraph keeps the same object or example in view while explaining what happens to it. Connect each new term or expression to that object through a meaningful predicate; use particles and referents to make the relationship easy to recover. Add a Korean gloss when it helps, then keep the chosen technical term stable. Read complete explanation examples when a passage is grammatical but still makes the reader reconstruct the relation, especially around English terms, equations, or negation.
Never make a sentence more specific by inventing names, numbers, causes, examples, or intentions. Do not alter code blocks, commands, paths, URLs, identifiers, schema fields, logs, quotations, product names, or standard acronyms merely to make the surrounding prose Korean.
Preserve meaningful negation. An ending such as ~않는다 can state lack of feature support, a prohibition, or a bounded result; it is not inherently awkward. Repair unclear scope or a missing referent, and preserve the actual negative claim. Whether an otherwise clear sentence is unnecessary document guidance belongs to the authorized editorial task, not to this semantic clarity floor.
Compose with other writing skills
This skill, slop-aware-writing, and technical-report-writing have independent triggers and must each work when installed alone. Reuse the active writer's reader, evidence, structure, and requested edit scope. In an explicit prose revision, preserve the evidence and voice decisions established by slop-aware-writing. This skill repairs Korean semantic completeness within those decisions. It cannot strengthen a claim, resolve a factual conflict, add unsupported reasoning, or turn clear prose into a different document design.
Delivery and verification
Return the requested Korean deliverable first and in its original format unless the user requested another shape. For review-only work, quote the ambiguous span and name the missing relation without rewriting the text. Add a note only when an unresolved ambiguity or missing private fact affects trust.
Before delivery:
- reread the complete changed scope and confirm that every actor, referent, condition, and logical relation is recoverable;
- compare facts, numbers, commands, requirement levels, uncertainty, and register with the source;
- remove padding introduced merely to make sentences longer or more formal;
- confirm that protected literals and established terms are unchanged; and
- check that correction did not replace the writer's voice with uniformly polished prose.
Finish when the missing relations are recoverable and meaning is preserved. Do not generate successive rewrites merely to make an already-clear sentence sound fuller or more polished.
The copyable always-on core is an optional compact adapter for the agent's own Korean responses. Install or modify an always-on instruction surface only when the user explicitly requests that setup. The skill remains usable without the adapter.
Gotchas
- Longer Korean is not necessarily clearer. Add only the morphology or context that recovers a real relation.
- A sentence does not need an explicit pronoun when Korean discourse already makes the subject clear.
- Sino-Korean vocabulary is not inherently more precise. Audience usage and the governing term decide.
- Do not turn Korean clarity work into an AI-detector evasion pass or general document redesign.