Agent skill

Figma to Android XML Skill: Convert Designs to Layouts

The figma-android-xml skill turns a Figma frame into native Android XML layouts, resources and view bindings, catching 22 known conversion pitfalls along the way.

Install
git clone https://github.com/jahonn/figma-android-xml.git
View on GitHub

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

What is the figma-android-xml skill?

figma-android-xml is a skill that reads a Figma frame through the Figma MCP server, then writes Android View-system XML: layouts, colors, dimens and themes. It runs a five-step process of inspecting existing resources, pulling design data, writing a spec report, generating code, then validating with a Gradle build and a screenshot comparison.

figma-android-xml is a skill for coding agents that build native Android apps on the View system rather than Jetpack Compose. It takes a Figma frame link and produces XML layouts, drawables and resource entries that match the design.

It depends on a Figma MCP server already being connected, since it reads design data, metadata and variables from the live frame rather than from a static export.

The five-step process

  • Inspection: it reads the project's existing colors, dimens and themes resources plus the target SDK before writing anything.
  • Design pull: it calls the Figma MCP server for the frame's layers, variables and spacing.
  • Spec report: it writes a report mapping Figma colors to color references and spacing to dimension references, as a check before code.
  • Generation: it writes resources, text styles, drawables and layout XML, then minimal Kotlin or ViewBinding glue code.
  • Validation: it runs a debug Gradle build and compares a screenshot against the Figma frame where that is available.

22 conversion pitfalls it catches

The skill documents 22 failure patterns seen when converting Figma output to Android XML by hand, grouped by asset format, layout and inset, state handling, Figma access, build and custom views.

  • Figma exports a vector shape with a PNG extension; the skill converts it to a VectorDrawable instead of embedding a raster image.
  • A LinearLayout with match_parent and weight=1 together pushes content off screen; the skill uses 0dp with the weight instead.
  • Target SDK 35 slides content under the status bar; the skill adds fitsSystemWindows to the root view.
  • duplicateParentState selector behavior is inconsistent across Android ROM variants; the skill writes an explicit state selector instead.

Who it is for

Best for

  • Teams shipping a native Android app on the classic View system who want a Figma frame turned into real XML.
  • Agents that already have a Figma MCP server connected and need the Android-specific resource and layout rules.
  • Projects that want a build-and-screenshot check before trusting the generated layout.

Not for

  • Projects already built on Jetpack Compose with its modern Material 3 patterns, rather than classic XML views, get a better match from the Android Material 3 skill instead.
  • Generating Tailwind-based color shade palettes for a web project, rather than native Android XML resources, is a different job that the Tailwind Shades MCP server does.
  • Converting one static SVG shape into a drawable without a full Figma frame or layout is a narrower job that SVG to Vector does on its own.
  • Turning a Figma frame into web code such as React or HTML, instead of into Android resources, is the job Figma Implement Design does with that frame.

Use it with UiChemy

This skill writes native Android code, a separate target from a WordPress page. For the web side of the same Figma frame, UiChemy's Figma to WordPress converts it into an editable Elementor or Gutenberg page instead of an app resource. Click Get Started on uichemy.com.