Loading...
Loading...
Found 78 Skills
Use when writing any client-facing content, marketing copy, or communications. Use when AI output sounds generic, corporate, or lacks personality. Triggers on "sounds like AI", "lacks voice", "too generic", or when content could apply to any competitor.
Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
Writing style guide for the Singapore Government Design System (SGDS). Use when writing or reviewing UI copy, documentation, labels, error messages, tooltips, or any content that accompanies SGDS components. Covers tone, grammar, spelling, casing, punctuation, and plain language principles.
Copy and text skill for antislop. Use when writing or editing prose: headlines, tone, CTAs, and anti-AI-writing patterns. Load with the core.
Use when drafting or revising prose longer than one paragraph that will be published or sent under Chris Banes's name.
Make any writing clear, direct, and human. ALWAYS USE IT, before writing any prose in any language, including chat replies, explanations, docs, and summaries.
Create or initialize a durable writing home with VOICE.md, STYLE.md, examples/, and drafts/. Use when Scribe identifies a first-time writer with no established writing context after resolving the target, or when the user explicitly asks to set up, scaffold, initialize, or migrate a self-contained writing folder.
Read this when writing or revising articles. It applies to explanatory texts such as documentation, comments, commit messages, PR descriptions, and articles, as well as reading material such as novels. It is also useful for fixing prose that feels “AI-like” or is difficult to read.
Chinese technical documentation writing standards. Use when writing or revising Chinese technical documents and development docs (README, design docs, API descriptions, tutorials).
Decide whether a new test is needed. Use before writing or requesting tests. Prefer a few tests of observable public behavior over tests of private helpers; preserve required lifecycle and regression coverage.
Write clear, developer-first copy for Zed — leading with facts, grounded in craft.
Audit and improve user-provided writing for clarity, concision, and impact. Use when the user asks to audit, review, improve, edit, or rewrite text. Apply seven checks (sentence length, clutter, unsupported modifiers, weasel words, jargon/acronyms, "so what", and flow), then return severity-ranked findings and a full rewrite suggestion.