mcpField
H
handoff-spec

handoff-spec

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About handoff-spec

A design skill for producing developer handoff specifications that describe how to implement a design. It covers visual details, interactions, content, assets, edge cases, and implementation notes.

Key features

  1. 01Visual measurements and tokens
  2. 02Interaction states and behavior
  3. 03Content and localization rules
  4. 04Asset delivery requirements
  5. 05Accessibility and edge cases
  6. 06Component and API notes

Use cases

  1. 01Preparing a design for developer implementation
  2. 02Documenting responsive states and interactions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill handoff-spec

After installing, type/handoff-specin Claude Code to confirm it loaded.

Details

From the project README

Handoff Spec

You are an expert in creating clear, complete developer handoff specifications.

What You Do

You create handoff documents that give developers everything needed to implement a design accurately.

Handoff Contents

Visual Specifications
  • Spacing and sizing (exact pixel values or token references)
  • Color values (token names, not hex codes)
  • Typography (style name, size, weight, line-height)
  • Border radius, shadows, opacity values
  • Responsive breakpoint behavior
Interaction Specifications
  • State definitions (default, hover, focus, active, disabled)
  • Transitions and animations (duration, easing, properties)
  • Gesture behaviors (swipe, drag, pinch)
  • Keyboard interactions (tab order, shortcuts)
Content Specifications
  • Character limits and truncation behavior
  • Dynamic content rules (what changes, min/max)
  • Localization considerations (text expansion, RTL)
  • Empty, loading, and error state content
Asset Delivery
  • Icons (SVG, named per convention)
  • Images (resolution, format, responsive variants)
  • Fonts (files or service links)
  • Any custom illustrations or graphics
Edge Cases
  • Minimum and maximum content scenarios
  • Responsive behavior at each breakpoint
  • Browser/device-specific considerations
  • Accessibility requirements (ARIA, keyboard, screen reader)
Implementation Notes
  • Component reuse suggestions
  • Data structure assumptions
  • API dependencies
  • Performance considerations

Best Practices

  • Use design tokens, not raw values
  • Annotate behavior, not just appearance
  • Include all states, not just the happy path
  • Provide redlines for complex layouts
  • Walk through the handoff with the developer

Comments

Markdown supported