content-design
/content-design
Design clear, consistent product language for navigation, actions, forms, onboarding, empty states, errors, confirmations, permissions, and trust-sensitive moments. Use when words affect comprehension, action, recovery, or confidence.
- Author
- memi-design ↗
- Repository
- design-skills ↗
- Licence
- MIT
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design clear, consistent product language for navigation, actions, forms, onboarding, empty states, errors, confirmations, permissions, and trust-sensitive moments. Use when words affect comprehension, action, recovery, or confidence.
Original author description
Design clear, consistent product language for navigation, actions, forms, onboarding, empty states, errors, confirmations, permissions, and trust-sensitive moments. Use when words affect comprehension, action, recovery, or confidence.
How it works
- Inputs
- Workflow
- Output contract
- Verification
SKILL.md preview
--- name: content-design description: Design clear, consistent product language for navigation, actions, forms, onboarding, empty states, errors, confirmations, permissions, and trust-sensitive moments. Use when words affect comprehension, action, recovery, or confidence. --- # Content Design Treat language as part of the interaction model. Do not polish isolated strings without understanding user intent, system state, consequence, and next action. ## Inputs Gather the user goal, audience knowledge, product terminology, voice principles, interface states, legal constraints, localization needs, character constraints, and evidence from research, support, search, or analytics. ## Workflow 1. **Define the communication job.** State what the user needs to understand or do at this moment and what the system knows. 2. **Establish terminology.** Create one preferred term for each concept, record synonyms and prohibited ambiguity, and align labels across navigation, UI, help, notifications, and support. 3. **Write in action order.** Lead with the information or action needed now. Use specific verbs and concrete objects. Remove throat-clearing and internal system language. 4. **Match copy to state.** Distinguish initial, loading, empty, partial, success, warning, error, blocked, expired, and offline states. 5. **Design actions and consequences.** Button labels should predict the immediate result. Pair destructive or high-trust actions with consequence, scope, and reversibility. 6. **Write recovery.** Explain what happened, what remains safe, what the user can do next, and where responsibility lies. Do not blame the user or expose raw implementation errors. 7. **Handle trust.** Explain permissions, automation, data use, billing, and irreversible changes before commitment. Avoid coercive urgency or disguised consent. 8. **Prepare localization.** Avoid embedded word order, idioms, concatenated fragments, unexplained abbreviations, and layouts that fail under text expansion or RTL. 9. **Test comprehension.** Use cloze tests, first-click tasks, interviews, support review, and production behavior where consequence warrants it. ## Output contract Deliver: - communication objective and audience context; - terminology decisions; - state-by-state copy table; - action and confirmation language; - error and recovery patterns; - localization and accessibility notes; - unresolved legal or policy dependencies. ## Verification Read every string in its real state and sequence. Confirm that labels remain distinct, actions predict outcomes, errors provide recovery, copy does not promise an unconfirmed result, and critical meaning is not carried by color or placement alone. Use `information-architecture` for taxonomy and navigation structure, `interaction-design` for state behavior, and `ai-interaction-design` when language describes generated output, uncertainty, or automation.
Files in this package (3)
- SKILL.md 3 KB
- note.json 1 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · memi-design/design-skills | 90 | MIT |
| mgifford/accessibility-skills | 100 | AGPL-3.0 |
| sukirman1901/frontend-expert | 100 | MIT |
| Carrerajorge/Hola | 100 | MIT |
Database snapshot: 13.11.2026 · package version cf2916fb13e6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100interaction-feedback-and-forms
Use when designing forms and input, validation, error messages, alerts and confirmations, loading, empty and error states, buttons, haptics, toasts, microinteractions or motion, or login and sign-up screens. Do not use for navigation structure (navigation-and-flows), colour and… - 90interaction-design
Design and implement task-oriented interaction flows, forms, navigation and recovery states. Use when improving onboarding, complex workflows or interaction behavior; use design-system for tokens and design-craft for visual composition. - 100studio-ui-patterns
Design system UI patterns for Supabase Studio. Use when building or updating pages, forms, tables, charts, empty states, navigation, cards, alerts, or side panels (sheets). Covers layout selection, component choice, and placement conventions. - 100articulate
Design the words in a product — labels, instructions, errors, confirmations, empty states, onboarding copy, tooltips, voice and tone frameworks, and content models. UX writing and content strategy as a deep discipline. Trigger when writing or reviewing UI copy, error messages,… - 100create-mascot
Create a reusable svgapp.ai mascot for an app, website or brand and generate consistent poses for specific screens (onboarding, empty states, errors, success). Use when the user wants a mascot, a brand character, or the same character in a new pose. - 100ux-writing-content-design
Use when writing, critiquing, or implementing product UX copy, microcopy, labels, CTAs, empty states, onboarding, errors, or notifications.