About superior-copy
A writing skill for producing specific, factual copy that fits a known audience, voice, and purpose. It helps writers improve product and other prose while preserving intentional style and avoiding unsupported claims or generic phrasing.
Key features
- 01Set voice from supplied evidence
- 02Draft around concrete actions and outcomes
- 03Preserve factual accuracy and uncertainty
- 04Remove generic or inflated language
- 05Review copy for clarity and consistency
Use cases
- 01Write product copy for a defined audience
- 02Improve labels, errors, and empty states
- 03Revise prose without erasing its voice
- 04Check copy for unsupported claims
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ kodekateam/ superior-skills --skill superior-copyAfter installing, type/superior-copyin Claude Code to confirm it loaded.
Details
From the project READMESuperior Copy
Write for a known reader doing a real task. Preserve the user's voice and facts; remove patterns that make prose interchangeable without sanding away personality.
Set the voice from evidence
Use supplied examples, existing product copy, audience, channel, and purpose. Identify a few observable traits—such as directness, sentence length, technical depth, humor, or formality—and reproduce them consistently.
Do not “improve” deliberate slang, fragments, punctuation habits, or cultural phrasing merely because they are unconventional. When no voice evidence exists, default to clear, concrete, calm language.
Draft from meaning
- Lead with the fact, action, or user outcome that matters now.
- Name the product object and action instead of relying on abstract nouns.
- Make button labels describe the result: “Send invoice,” not “Continue.”
- Give errors a cause and recoverable next step when known.
- Make empty states explain why the state exists and the one useful way forward.
- Vary rhythm according to meaning; do not force every idea into triplets, slogans, or short dramatic fragments.
Guard factual integrity
- Never invent customers, quotes, numbers, research, awards, compliance, or consensus.
- Attribute claims to a real source or write a narrower factual statement.
- Mark examples as examples. Do not make placeholder identities look like real users.
- Preserve uncertainty where evidence is incomplete; do not fill gaps with plausible detail.
- Avoid guarantees unless the product contract actually guarantees the result.
Remove interchangeable language
Revise phrases that add mood but no information, including vague superlatives, inflated significance, anonymous authority, and generic optimism. Replace them with the concrete capability, constraint, or consequence.
Watch for repeated scaffolds:
- announcing the structure before stating the point;
- “not just X, but Y” used as automatic emphasis;
- synonym cycling to avoid repeating the correct term;
- false ranges such as “from ideas to impact”;
- canned candidness or chatbot sign-offs;
- excessive hedging that hides the actual confidence level.
These are signals, not forbidden strings. Keep a construction when it matches the voice and carries meaning.
Format with restraint
- Use headings and lists only when they improve navigation or comparison.
- Do not bold fragments throughout ordinary prose or decorate headings with unrelated emoji.
- Use quotation marks for actual quotations, terms, or deliberate irony—not synthetic emphasis.
- Keep punctuation natural to the writer. Do not enforce a universal ban on em dashes, parentheses, or fragments.
- Prefer parallel structure when items are genuinely parallel; do not regularize everything into one cadence.
Final pass
Read the copy aloud. Check that every claim is supportable, each CTA predicts its action, repeated phrases are intentional, and the ending contributes information. Compare against the voice evidence, then remove only the patterns that weaken specificity or trust.