← ClaudeAtlas

microcopy-tone-auditlisted

Audits UI copy, product microcopy, error messages, and content against a style guide, flagging tone violations, jargon, unhelpful error messages, click-phrased CTAs, and missing accessibility text, then suggesting specific rewrites. Use this skill whenever the user asks to review, audit, or check product copy, UI text, microcopy, error messages, button or CTA text, or UX writing, or asks whether their content matches a style guide or brand voice, even if they don't use the word "audit" explicitly. Also trigger when a user pastes UI copy, a component's text strings, or an error message list and asks for feedback, a review, or a "second pair of eyes." If the user supplies their own style guide (pasted, uploaded, or linked), use it instead of the built-in default described in references/default-style-guide.md.
rsmith155/microcopy-tone-audit · ★ 0 · Web & Frontend · score 52
Install: claude install-skill rsmith155/microcopy-tone-audit
# Microcopy & Tone Audit Reviews product and UI copy against a style guide and produces a structured audit: what violates the guide, why, and a specific suggested rewrite for each flagged item. Works with either the user's own style guide or a sensible built-in default when they don't have one yet. ## When to use this skill Trigger on requests like: - "Can you review this error message copy?" - "Does this match our style guide?" - "Check this button text for tone." - "Audit this onboarding flow's copy." - "Here's our microcopy, what's wrong with it?" - Any pasted block of UI strings, error messages, or button/CTA text followed by a request for feedback, even an informal one like "does this sound right?" Do **not** trigger this skill for requests to *write* new copy from scratch with no existing draft to evaluate — that's a drafting task, not an audit. If the user's own request is ambiguous between "write this for me" and "review what I have," ask which they want, or lean toward audit if they've pasted existing text. ## Step 1: Determine which style guide to use Ask, or infer from context, whether the user has their own style guide: - **If they paste, upload, or link a style guide** — use that exclusively. Do not blend it with the default in `references/default-style-guide.md`. Read their guide fully before auditing anything. - **If they don't have one** — tell them you're using a general-purpose default (don't audit silently against an unstated standard), then read `re