Skip to content
Log in

Design Handoff Spec

Specifies behaviour and states rather than appearance, because developers need the rules and can read the pixels themselves.

0

Share this prompt

Free — no card needed

Create a free account

to open Design Handoff Spec — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryDesignForDesigners, DevelopersTested onClaudeChatGPT

Running it, start to finish

  1. List every state and design the missing ones before handing over.
  2. Specify behaviour for long, empty and extreme content.
  3. Mark which values are exact and which are approximate.

What you get back

The output this produces, every time.

  • Inventories every state and names the ones not designed, which is the main source of handoff friction.
  • Specifies content extremes, since designs are made with pleasant data and break on real data.
  • Says what is flexible and what is exact, so developers neither over-match nor change what mattered.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Design the empty and error states. They are the most-skipped and the most-encountered. A developer who has to invent them will invent them differently.
  • Specify the long-content case. A name three times longer than your sample breaks more layouts than any other single input.
  • Mark what is flexible. Without it developers match pixel values that did not matter and change things that did.

More Design prompts

All Design

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.