# Technical Writing For Designers

> Writing design documentation, component specs, and design decision records for technical audiences.

- Skill: `dragoon0x/technical-writing-for-designers` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dragoon0x/technical-writing-for-designers`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dragoon0x/technical-writing-for-designers/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: dragoon0x (https://skillmd.com/u/dragoon0x)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dragoon0x/technical-writing-for-designers

---


# 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?
```