Technical writing for designers
Skill Dragoon0x/everything-design-taste/skills/technical-writing-for-designers
Writing design documentation, component specs, and design decision records for technical audiences.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill technical-writing-for-designersAssembled 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, 258 tokens by cl100k_base, as published. Nobody here has run it
Technical Writing for Designers
Component Documentation
## ComponentName
### Purpose
One sentence: what problem this solves.
### When to Use
- Specific scenarios (not 'when appropriate')
### When NOT to Use
- Common misuse cases with alternatives
### Props/API
| Prop | Type | Default | Description |
|------|------|---------|-------------|
| variant | 'primary' \| 'secondary' | 'primary' | Visual style |
| size | 'sm' \| 'md' \| 'lg' | 'md' | Component size |
| disabled | boolean | false | Disables interaction |
### States
- Default, Hover, Active, Focus, Disabled, Loading, Error
### Accessibility
- ARIA role and attributes
- Keyboard behavior
- Screen reader expectations
### Examples
[Code examples for common usage patterns]
Design Decision Records (DDR)
## DDR-001: [Decision Title]
Date: YYYY-MM-DD
Status: Accepted / Proposed / Deprecated
### Context
What situation prompted this decision?
### Decision
What did we decide?
### Alternatives Considered
What else was considered and why was it rejected?
### Consequences
What are the implications of this decision?
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.