What is Design-To-UI?
Design-To-UI is an agent plugin from NAVER with seven skills. The main pipeline reads a Figma screen, classifies assets, maps your project's design tokens, and generates Android or iOS code, while a separate design-qa skill screenshots the built app and diffs it against the Figma original to catch pixel-level mismatches before you ship.
Design-To-UI is a Claude Code plugin, published by NAVER, that turns a Figma screen into native mobile code. It runs a seven-step pipeline: design analysis, asset classification, design system mapping, and platform-specific code generation.
It targets Android through Jetpack Compose or XML layout, and iOS through SwiftUI or UIKit, so the same Figma source can drive either platform depending on which skill you call.
What changes in your workflow
- The figma-asset-download skill pulls SVG and PNG assets through the Figma REST API instead of you exporting them by hand.
- generate-project-design-system reads your existing codebase to build a token mapping, so generated code reuses your real colors and type instead of raw values.
- design-qa captures screens from the built app and overlays or diffs them against the Figma original, flagging pixel-level mismatches.
- figma-diff-apply detects what changed in Figma since the last run and applies only that minimal update to the code.
The branch and handoff commands
| Command | What it does |
|---|---|
| /figma-start | Clones the dev PR project, creates a design branch, and builds the app |
| /figma-apply | Commits Figma changes to the current branch, repeatable as the design updates |
| /handoff | Opens a pull request from the design branch into the dev PR and requests review |
Who it is for
Best for
- Mobile teams converting Figma screens to Compose, XML, SwiftUI or UIKit who want the design system tokens mapped automatically.
- Workflows where a designer keeps iterating in Figma and a developer needs only the changed parts reapplied, not a full rebuild.
- Teams who want an automatic pixel-level check between the shipped screen and the original design.
Not for
- If the target is a web page built from a Figma frame rather than a native mobile screen, Figma Implement Design Skill runs that seven step Figma workflow for code instead.
- When all you need is one Figma icon turned into an Android Vector Drawable XML file rather than a full screen pipeline, the svg2vector MCP server converts that Figma icon to Android XML directly.
- If the question is which Material Design 3 rules an Android screen should follow rather than generating the screen itself, Platform Design Android teaches those Android rules.
- When the iOS code needs an accessibility audit against SwiftUI and UIKit rules rather than a Figma handoff, Swift Accessibility Skill covers that SwiftUI and UIKit audit.
Use it with UiChemy
Design-To-UI targets native Android and iOS apps, not a website. For the same Figma source turned into an editable WordPress page instead, UiChemy Figma to WordPress and Composer cover that path. Click Get Started on uichemy.com.
How to install NAVER Design-To-UI: Figma to Android and iOS Code
/plugin marketplace add https://github.com/naver/design-to-ui.gitWeb and Flutter output are not supported yet; the README lists them as contributions welcome.Add the marketplace
In Claude Code, run
/plugin marketplace add https://github.com/naver/design-to-ui.git, then restart Claude Code as the README instructs.Set up Figma access
Enable MCP in the Figma Desktop app and set a Figma personal access token as the FIGMA_ACCESS_TOKEN environment variable for asset downloads.
Install platform tooling
Install Android Studio for Compose or XML output, Xcode for SwiftUI or UIKit output, and set up Git, npm and your Java environment variables.
Generate your project's token mapping
Run the generate-project-design-system skill once against your codebase before the first design-to-ui run, since there is no universal default mapping.
Check that it loaded
Run /figma-start against a Figma screen and confirm the plugin builds the app and that design-qa reports a close match between the built screen and the Figma original.
Key features
- Seven-step pipelineDesign analysis, asset classification, system mapping and platform-specific code generation run as one connected pipeline rather than separate manual steps.
- Four target code stylesGenerates Jetpack Compose or XML layout for Android, and SwiftUI or UIKit for iOS, from the same Figma source.
- Project-aware token mappinggenerate-project-design-system reads your own codebase first, so generated screens reuse your existing colors, type and components.
- Pixel-level design QAdesign-qa captures the built app's screens and overlays or diffs them against the original Figma frames to catch mismatches.
- Incremental Figma updatesfigma-diff-apply detects what changed since the last run and updates only that part of the code instead of regenerating everything.
- Built-in branch workflowfigma-start, figma-apply and handoff commands manage a design branch and open a pull request without a separate Git workflow to remember.
- Usage logging to DiscussionsThe discussion skill logs real usage experiences to GitHub Discussions with an auto-generated summary for the maintainers.
Frequently asked questions
What is NAVER's Design-To-UI plugin?
It is a Claude Code plugin that converts a Figma screen into native Android or iOS code through a seven-step pipeline, then checks the built app's screens against the original Figma frames with a dedicated design-qa skill.
How do I install Design-To-UI?
Run the plugin marketplace add command the README gives, pointed at the naver/design-to-ui repository, then restart the agent. You also need Figma Desktop with MCP enabled and a Figma personal access token set as FIGMA_ACCESS_TOKEN.
Which platforms does it generate code for?
Android through Jetpack Compose or XML layout, and iOS through SwiftUI or UIKit. The README lists web and Flutter as not supported yet, with contributions welcomed for those two platforms in a future release.
Does it reuse my project's existing design tokens?
Yes, after setup. The generate-project-design-system skill reads your codebase to build a token mapping first, since the README states there is no universal default and each project needs its own mapping.
How does the design QA step work?
The design-qa skill captures screens from the built app and compares them against the original Figma frames through an overlay or diff view, flagging pixel-level mismatches for a developer to fix.
What happens when the Figma design changes after the code is generated?
The figma-diff-apply skill detects what changed since the last run and applies only that minimal update to the code, so a small design tweak does not force a full regeneration.
Does Design-To-UI work with agents other than Claude?
The README documents it specifically as an agent plugin, installed through a plugin marketplace add command, and does not list a separate install path for agents outside that plugin system.


