SKILL.md
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