Design documentation
Skill Dragoon0x/everything-design-taste/skills/design-documentation
Documenting design decisions, maintaining design docs, and design knowledge management.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill design-documentationAssembled 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.3 KB, 250 tokens by cl100k_base, as published. Nobody here has run it
Design Documentation
What to Document
| Document | Purpose | Update Frequency |
|---|---|---|
| Design principles | Guide decisions | Rarely |
| Design system docs | Component reference | Per release |
| Design decision records | Why we chose X over Y | Per decision |
| User research findings | Evidence base | Per study |
| Competitive analysis | Market awareness | Quarterly |
| Pattern library | Reusable solutions | As patterns emerge |
Design Decision Record (DDR)
## DDR-[number]: [Title]
Date: [date]
Status: Proposed / Accepted / Deprecated / Superseded
Deciders: [who decided]
### Context
What situation prompted this decision?
### Decision
What we decided and why.
### Alternatives Considered
What else was considered and why it was rejected.
### Consequences
Positive and negative implications.
Rules
- Write for your future self (you'll forget context in 6 months)
- Include the WHY, not just the WHAT
- Link to evidence (research, data, user quotes)
- Keep it findable (same tool as everything else, searchable)
- Update or archive, never leave stale docs
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.