/design-handoff
Generate comprehensive developer handoff documentation from a design.
Usage
/design-handoff $ARGUMENTS
Generate handoff specs for: @$1
If a Figma URL is provided, pull the design from Figma. Otherwise, work from the provided description or screenshot.
What to Include
Visual Specifications
- Exact measurements (padding, margins, widths)
- Design token references (colors, typography, spacing)
- Responsive breakpoints and behavior
- Component variants and states
Interaction Specifications
- Click/tap behavior
- Hover states
- Transitions and animations (duration, easing)
- Gesture support (swipe, pinch, long-press)
Content Specifications
- Character limits
- Truncation behavior
- Empty states
- Loading states
- Error states
Edge Cases
- Minimum/maximum content
- International text (longer strings)
- Slow connections
- Missing data
Accessibility
- Focus order
- ARIA labels and roles
- Keyboard interactions
- Screen reader announcements
Principles
- Don't assume — If it's not specified, the developer will guess. Specify everything.
- Use tokens, not values — Reference
spacing-md not 16px.
- Show all states — Default, hover, active, disabled, loading, error, empty.
- Describe the why — "This collapses on mobile because users primarily use one-handed" helps developers make good judgment calls.
Output
## Handoff Spec: [Feature/Screen Name]
### Overview
[What this screen/feature does, user context]
### Layout
[Grid system, breakpoints, responsive behavior]
### Design Tokens Used
| Token | Value | Usage |
|-------|-------|-------|
| `color-primary` | #[hex] | CTA buttons, links |
| `spacing-md` | [X]px | Between sections |
| `font-heading-lg` | [size/weight/family] | Page title |
### Components
| Component | Variant | Props | Notes |
|-----------|---------|-------|-------|
| [Component] | [Variant] | [Props] | [Special behavior] |
### States and Interactions
| Element | State | Behavior |
|---------|-------|----------|
| [CTA Button] | Hover | [Background darken 10%] |
| [CTA Button] | Loading | [Spinner, disabled] |
| [Form] | Error | [Red border, error message below] |
### Responsive Behavior
| Breakpoint | Changes |
|------------|---------|
| Desktop (>1024px) | [Default layout] |
| Tablet (768-1024px) | [What changes] |
| Mobile (<768px) | [What changes] |
### Edge Cases
- **Empty state**: [What to show when no data]
- **Long text**: [Truncation rules]
- **Loading**: [Skeleton or spinner]
- **Error**: [Error state appearance]
### Animation / Motion
| Element | Trigger | Animation | Duration | Easing |
|---------|---------|-----------|----------|--------|
| [Element] | [Trigger] | [Description] | [ms] | [easing] |
### Accessibility Notes
- [Focus order]
- [ARIA labels needed]
- [Keyboard interactions]
If Connectors Available
If ~~design tool is connected:
- Pull exact measurements, tokens, and component specs from Figma
- Export assets and generate a complete spec sheet
If ~~project tracker is connected:
- Link the handoff to the implementation ticket
- Create sub-tasks for each section of the spec
Tips
- Share the Figma link — I can pull exact measurements, tokens, and component info.
- Mention edge cases — "What happens with 100 items?" helps me spec boundary conditions.
- Specify the tech stack — "We use React + Tailwind" helps me give relevant implementation notes.
1---2name: design-handoff3description: Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.4---56# /design-handoff789Generate comprehensive developer handoff documentation from a design.1011## Usage1213```14/design-handoff $ARGUMENTS15```1617Generate handoff specs for: @$11819If a Figma URL is provided, pull the design from Figma. Otherwise, work from the provided description or screenshot.2021## What to Include2223### Visual Specifications24- Exact measurements (padding, margins, widths)25- Design token references (colors, typography, spacing)26- Responsive breakpoints and behavior27- Component variants and states2829### Interaction Specifications30- Click/tap behavior31- Hover states32- Transitions and animations (duration, easing)33- Gesture support (swipe, pinch, long-press)3435### Content Specifications36- Character limits37- Truncation behavior38- Empty states39- Loading states40- Error states4142### Edge Cases43- Minimum/maximum content44- International text (longer strings)45- Slow connections46- Missing data4748### Accessibility49- Focus order50- ARIA labels and roles51- Keyboard interactions52- Screen reader announcements5354## Principles55561. **Don't assume** — If it's not specified, the developer will guess. Specify everything.572. **Use tokens, not values** — Reference `spacing-md` not `16px`.583. **Show all states** — Default, hover, active, disabled, loading, error, empty.594. **Describe the why** — "This collapses on mobile because users primarily use one-handed" helps developers make good judgment calls.6061## Output6263```markdown64## Handoff Spec: [Feature/Screen Name]6566### Overview67[What this screen/feature does, user context]6869### Layout70[Grid system, breakpoints, responsive behavior]7172### Design Tokens Used73| Token | Value | Usage |74|-------|-------|-------|75| `color-primary` | #[hex] | CTA buttons, links |76| `spacing-md` | [X]px | Between sections |77| `font-heading-lg` | [size/weight/family] | Page title |7879### Components80| Component | Variant | Props | Notes |81|-----------|---------|-------|-------|82| [Component] | [Variant] | [Props] | [Special behavior] |8384### States and Interactions85| Element | State | Behavior |86|---------|-------|----------|87| [CTA Button] | Hover | [Background darken 10%] |88| [CTA Button] | Loading | [Spinner, disabled] |89| [Form] | Error | [Red border, error message below] |9091### Responsive Behavior92| Breakpoint | Changes |93|------------|---------|94| Desktop (>1024px) | [Default layout] |95| Tablet (768-1024px) | [What changes] |96| Mobile (<768px) | [What changes] |9798### Edge Cases99- **Empty state**: [What to show when no data]100- **Long text**: [Truncation rules]101- **Loading**: [Skeleton or spinner]102- **Error**: [Error state appearance]103104### Animation / Motion105| Element | Trigger | Animation | Duration | Easing |106|---------|---------|-----------|----------|--------|107| [Element] | [Trigger] | [Description] | [ms] | [easing] |108109### Accessibility Notes110- [Focus order]111- [ARIA labels needed]112- [Keyboard interactions]113```114115## If Connectors Available116117If **~~design tool** is connected:118- Pull exact measurements, tokens, and component specs from Figma119- Export assets and generate a complete spec sheet120121If **~~project tracker** is connected:122- Link the handoff to the implementation ticket123- Create sub-tasks for each section of the spec124125## Tips1261271. **Share the Figma link** — I can pull exact measurements, tokens, and component info.1282. **Mention edge cases** — "What happens with 100 items?" helps me spec boundary conditions.1293. **Specify the tech stack** — "We use React + Tailwind" helps me give relevant implementation notes.
clawpod-app