Agent skill

NAVER Design-To-UI: Figma to Android and iOS Code

NAVER's Design-To-UI plugin turns a Figma screen into Jetpack Compose, XML, SwiftUI or UIKit code through a seven-step pipeline, then checks the build against the original.

Install
/plugin marketplace add https://github.com/naver/design-to-ui.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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

CommandWhat it does
/figma-startClones the dev PR project, creates a design branch, and builds the app
/figma-applyCommits Figma changes to the current branch, repeatable as the design updates
/handoffOpens 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.