# Plan an interface from code and design — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] Existing frontend source with the framework and project design tokens.

- [ ] An authorised design file or exported frames, plus the user task and target devices.

## Output checks

- [ ] Token values are traced to project files rather than copied from a sample palette.

- [ ] Research observations are separated from proposed personas or usability hypotheses.

- [ ] Loading, empty, error and success states have defined behaviour.

- [ ] Keyboard, narrow-screen and relevant theme checks are observed before calling implementation complete.

## Deliverables

- [ ] Code-derived token and component inventory

- [ ] Task-flow brief

- [ ] State and interaction specification

- [ ] Browser acceptance checklist

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- The extraction skill reads frontend source; Figma frames alone are not its documented input. The Copilot UX definition and Figma connection need separate host setup. This pairing is not a tested direct integration.

- Respect design-file permissions and asset licences. Do not overwrite shared designs or claim browser accessibility was tested until it was.

Workflow: https://undominated.ai/workflows/#plan-an-interface