Practise the standard verbs for handing off a design cleanly to engineering.
0 / 5 completed
1 / 5
Fill in: 'We ___ every reusable element as a Figma component before handoff, so an engineer implementing it can see exactly which variants and states actually exist.'
We 'mark an element' — the standard, simple collocation for designating a piece of a design as a formal component. The other options are less idiomatic here.
2 / 5
Fill in: 'Handing off a design with no annotated spacing or states can ___ an engineer guessing values from pixels instead of building from an actual specification.'
We say an unannotated handoff will 'leave' an engineer guessing values — the standard, natural collocation for the resulting ambiguity. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every interactive state, hover, focus, disabled and error, in the file before handoff, rather than shipping only the single default state a designer happened to draw.'
We 'include a state' — the standard, simple collocation for covering all interactive variations in a design file. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the design tokens in Figma directly to the codebase's variables, so a colour change in one place doesn't require manually hunting down every hard-coded hex value.'
We 'map tokens' — the standard, simple collocation for linking design values to their code equivalents. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the shipped implementation against the original design before calling it done, since a small missed detail is far cheaper to fix before release than after.'
We 'compare an implementation' — the standard, simple collocation for checking built output against the source design. The other options aren't idiomatic here.