Figma to SwiftUI

Deliver native SwiftUI that matches the requested Figma design and fits the existing app. Treat generated web code as design evidence, not as code to port. Preserve the project's architecture, component APIs, and behavior outside the requested change.

Choose the scope

Use the user's request and any brief to establish the target screens, actions, states, and supported devices. A brief defines behavior and scope; Figma defines visuals within that scope. Read source-document.md when a brief needs reconciliation with the design.

• Implement a screen or component: gather the relevant design evidence and project context, then implement through completion.
• Update existing UI: inspect the affected view and dependencies; use adaptation-workflow.md to preserve behavior while closing the visual differences.
• Plan, map tokens, or export assets: deliver that artifact without automatically implementing screens or changing shared design systems.

Resolve routine choices from the codebase and design. Ask when an unresolved choice materially changes scope, behavior, or the target design; continue independent work while it is clarified. A plan or difference checklist is working context, not a mandatory approval gate.

Gather the evidence needed

Use available Figma tools according to their current schemas. Do not assume every server exposes the same tools or parameters.