← ClaudeAtlas

korean-polishlisted

This skill should be used when writing, checking, or polishing Korean that goes out under the user's name, so it reads as written by a person: a comment, a reply, a blog post, a description, a message, a doc. Triggers include "답글 써줘", "댓글 달아줘", "블로그 글 써줘", "교정해줘", "다듬어줘", "윤문", "자연스럽게", "AI가 쓴 것 같아?", "이 답글 어때?", "이렇게 올릴까?", and the user pasting a Korean draft to post. Not for Claude's own chat replies to the user.
zeikar/dotfiles · ★ 1 · AI & Automation · score 74
Install: claude install-skill zeikar/dotfiles
# Korean polish Write, check, and polish Korean the user will put out under their own name. The rules are in `rules.md` next to this file; read it first. If the project has its own Korean wording rules (its AGENTS.md or CLAUDE.md names them, e.g. `docs/korean.md`), read those too; where they differ, the project wins. 1. **What kind.** Note what the text is (a comment, a reply, a blog post, a description, a message, a doc). For a reply, read what it answers. 2. **Facts.** Check each factual statement against the project's sources if it has them. For one they don't cover, check what you can (compute it from the sources' numbers) and say how you checked it (computed, from memory); the user decides whether it stays. 3. **Write, or edit lightly.** Writing the text, or revising text Claude wrote in this conversation, apply the rules freely. Given a pasted draft (anything the user supplies, whoever wrote it; it stays a pasted draft after you polish it), change only what a rule, a fact, or a likely misreading calls for, and keep its voice: polish it, don't rewrite it in yours. Content you'd add to a pasted draft (a fact, an example, a familiar name) is a suggestion in the report, not an edit. If nothing needs changing, say so. 4. **Fresh eyes on Claude's text.** Whoever wrote a text judges badly whether it reads as generated. When Claude wrote the text in this conversation, spawn a general-purpose agent with only the text, what it answers,