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.
How to install Figma to Android XML Skill: Convert Designs to Layouts
git clone https://github.com/jahonn/figma-android-xml.gitNo npm, gh or other package manager install is documented; cloning the repository is the only installation route the README gives.Clone the skill
Run git clone https://github.com/jahonn/figma-android-xml.git, then place the cloned contents where your agent platform looks for skills, for example under .claude/skills.
Connect a Figma MCP server
The skill calls out to a Figma MCP server for design data, so one needs to already be connected before you invoke the skill.
Open an Android View-system project
The skill targets classic Android XML resources, not Jetpack Compose, so point it at a project that still uses the View system.
Invoke it with a frame link
Call the skill with a Figma design URL and a target layout name, for example an activity_login.xml-style request.
Check that it loaded
Run the skill against one Figma frame and confirm it writes layout XML plus matching colors and dimens entries, then check that ./gradlew assembleDebug finishes without errors.
Key features
- Resource-first inspectionBefore writing anything, the skill reads the project's current colors, dimens and themes resources and the target SDK, so new output matches existing names.
- Figma MCP dependencyIt pulls layer, variable and spacing data through an already-connected Figma MCP server rather than guessing values from a screenshot.
- Spec report gateA written report maps every color to a color reference and every spacing value to a dimension reference, as a check before code generation starts.
- Sequential generation orderResources, text styles and drawables are generated before layout XML, and layout XML before any Kotlin or ViewBinding code.
- Gradle build validationThe last step runs ./gradlew assembleDebug so a broken layout is caught before it reaches a device or emulator.
- Screenshot comparisonWhere a screenshot tool is available, the skill compares the rendered layout against the source Figma frame and iterates on mismatches.
- 22 documented pitfallsCovers asset format, layout and inset, state handling across ROM variants, Figma access limits, build issues and custom view gaps.
- Image read limitsThe skill caps image reads at roughly two per turn, since the author found that processing 13 or more images in one turn causes API errors.
Frequently asked questions
What is the figma-android-xml skill?
It is a skill that converts a Figma frame into native Android XML: layouts, colors, dimens, themes and minimal Kotlin or ViewBinding glue code. It depends on a connected Figma MCP server for the design data and runs a five-step inspect, pull, spec, generate and validate process.
How do I install the figma-android-xml skill?
Clone the repository with git clone and place the contents where your agent platform looks for skills. The README documents no package manager command, so cloning is the only installation route it gives.
Does figma-android-xml work without a Figma MCP server?
No. The skill's design pull step calls a Figma MCP server for layer, variable and spacing data from the live frame, so one needs to be connected before the skill can run.
Does this skill support Jetpack Compose?
No, it targets the classic Android View system and its XML resources. For Compose and current Material 3 guidance, a separate skill such as the Android Material 3 one covers that side of the platform.
What are the 22 pitfalls it catches?
They cover asset format issues such as SVGs exported as PNG, layout and inset bugs like weight conflicts and edge-to-edge insets, state handling that varies across ROM variants, and build or custom view gaps found converting real Figma frames by hand.
Does it check its own output?
Yes. The last step runs a debug Gradle build and, where a screenshot tool is available, compares the rendered layout against the source Figma frame before calling the task done.
Why does it limit how many images it reads per turn?
The author found that reading 13 or more images in a single turn causes API errors, so the skill caps reads at roughly two images per turn and processes the rest across further turns.


