Refine the Korean document in the order of 설계 → 작성 또는 수정 → 정적 탐지 → 문맥 판단 → 재검사 . Detection results are suspected items, not automatic correction commands.
1. Decide the work mode
- If it is a request for new writing, first decide the reader, purpose, key message, and document genre, then write.
- If it is editing an existing text, preserve facts, figures, proper nouns, quotations, and the tone specified by the user.
- If only diagnosis is requested, do not change the original text and report only findings and improvement priorities.
- Ask about the reader or purpose only when the input is insufficient and the result would vary greatly. Otherwise, infer reasonably from context and proceed.
2. Read the necessary reference materials
- In all work, apply
references/writing-principles.md. - If the meaning of a lint finding or whether to fix it is unclear, read
references/rules.md. - For business, technical, or blog documents, read only the relevant genre in
references/genres.md. - When reviewing issues that are difficult to detect statically, read
references/review-checklist.md. - Only when there is a request to record the user's unique style, copy and write
assets/style-profile-template.md.
3. Design and write
For new writing, internally finalize the following before the body.
- Decide who the reader is.
- Decide what the reader should know or do after reading.
- Write the key message in one sentence.
- Design a title and subheadings that reveal the conclusion.
- Do not create figures, facts, or quotations without evidence.
For existing texts, identify the function of each paragraph and then revise only the parts that have value. Do not flatten every sentence to the same length and sentence pattern.
4. Run static detection
Run the following on the target file. Replace with the absolute path of the directory containing SKILL_DIR은 이 SKILL.md.
uv run "$SKILL_DIR/scripts/lint.py" path/to/document.md --genre business
uv run "$SKILL_DIR/scripts/lint.py" path/to/document.md --genre business --json
Choose the genre from business, tech, blog, general , and the default is general. Save pasted text to a temporary file, inspect it, and delete it after the work.
When quickly checking only the structure:
uv run "$SKILL_DIR/scripts/outline.py" path/to/document.md
When checking the first appearance of English abbreviations and technical term candidates:
uv run "$SKILL_DIR/scripts/terms.py" path/to/document.md
5. Judge and revise
Classify each finding as one of the following.
수정: In context, it is actually unnatural or obscures the meaning.유지: It is an intended expression, proper term, quotation, or a form necessary for the genre.
When revising, follow this order.
- Preserve facts and intent.
- Make the actor and action concrete.
- Reduce unnecessary abstract nouns and translationese.
- Unify the style and level of politeness.
- Make natural changes to sentence length and ending forms, but do not force changes.
6. Recheck and converge
Save the first JSON result and pass it as the baseline after revision.
uv run "$SKILL_DIR/scripts/lint.py" path/to/document.md \
--genre business \
--json > /tmp/natural-korean-before.json
uv run "$SKILL_DIR/scripts/lint.py" path/to/document.md \
--genre business \
--baseline /tmp/natural-korean-before.json
Repeat until there are no new findings and all existing findings have been judged as either revised or retained. Even if lint passes, at the end check the following from the perspective of a first-time reader.
- Can the key point be grasped in the first paragraph?
- Does each paragraph have a role?
- Do the subject and predicate agree naturally?
이것,해당,이를Is it clear what this refers to?- Are facts, assumptions, and opinions distinguished?
7. Deliver the results
Along with the proofreading results, briefly summarize the important reasons for the revisions. If there are findings that were retained, state the reasons for that as well. Since lint is not a guarantee of spelling or a judge of whether text was AI-written, do not create scores or probabilities in that sense.