Loading...
Loading...
Found 16 Skills
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.
Humanize text: strip AI-isms and add real voice.
Proofread and improve English text written by the user before answering their actual question. Use this skill whenever the user's message contains English sentences or paragraphs — even mixed with Korean — and a substantive answer is expected. Trigger on any message where English prose is present: questions, requests, opinions, descriptions, or explanations written (fully or partly) in English. Do NOT skip proofreading just because the English looks mostly correct; always run the correction block first. Skip only for: single English words, proper nouns, code snippets, or messages written entirely in Korean with no English prose.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.