📋Design Handoff Spec Guide

Guide how to write design specs and units for developer handoff

Principles of Design Handoff Specs

A design handoff is the process of giving developers everything they need to implement the design correctly. Vague specs lead to constant back-and-forth questions and final results that don't match design intent. A good spec is complete enough for developers to implement without needing to ask the designer.

Color tokens, typography, spacing, component states, and responsive breakpoints are the five core categories. Tools like Figma Dev Mode and Zeplin can extract some of this automatically, but they often miss dynamic specs like hover/focus states and animation details.

Token-Based Specs

Defining colors, sizes, and spacing as design tokens allows designers and developers to speak the same language. Names like color-primary-500 and spacing-md survive value changes — the token name stays stable even if the underlying value updates.

Frequently Asked Questions

Should design specs use px or rem?

rem is preferred for accessibility (respects user font preferences). Listing both px and rem is common practice. Align with your team.

What must be in a handoff spec?

Color tokens, typography, spacing, component states (hover/focus/disabled), and responsive breakpoints are essential.

Can I hand off without Figma plugins?

Yes. Figma Inspect panel or Notion/Confluence spec tables work well. Clear documentation matters more than the tool.