Loading...
Loading...
Found 5 Skills
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
Use only when explicitly asked to write or edit prose. Not for code comments, commit messages, or inline docs.
Use this skill for writing, reviewing, and editing documentation (`/docs` directory or any .md file).
This skill should be used when the user asks to write, edit, review, or improve Markdown content (README, docs, changelog, guides), or needs Markdown formatting, syntax help, or advanced patterns (tables, callouts, task lists, mermaid, details/summary, footnotes).
Rewrite AI-sounding text so it reads like a human domain expert without changing what it says. Use when editing or reviewing prose, documentation, commit messages, PR descriptions, and summaries for AI tells: not-X-but-Y contrasts, copula avoidance ("serves as", "stands as"), forced triads, em dashes everywhere, inflated significance ("pivotal", "testament", "tapestry"), sales puffery, formulaic "challenges and future outlook" conclusions, canned procedural summaries ("refined for clarity and flow", "preserved X while improving Y"), shallow -ing riders, bold-colon listicles, and stock AI vocabulary. Exhaustively based on Wikipedia's "Signs of AI writing" and WikiProject AI Cleanup.