korean-writing

Plugin korean-writing from marketplace minjun-skills in minjun0219/skills. Commands read from the repo's manifest — 8 days ago.

Skills (4)

• doc-writing

  Use when writing or restructuring a document or long answer a person will read (README, design doc, ADR, PR description, report, wiki note), or when asked 안 읽혀, 눈에 안 들어와, 문서 정리해줘, 문서 구조 봐줘. Sentence-level Korean style belongs to korean-writing.

• korean-writing

  Use when writing or revising Korean text a person will read — docs, README, site pages, PR bodies, commit messages, review replies, chat explanations — or when asked 한국어 문서 써줘, 번역투 고쳐줘, 한국어 어색해, AI 티 나, 이 문서 다듬어줘, 커밋 메시지 자연스럽게. Product UI, CLI and server strings belong to ux-writing.

• splitting-prs

  Use when deciding how many PRs a change should ship as — while planning a code change, right before opening a PR whose reviewable diff exceeds ~400 lines or mixes concerns, or when asked 이 PR 너무 큰가, PR 쪼개줘, 스택으로 낼까 — and when working an existing GitHub-native stack (adopting base-chained PRs, answer

• ux-writing

  Use when writing or revising Korean user-facing product strings, including a single string added in passing during other code work (an alt text, a CLI message, an error string) — web/app UI copy (buttons, toasts, dialogs, form errors, empty states), CLI/TUI output, server/API messages, i18n catalogs