Designer checklist

Use this short check before handing a Figma file to implementation. If a point needs a detailed decision, follow its guide instead of trying to solve the whole specification at once.

Before you start

Choose the area you are handing over:

• a full page with its prepared widths; or
• one clearly marked new section inside an existing product.

Do not add page metadata to an existing product just to make one section checkable. See the team adoption guide for that case.

Page and widths

For a page, check all three points. For a selected section, check its [section=...] root and only the contexts being handed over; do not require page tags or invent missing variants.

• The page, route when known, width, and state are clear from the root.
• The prepared roots describe the same page and preserve the same meaning.
• The same logical element keeps the same name across widths.

See responsive behavior.

Names and relationships

• Important layers use short English names in kebab-case.
• Names do not contain device or width suffixes.
• Related layers are connected by a meaningful parent, not only by visual proximity.

See layer names and design rules.

Links, actions, and states

• Every link has a known [href=...], or a draft [link] backed by an owned open question.
• Every interface change has an [action] and an existing target.
• Important default, loading, empty, error, and success states are shown or described.

See interactions and state reactions.

Content and components

• Text, prices, images, and lists survive realistic data and localization.
• Content, decoration, and exportable assets are distinguishable.
• Components come from the right library and remain editable where they should.

See components and content and overflow.

Handoff test

• A person who did not prepare the file can find the declared page or section, its contexts, actions, targets, and editable resources without a call.

If one answer still lives in chat, add it to the file or record it as an owned open question. In DFC Bridge Assistant, run Check page for a page or Check selected section for the selected section roots. Fix findings and rerun. Keep external dependencies with their owners; a clean source report does not approve the host page or the implementation.

For a stricter review

Use the full review only when the team needs an exhaustive audit of data, accessibility, motion, implementation evidence, and release decisions.