Design Handoff
Translate design intent into a buildable contract without duplicating implementation choices that the codebase already owns.
- Capture user goal, hierarchy, layout behavior, semantic components, tokens, assets, and content constraints.
- Specify responsive rules, keyboard/touch behavior, loading/empty/error/permission states, and destructive actions.
- Mark canonical source, decision owner, version, and unresolved questions.
- Write acceptance criteria that can be verified visually and behaviorally.
- Review the implemented result against the contract, not pixel similarity alone.
Do not assume a design file is complete, invent breakpoints, or pass sensitive assets outside the approved scope.