Handoff Spec

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).

Instructions onlyDesign & Creative
AI-generated overview

Produces developer handoff specifications covering visual, interaction, content, asset, edge-case and implementation details for a design.

What it does
This skill guides the creation of a handoff document that gives developers what they need to implement a design accurately. It structures the document into visual specifications (spacing, color tokens, typography, radius, shadows, breakpoints), interaction specifications (states, transitions, gestures, keyboard behavior), content specifications (character limits, dynamic content, localization, empty/loading/error states), asset delivery, edge cases and implementation notes. The output is a written specification document rather than code or design files.
When to use it
Use it when a design is being handed off to engineering for implementation. It is intended for the point where developers pick up the work and need precise measurements, behaviors, assets, states and edge cases. It is not for verifying a finished implementation or for reusable library component specs.
Requirements
No scripts or tooling are required; it is an instructions-only skill. It needs the design context and details supplied by the user, and it may reference design tokens, asset files or service links if those are provided.

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

Source and attribution

Source:owl-listener/designer-skillsindesign-ops/skills/handoff-specat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal