Content design systems
Skill Dragoon0x/everything-design-taste/skills/content-design-systems
Content design as a system: reusable content patterns, content components, and content governance.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill content-design-systemsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 292 tokens by cl100k_base, as published. Nobody here has run it
Content Design Systems
What It Is
The same way UI components are reusable, content has patterns that should be standardized.
Content Components
| Component | Structure | Example |
|---|---|---|
| Page title | Action + object | 'Manage your team' |
| Section header | Noun or noun phrase | 'Billing history' |
| Empty state | What + why + action | 'No projects yet. Create one to get started.' |
| Confirmation | Action + outcome | 'Payment received. You'll get a receipt by email.' |
| Error | Problem + fix | 'File too large. Maximum size is 10MB.' |
| Tooltip | What this does | 'Sort by most recent first' |
Content Governance
- Glossary: terms and their approved usage
- Capitalization rules: Title Case for page titles, sentence case for everything else
- Number rules: spell out one through nine, numerals for 10+
- Date format: standardize across the product
- Terminology: 'workspace' or 'project'? Pick one. Never both.
Content Review Checklist
- Matches brand voice
- Free of jargon
- Actionable (tells user what to do)
- Specific (no vague language)
- Consistent with existing patterns
- Accessible (plain language, 8th grade reading level)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.