agentleFS
nisarthnisarth/claude-skills-store/skills/design/design-handoff/SKILL.md

design-handoff

Skill1 starsChanged 7 months agoMITView on GitHub

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. Trigger phrases: "design handoff", "dev handoff", "spec for engineering", "developer spec", "handoff document", "implementation spec", "design to code", "engineering spec", "component spec", "build spec for this design"

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use design-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document all tokens used, organized by category:

    line 64

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Handoff Spec Generator

Generate comprehensive developer handoff specifications from designs. Cover layout structure, design tokens, component props, interaction states, responsive behavior, edge cases, and animations.

Workflow

Step 1: Identify What Needs Speccing

Clarify the scope:

ScopeWhat to Document
Single componentProps, states, tokens, accessibility
Screen/pageLayout, component composition, data flow, responsive
User flowScreen transitions, state management, error handling
Design system additionNaming, variants, API, usage guidelines

Step 2: Document Layout and Structure

### Layout Specification

**Container**: [Max-width, padding, alignment]
**Grid**: [Columns, gutter, breakpoint behavior]

#### Component Tree

Page +-- Header | +-- Logo | +-- Navigation | +-- UserMenu +-- Main | +-- SectionTitle | +-- CardGrid | | +-- Card (repeated) | | +-- CardImage | | +-- CardTitle | | +-- CardMeta | +-- Pagination +-- Footer


#### Spacing
| Between | Value | Token |
|---------|-------|-------|
| Header and Main | 32px | space-8 |
| Section title and cards | 24px | space-6 |
| Cards (horizontal) | 16px | space-4 |
| Cards (vertical) | 16px | space-4 |

Step 3: Specify Design Tokens

Document all tokens used, organized by category:

  • Colors: Map each usage (background, text, actions, borders) to token names and hex values
  • Typography: Font family, size, weight, and line height for each text level, mapped to tokens
  • Dimensions: Border radius, shadows, input heights, and other dimensional values mapped to tokens

### Step 4: Define Component Props and States

For each component:

Component: [Name]

Props

PropTypeDefaultRequiredDescription
titlestring-YesCard heading text
descriptionstring-NoOptional body text
variant'default''featured''default'NoVisual variant
onClick() => void-NoClick handler
disabledbooleanfalseNoDisabled state

States

StateVisual ChangeTrigger
Default[Description]Initial
HoverBackground darkens, cursor pointerMouse enter
Active/PressedScale 0.98, shadow reducesMouse down
Focus2px ring, offset 2px, color-action-primaryTab focus
DisabledOpacity 0.5, cursor not-alloweddisabled=true
LoadingSkeleton placeholderData fetching
ErrorRed border, error message belowValidation failure
EmptyIllustration + CTANo data

### Step 5: Specify Responsive Behavior

Responsive Breakpoints

BreakpointWidthLayout Change
Mobile< 640pxSingle column, stacked layout
Tablet640-1024pxTwo-column grid
Desktop1024-1280pxThree-column grid
Wide> 1280pxMax-width container, centered

Mobile-Specific Changes

  • Navigation collapses to hamburger menu
  • Cards stack vertically with full width
  • Touch targets minimum 44x44px
  • Font sizes scale down: heading 20px, body 14px

Component Behavior by Breakpoint

ComponentMobileTabletDesktop
CardGrid1 col2 col3 col
NavigationHamburgerHorizontalHorizontal
SidebarHidden, drawerCollapsedVisible

### Step 6: Document Interactions and Animations

Interactions

[Interaction Name]

  • Trigger: [User action]
  • Animation: [Property], [Duration], [Easing]
  • Result: [End state]

Example:

  • Trigger: User clicks "Add to cart" button
  • Animation: Button text cross-fades to checkmark, 200ms, ease-out
  • Result: Button shows "Added" state for 2s, then reverts

Transitions

ElementPropertyDurationEasingTrigger
Card hoverbackground-color150msease-in-outMouse enter
Modal openopacity + transform200msease-outButton click
Modal closeopacity + transform150msease-inClose/escape
ToasttranslateY300msspring(1, 80, 10)Programmatic

### Step 7: Compile the Handoff Document

Design Handoff: [Feature/Page Name]

Designer: [Name] | Date: [Date] | Figma: [Link]

Overview

[1-2 sentences: what this is and what it does]

Layout and Structure

[From Step 2]

Design Tokens

[From Step 3]

Components

[From Step 4]

Responsive Behavior

[From Step 5]

Interactions and Animations

[From Step 6]

Edge Cases, Accessibility, and Open Questions

[Edge cases, a11y requirements, and questions for engineering]


## Examples

### Example 1: New Page
**User**: "Create a handoff spec for this settings page design."
**Response**: Document the page layout, navigation structure, form components with all states, validation behavior, save/cancel flow, responsive breakpoints, and error handling for each settings section.

### Example 2: Component
**User**: "Spec out this new notification component."
**Response**: Define props (type, message, action, dismissable), all visual states (info, success, warning, error), animation (slide-in, auto-dismiss timer), stacking behavior (max 3, queue after), and accessibility (role=alert, aria-live=assertive).

### Example 3: Flow
**User**: "Handoff spec for the checkout flow."
**Response**: Document each step (cart review, shipping, payment, confirmation), transition between steps, validation at each stage, error handling (payment failure, out of stock), loading states during payment processing, and the confirmation/receipt screen.

## Best Practices

1. **Link to the source.** Always include the Figma (or equivalent) link. The spec supplements the design; it does not replace it.
2. **Spec the invisible states.** Loading, empty, error, and disabled states are often missed in mockups but critical for implementation.
3. **Use tokens, not raw values.** Reference design system tokens instead of hex codes and pixel values. This makes the implementation maintainable.
4. **Be explicit about behavior.** "The modal closes" is ambiguous. "The modal fades out over 150ms and focus returns to the trigger button" is implementable.
5. **Include real content examples.** Spec with realistic data: long names, empty fields, truncated text. Specs using "Lorem ipsum" miss layout-breaking edge cases.
6. **Note what is not in the mockup.** If the mockup shows the happy path, explicitly list the states the engineer needs to build that are not designed yet.
7. **Review with engineering before finalizing.** A handoff is a collaboration. Engineers often spot missing specs, impossible interactions, or simpler alternatives.
8. **Version the spec.** When designs change after handoff, update the spec and note what changed so engineers know what to revisit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.