# Design Handoff

Generate developer handoff specs from a design.

- Repository: https://github.com/TencentCloud/Octop (11420 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add TencentCloud/Octop --skill design-handoff -g -a claude-code -y`
Codex: `npx skills add TencentCloud/Octop --skill design-handoff -g -a codex -y`
Cursor: `npx skills add TencentCloud/Octop --skill design-handoff -g -a cursor -y`
Gemini CLI: `npx skills add TencentCloud/Octop --skill design-handoff -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /design-handoff

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

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

1. **Don't assume**, If it's not specified, the developer will guess. Specify everything.
2. **Use tokens, not values**, Reference `spacing-md` not `16px`.
3. **Show all states**, Default, hover, active, disabled, loading, error, empty.
4. **Describe the why**, "This collapses on mobile because users primarily use one-handed" helps developers make good judgment calls.

## Output

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

The rest: https://github.com/TencentCloud/Octop/blob/HEAD/src/octop/infra/agents/experts/library/design/skills/design-handoff/SKILL.md