| name | copy-sexyness |
| description | Polish product language so it feels clear, human, specific, and non-AI: labels, buttons, empty states, errors, onboarding, settings, tooltips, docs snippets, and microcopy. Use when sexyness requires sharper words, less generic prose, better UX writing, or removal of AI slop from interface text. |
Copy Sexyness
Use this sub-skill when words are part of the product surface.
Standards
- Make copy specific to the user's task and domain.
- Prefer short, concrete labels over clever slogans.
- Put the action in buttons and the consequence in supporting text.
- Make errors explain what happened, why it matters, and what the user can do next.
- Keep tone consistent with the product: calm for tools, playful only where it helps.
- Remove filler, hype, vague adjectives, duplicated explanation, and AI-sounding structure.
- Avoid visible instructions that explain obvious UI mechanics.
Process
- Inventory visible copy in the affected flow.
- Identify the user's state: first use, routine use, error, empty, loading, success, or destructive action.
- Rewrite for clarity, confidence, and brevity.
- Check text in the actual UI for wrapping, truncation, and translation risk.
QA Gate
- Labels and actions are understandable without extra explanation.
- Error and empty states are actionable.
- Copy fits inside its containers at relevant viewport sizes.
- Tone matches the product context.
- No generic AI filler remains in the touched surface.
