Agent skill

Figma To Webui

Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines.

BSD-3-ClauseAuto-check passedFrontend & Design

Install Figma To Webui

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .claude/skills/figma-to-webui && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .claude/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .agents/skills/figma-to-webui && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .agents/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .cursor/skills/figma-to-webui && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .cursor/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nwjs/chromium.src.git --path agents/projects/chrome-design-system/skills/figma-to-webui

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .gemini/skills/figma-to-webui && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .gemini/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .github/skills/figma-to-webui && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .github/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nwjs/chromium.src --skill figma-to-webui -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src figma-to-webui --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/projects/chrome-design-system/skills/figma-to-webui .opencode/skills/figma-to-webui && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "figma-to-webui" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-webui into .opencode/skills/figma-to-webui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-webui", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: figma-to-webui
GitHub stars: 160
Token cost: ~1.3k tokens
SKILL.md length: 581 words
Files: 3
Skills in repo: 64
Repo updated: Oct 3, 2026
First seen: Oct 8, 2026
Licence: BSD-3-Clause

At a glance

Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines.

Works in 5 steps: Discovery & Context Retrieval → Design-to-Code Gap Auditing → WebUI Component Implementation → …
Asked to create WebUI code from a Figma frame URL
SKILL.md covers Prerequisites, 1. Discovery & Context Retrieval, 2. Design-to-Code Gap Auditing and 3. WebUI Component…, plus 2 more sections
Reaches figma.com

What it does

Figma To Webui is an agent skill from nwjs/chromium.src. Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md`).

It sits in Frontend & Design. It works with Figma. The repository describes itself as: Chromium codebase with NW.js modifications. Based on https://chromium.googlesource.com/chromium/src.git. The licence is BSD-3-Clause.

When your agent uses it

Asked to create WebUI code from a Figma frame URL

Example prompts

“/figma-to-webui”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Discovery & Context Retrieval
Design-to-Code Gap Auditing
WebUI Component Implementation
Host Page Integration & Theme Support
Report

What it can do on your machine

Read from SKILL.md and the folder at commit a9e8946. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- figma.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Figma To Webui loads about 1.3k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nwjs/chromium.src at commit a9e8946, republished under its BSD-3-Clause licence (© nwjs). 581 words, ~1,256 tokens.

Download SKILL.mdSave it as .claude/skills/figma-to-webui/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: figma-to-webui
description: Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.
metadata.author: Chrome Design System Team

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):

Read the Figma design: Extract information from the Figma design using the figma-context skill.
Reference Existing Component Specs: Map Figma components in the Figma design to Chromium WebUI components using the chrome-components skill.
Reference Token & Font Mapping: Translate Figma variables to equivalent Chromium CSS variables using the chrome-tokens skill.

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

Implement the WebUI code using the webui-code skill.

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.
HTML:
- Strictly mirror the container and node element hierarchy from Figma. 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.
- Implement pure UI templates only. Do NOT add interactive event listeners or handlers (e.g., @click, @change, etc.). Bind properties declaratively to pre-populated mock values without mutation handlers.
- Do NOT add any extra mock elements that are not in the Figma frame.
CSS:
- Typography & Font Fidelity: Carry over all Figma font styles into the WebUI stylesheet.
- Use WebUI Components As-Is: When using existing WebUI components, DO NOT add custom styling to existing components in order to match the Figma specifications. Use the WebUI components as-is.
- Clean Flex Layouts (No Hardcoded Flex-Basis): For elements in Figma
  - With auto-layout fill container (filling the remaining space in a flex row or column), use standard CSS flex shorthand (flex: 1) instead of computing or hardcoding static pixel flex-basis or fixed width. This ensures responsive layouts that cleanly adapt to parent padding, gap, and sibling sizes.
  - With fixed width, use CSS width property instead of flex-basis.
- Strictly Use Figma-to-CSS Token Map: For all Figma variables used in the design, map them to existing Chromium CSS variables using the token mapping catalog. If there is a match, you MUST use it.
Output Location: Save the implementation files inside the ./out/<ComponentName> directory, unless specified otherwise.
Builds: Do not run any builds.

Show full SKILL.md (126 more words)Show less

4. Host Page Integration & Theme Support

Whenever creating or integrating a WebUI component into a host HTML page (e.g. an internal diagnostics page, a feature page, or webui_gallery.html):

Import Color Pipeline Stylesheet: Ensure <link rel="stylesheet" href="chrome://theme/colors.css?sets=ui,chrome"> is included in the host HTML <head> or <body>.
- This connects Chromium's ThemeSource (ui::ColorProvider) to the DOM, defining dynamic Material 3 --color-sys-* variables at runtime for both light and dark mode.
Import Shared Typography & Spacing Stylesheets: Ensure standard shared stylesheets like chrome://resources/css/text_defaults_md.css and chrome://resources/css/md_colors.css are imported if text and focus defaults are required.

5. Report

Create an artifact that summarizes the work performed. Explain rationale for the following:

Any custom CSS added to WebUI components
Use of CSS variables and token mappings
Host HTML integration and theme compatibility

Files

SKILL.md and 2 other files in agents/projects/chrome-design-system/skills/figma-to-webui of nwjs/chromium.src.

SKILL.md
.gitignore
README.md

Open the folder on GitHubat commit a9e8946

Compare with similar skills

Figma To Webui next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Figma To Webui compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Figma To Webui this skillnwjs/chromium.src	160	—	~1.3k	Automated safety check: Pass	BSD-3-Clause	6 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma Design to Codewarpdotdev/warp	65k	4 repos	~2.9k	Automated safety check: Pass	AGPL-3.0	today
Figma Design System Rules Generatorwarpdotdev/warp	65k	3 repos	~4.6k	Automated safety check: Pass	AGPL-3.0	today
Figma Code Connect Componentswarpdotdev/warp	65k	2 repos	~4.2k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
65k GitHub starsUsed in 4 repos~2.9k tokens
Frontend & DesignAuto-check passed
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
65k GitHub starsUsed in 3 repos~4.6k tokens
Frontend & DesignAuto-check passed
Figma Code Connect Components
warpdotdev/warp
Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.
65k GitHub starsUsed in 2 repos~4.2k tokens
Frontend & DesignAuto-check passed
Cc Design
ZeroZ-lab/cc-design
High-fidelity HTML design and prototype creation. An agent skill from ZeroZ-lab/cc-design.
827 GitHub stars~2.2k tokensUpdated 3 mo ago
Frontend & DesignAuto-check: notes

More from nwjs/chromium.src

All 64 skills in this repo

Analyzing SQL Traces
nwjs/chromium.src
Extracts raw trace data from Perfetto traces, runs arbitrary SQL queries for custom follow-up analysis, and applies expert cognitive principles (Tiered Flow Analysis, Semantic Mismatch, Redundancy)…
160 GitHub stars~2.9k tokensUpdated 6 days ago
Auto-check passed
Chrome Performance Optimizer
nwjs/chromium.src
Autonomous multi-agent performance optimization loop for Chromium and V8.
160 GitHub stars~4.2k tokensUpdated 6 days ago
Auto-check passed
Automated Tracing
nwjs/chromium.src
Automated Tracing & Performance Telemetry in Chromium using Perfetto and Telemetry benchmarks.
160 GitHub stars~1.5k tokensUpdated 6 days ago
Auto-check passed
Chrome Releases
nwjs/chromium.src
Queries Chrome commit, version, release, and milestone metadata.
160 GitHub stars~1.3k tokensUpdated 6 days ago
Auto-check passed
Chromium Docs
nwjs/chromium.src
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
160 GitHub stars~1.2k tokensUpdated 6 days ago
Auto-check passed
Gn Deps Debugging
nwjs/chromium.src
Diagnose Chromium GN dependency and include-visibility failures, including BUILD.gn deps/publicdeps, DEPS include rules, private headers, and circular dependencies.
160 GitHub stars~1.5k tokensUpdated 6 days ago
Auto-check passed

Works with

Figma

Questions about Figma To Webui

What does Figma To Webui do?

Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. src. Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines.

When should I use Figma To Webui?

Figma To Webui fits situations like: asked to create WebUI code from a Figma frame URL.

How do I install Figma To Webui in Claude Code?

Run `npx skills add nwjs/chromium.src --skill figma-to-webui -a claude-code`. Or copy the skill folder (agents/projects/chrome-design-system/skills/figma-to-webui in nwjs/chromium.src) into .claude/skills/figma-to-webui in your project. Claude Code loads it when a task matches its description.

How do I install Figma To Webui in Codex?

Run `npx skills add nwjs/chromium.src --skill figma-to-webui -a codex`. Or copy the skill folder (agents/projects/chrome-design-system/skills/figma-to-webui in nwjs/chromium.src) into .agents/skills/figma-to-webui in your project. Codex loads it when a task matches its description.

Can I use Figma To Webui in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nwjs/chromium.src --skill figma-to-webui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/figma-to-webui, .gemini/skills/figma-to-webui, .github/skills/figma-to-webui and .opencode/skills/figma-to-webui in your project.

What does Figma To Webui need to run?

SKILL.md names no scripts, command-line tools or credentials: Figma To Webui is instructions for the agent only.

Does Figma To Webui access the network?

SKILL.md names 1 domain. In commands or code: figma.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Figma To Webui safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Figma To Webui use?

Figma To Webui is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Figma To Webui use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Figma To Webui?

Skills that share tags, products or a category with Figma To Webui: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Figma Design to Code (warpdotdev/warp, 65k stars) and Figma Design System Rules Generator (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Figma To Webui?

nwjs (a GitHub organization) maintains it in nwjs/chromium.src, which has 160 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 3, 2026.

Source: nwjs/chromium.src on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Figma To Webui

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Figma to WebUI: Code Generation

Prerequisites

1. Discovery & Context Retrieval

2. Design-to-Code Gap Auditing

3. WebUI Component Implementation

Guidelines

4. Host Page Integration & Theme Support

5. Report

Files

Compare with similar skills

Similar skills

More from nwjs/chromium.src

Related

Questions about Figma To Webui