figma-to-webui

figma-to-webui is a skill for Claude Code, Codex from chromium/chromium. It costs 44 tokens per session (2,067 once invoked), scanned A, original, BSD-3-Clause.

A code-generation workflow that turns a Figma design frame into Chromium WebUI code. WebUI is Chrome's web-based interface layer, built here with Lit elements and CSS.

In plain words
What is it for?
Use it to create production-oriented WebUI code from a Figma frame URL in the Chromium source repository.
Why use it?
It reduces the manual work of converting a visual design into Chrome's web interface structure and styling. It also helps connect the design to existing components and shared design values.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 ui/webui/resources/tools/stylelint.py --config ui/webui/resources/tools/stylelint.config_base.mjs --in_folder <relative_folder_path> --in_files <file_na.

Good fit Use it to create production-oriented WebUI code from a Figma frame URL in the Chromium source repository.

Compare 6 skills from other repositories ↓
About the project

Chromium is an open-source web browser project and the official GitHub mirror of its source code. It is used to build and maintain software for browsing the web, with documentation and code for products such as Chrome and Android WebView.

chromium/chromium · 24,743 stars · on GitHub · chromium.googlesource.com

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/chromium/chromium
agentmods
npx agentmods add skills/chromium/chromium/figma-to-webui

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for figma-to-webui

README.md
[![agentmods](https://agentmods.dev/badge/skills/chromium/chromium/figma-to-webui/github.svg)](https://agentmods.dev/skills/chromium/chromium/figma-to-webui)
Your own site
<a href="https://agentmods.dev/skills/chromium/chromium/figma-to-webui"><img src="https://agentmods.dev/badge/skills/chromium/chromium/figma-to-webui/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for figma-to-webui

Your own site · 80×15
<a href="https://agentmods.dev/skills/chromium/chromium/figma-to-webui"><img src="https://agentmods.dev/badge/skills/chromium/chromium/figma-to-webui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,067 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.02067
Opus 5 $0.00022 $0.01033
Sonnet 5 $0.00009 $0.00413
Haiku 4.5 $0.00004 $0.00207

Measured 9d ago against content hash 9b43eb256f2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

figma-to-webui scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/projects/chrome-design-system/skills/figma-to-webui/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Figma to WebUI: Code Generation

Prerequisites

  • Figma MCP Server: Must be active and configured in the workspace context to fetch designs and metadata.
  • Chromium Repository: This skill should be executed from inside the root directory of the Chromium repository source code (//src/).

If prerequisites are not met, STOP execution and inform the user.


1. Discovery & Context Retrieval

When given a Figma design URL (e.g., https://www.figma.com/design/:fileKey/:fileName?node-id=:nodeId):

  1. Extract Parameters: Extract the fileKey and the nodeId (replace hyphens with colons, e.g. 54800-5491 becomes 54800:5491).
  2. Retrieve Design Context: Call get_design_context with fileKey and nodeId to fetch the metadata, layout hierarchy, layer styles, and a screenshot of the node.
  3. Reference Existing Component Specs: Look up component spec files for relevant components using the project-knowledge skill to map Figma components to Chromium WebUI components.
  4. Reference Token & Font Mapping: Read the Chrome Design System token mapping from the project-knowledge skill to translate Figma variables to equivalent Chromium CSS variables (e.g., desktop/sys/surface-colors/surface-2 to --color-sys-surface2), and translate Figma typography styles to equivalent Chromium font families, sizes, weights, and line heights.

2. Design-to-Code Gap Auditing

Before writing any code, first check if the user already did an audit of this Figma design against production coding standards within the current chat session's recent history (past 5 commands). If not, perform the audit. Incorporate the feedback from this audit into the following code implementation.


3. WebUI Component Implementation

Guidelines

  • Scope: Focus strictly on building the UI. Do not add functionality beyond what is specified in the Figma mockup. If the Figma mockup includes a window frame or top Chrome frame, disregard these.
  • Strictly Follow Element Hierarchy: Strictly mirror the container and node element hierarchy exported from the Figma design context (get_design_context). Ensure outer and inner containers maintain their exact nesting relationships. Exception: if a frame contains only one other frame, these frames can be combined; merge their properties.
  • Pure UI Only (No Event Listeners): Implement pure UI templates only. Do NOT add interactive event listeners or handlers (e.g., @click, @selected-changed, @value-changed, @change, etc.). Bind properties declaratively to pre-populated mock values without mutation handlers.
  • Output Location: Save the implementation files inside the out/ directory (relative to the skill directory), unless specified otherwise.
  • Builds: Do not run any builds.

Read the full file on GitHub · 177 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 177 lines · 44 tokens per session scan A 9b43eb256f2f

Subscribe to this mod's changes

figma-to-webui is a skill published in the GitHub repository chromium/chromium (24,743 stars, last pushed today), licensed BSD-3-Clause. It adds 44 tokens to every session and 2,067 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

reveal-hover-effect

Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…

MengTo/Skills · 66 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens