Connect Figma (One-time setup)
In Figma, go to Settings → Security → Personal Access Tokens → Generate new token and enable:
Any file you have access to in Figma is now available to reference in future sessions.
current_user:readfile_content:readlibrary_asset:readlibrary_content:readfile_dev_resource:read

Share the frame and describe what you need
Open a revolte session in the repo and point at a specific frame rather than an entire file, and describe the implementation constraints up front.
Revolte extracts, builds, and verifies
Revolte reads the Figma frame, maps the design to your codebase, implements the components, then opens the app in a browser to check the result visually.
- Reads the frame — Pulls the component tree, design tokens (colors, spacing, radii), typography, and auto-layout properties straight from the specified frame.
- Maps tokens to your system — Matches Figma colors and spacing to the closest values in your existing design system instead of hardcoding raw pixel values.
- Builds the components — Implements the UI following your project’s existing patterns, reusing shared components wherever the design already matches.
- Checks it in the browser — Starts the app locally, navigates to the new page, and compares it against the Figma frame at multiple viewports.
Continue iterating
Since the session already has context on both the repo and the frame, you can refine with short follow-ups instead of re-explaining the task:
- “Use the existing
Buttoncomponent for all primary actions.” - “Implement the hover and active states from the design.”
- “Add loading and error states to this page.”
- “Match the mobile layout shown in the frame — it collapses to a single column.”
Tips
- Link individual frames instead of whole Figma files — it keeps the context focused.
- Call out components you expect to be reused if your design system has established patterns.
- Include interaction and accessibility requirements in the initial prompt; they’re easy to miss otherwise.