Write the blog post and explanatory text in the order of 독자 질문 정의 → 핵심 답 → 근거 정리 → 구조 → 초안 → 문체·구조 검사 .
1. Define the reader's question and the article's promise
- Who reads it and in what situation?
- What answer does the reader most want to know first?
- What should they understand or do after reading?
- Which format is it: informational explanation, practical guide, comparison, or case study?
- What experiences, facts, figures, and sources are available?
Reflect search keywords naturally only when the user requests it. Do not damage titles and sentences just to repeat keywords.
2. Distinguish facts from experience
- Do not write about things you have not experienced as if they were first-person reviews.
- Do not fabricate unverified statistics, quotations, prices, features, or the latest information.
- Research claims that require external evidence and place the source near the claim.
- For comparison articles, compare subjects on the same criteria, and if there are affiliate relationships or conflicts of interest, provide a place to disclose them.
- Do not state inferences and opinions as if they were facts.
Choose the article type from references/formats.md.
3. Write without hiding the answer
Present the core answer or awareness of the problem within the first two paragraphs. 오늘날, 빠르게 변화하는 시대Do not use an introduction that could be attached to any article, such as
- The title contains a promise that the body will actually keep.
- Subheadings contain the reader's next question or the conclusion of the section.
- Use scenes, actions, examples, and figures rather than abstract evaluations.
- Do not make every section the same number of paragraphs and the same format.
- End the conclusion with the reader's criteria for judgment or next action rather than a summary.
references/quality-gate.mdApply , and if a file is needed, assets/blog-template.mduse only as much as necessary.
4. Check style and structure
CORE_SKILL_DIRInterpret as natural-korean, WRITER_SKILL_DIR은 write-natural-koreanin the same parent folder.
uv run "$CORE_SKILL_DIR/scripts/lint.py" path/to/article.md --genre blog
uv run "$CORE_SKILL_DIR/scripts/outline.py" path/to/article.md
uv run "$WRITER_SKILL_DIR/scripts/article_check.py" path/to/article.md
Run only the available check skills. If there is no checker, manually review with a quality gate and disclose that fact. Do not treat the mixing of consistent polite speech and action recommendations as -하세요 as an automatic error.
5. Final delivery
Present the completed version the reader will read first. If there are sources, unverified information, or title candidates for the editor to decide, briefly separate them afterward. Do not leave internal briefs and lint results unless requested.