Design Handoff

Create or review a design-to-engineering handoff with intent, responsive behavior, tokens, states, interaction rules, edge cases, assets, acceptance criteria, and open decisions. Use for design handoff, developer handoff, Figma handoff, implementation spec, or UI acceptance criteria. Turkish triggers: tasarımı geliştiriciye devret, ölçü ve durumlar, asset ve acceptance criteria.

yigityildiz0 Updated

File contents

Design Handoff

Translate design intent into a buildable contract without duplicating implementation choices that the codebase already owns.

  1. Capture user goal, hierarchy, layout behavior, semantic components, tokens, assets, and content constraints.
  2. Specify responsive rules, keyboard/touch behavior, loading/empty/error/permission states, and destructive actions.
  3. Mark canonical source, decision owner, version, and unresolved questions.
  4. Write acceptance criteria that can be verified visually and behaviorally.
  5. 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.

yigityildiz0/universal-ai-skill-library/tree/main/skills/common/design-handoff commit fba61a5190

Frequently asked questions

npx skillmds@latest add yigityildiz0/design-handoff