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.
Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings.
Install Figma To Views JSON
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nwjs/chromium.src figma-to-views-json --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-views-json .claude/skills/figma-to-views-json && rm -rf skills-srcUse ~/.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/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .claude/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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 install https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-jsonType 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.
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nwjs/chromium.src figma-to-views-json --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-views-json .agents/skills/figma-to-views-json && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .agents/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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.
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nwjs/chromium.src figma-to-views-json --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-views-json .cursor/skills/figma-to-views-json && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .cursor/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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 https://github.com/nwjs/chromium.src.git --path agents/projects/chrome-design-system/skills/figma-to-views-json--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nwjs/chromium.src figma-to-views-json --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-views-json .gemini/skills/figma-to-views-json && rm -rf skills-srcUse ~/.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/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .gemini/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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.
$ gh skill install nwjs/chromium.src figma-to-views-jsonInstalls 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).
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ 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-views-json .github/skills/figma-to-views-json && rm -rf skills-srcUse ~/.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/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .github/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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.
$ npx skills add nwjs/chromium.src --skill figma-to-views-json -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nwjs/chromium.src figma-to-views-json --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-views-json .opencode/skills/figma-to-views-json && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "figma-to-views-json" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/projects/chrome-design-system/skills/figma-to-views-json into .opencode/skills/figma-to-views-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-to-views-json", 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-views-json- GitHub stars
- 160
- Token cost
- ~1k tokens
- SKILL.md length
- 449 words
- Files
- 3
- Skills in repo
- 64
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings.
- Works in 3 steps: Discovery & Context Retrieval → Design-to-Code Gap Auditing → Views Component Implementation
- Asked to create C++ Views Prototype JSON script from a Figma frame URL
- SKILL.md covers Prerequisites, 1. Discovery & Context Retrieval, 2. Design-to-Code Gap Auditing and 3. Views Component…
- Reaches figma.com
What it does
Figma To Views JSON is an agent skill from nwjs/chromium.src. Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings. Use when asked to create C++ Views Prototype JSON script from a Figma frame URL.
Its SKILL.md is about 1k 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 and C++. 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 C++ Views Prototype JSON script from a Figma frame URL
Example prompts
- “/figma-to-views-json”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7b52561. 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 Views JSON loads about 1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 449 words of instructions outside code blocks.
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 7b52561, republished under its BSD-3-Clause licence (© nwjs). 449 words, ~1,013 tokens.
Download SKILL.mdSave it as
.claude/skills/figma-to-views-json/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- figma-to-views-json
- description
- Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings. Use when asked to create C++ Views Prototype JSON script from a Figma frame URL.
Figma to Views JSON: 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/).
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-contextskill. - Reference Existing Component Specs: Look up component spec files for
relevant components using the
chrome-componentsskill to map Figma components to Chromium C++ Views components. - Reference Token Mapping: Consult the Chrome Design System token mapping
using the
chrome-tokensskill to translate the variables from the Figma design (e.g.,desktop/sys/base-colors/base) to equivalent C++ identifiers (ui::kColorSysBase).
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. Views Component Implementation
Implementation Rules
- JSON Schema rules: Read
//ui/views/examples/json_view_builder_schema.msfor the rules about which components/properties are available for use. - Surface & Background Colors: Map Figma variables strictly to their C++
ui::ColorIdequivalents as documented in Chrome Design System token mappings. - Corner Radius Tokens: Do not hardcode arbitrary radius numbers when design system tokens apply. Use CornerRadius as defined in the schema.
- Responsive Layout & Flex Spacing: Use
BoxLayout,BoxLayoutView,FlexLayout,FlexLayoutView,TableLayoutorTableLayoutViewfor structured horizontal and vertical stacking, or fully structured tables.- Apply consistent spacing and padding using standard
InsetsMetric:andSetBetweenChildSpacing(...)andDistanceMetric:values for measurements. - Use
layout_flexpseudo-property on components in horizontal or vertical layouts to distribute space proportionally.
- Apply consistent spacing and padding using standard
- 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.
- Output Location: Save the implementation files inside the
out/
<ComponentName>directory (relative to the skill directory), unless specified otherwise. - Builds: For testing, ensure the views_examples target is built in the
user's preferred
out/<out>directory. Ask the user if multiple are found.- MacOS: When building under MacOS, the views_examples target builds the
Views Examplesapp bundle within theout/<out>directory. To run from the command-line, the executable needs to be referenced within the bundle.
- MacOS: When building under MacOS, the views_examples target builds the
- Test: Launch the built views_examples application using the
--enable-examples="Views Canvas"switch and the--views-canvas-json-fileswitch with the quoted path to the JSON file generated in the previous step above. Be sure to launch the views_examples app onto the same GUI output screen as the one the user is logged in with.
Show full SKILL.md (3 more words)Show less
File 1: <component_name>.json
© nwjs, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in agents/projects/chrome-design-system/skills/figma-to-views-json of nwjs/chromium.src.
- SKILL.md
- .gitignore
- README.md
Open the folder on GitHubat commit 7b52561
Compare with similar skills
Figma To Views JSON 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Figma To Views JSON this skillnwjs/chromium.src | 160 | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design System Rules Generatorwarpdotdev/warp | 65k | 3 repos | ~4.6k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Code Connect Componentswarpdotdev/warp | 65k | 2 repos | ~4.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
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.
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.
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.
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.
Cc Design
ZeroZ-lab/cc-design
High-fidelity HTML design and prototype creation. An agent skill from ZeroZ-lab/cc-design.
More from nwjs/chromium.src
All 64 skills in this repoAnalyzing 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)…
Chrome Performance Optimizer
nwjs/chromium.src
Autonomous multi-agent performance optimization loop for Chromium and V8.
Automated Tracing
nwjs/chromium.src
Automated Tracing & Performance Telemetry in Chromium using Perfetto and Telemetry benchmarks.
Chrome Releases
nwjs/chromium.src
Queries Chrome commit, version, release, and milestone metadata.
Chromium Docs
nwjs/chromium.src
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
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.
Related
Categories
Questions about Figma To Views JSON
What does Figma To Views JSON do?
Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings. src. Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings.
When should I use Figma To Views JSON?
Figma To Views JSON fits situations like: asked to create C++ Views Prototype JSON script from a Figma frame URL.
How do I install Figma To Views JSON in Claude Code?
Run `npx skills add nwjs/chromium.src --skill figma-to-views-json -a claude-code`. Or copy the skill folder (agents/projects/chrome-design-system/skills/figma-to-views-json in nwjs/chromium.src) into .claude/skills/figma-to-views-json in your project. Claude Code loads it when a task matches its description.
How do I install Figma To Views JSON in Codex?
Run `npx skills add nwjs/chromium.src --skill figma-to-views-json -a codex`. Or copy the skill folder (agents/projects/chrome-design-system/skills/figma-to-views-json in nwjs/chromium.src) into .agents/skills/figma-to-views-json in your project. Codex loads it when a task matches its description.
Can I use Figma To Views JSON 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-views-json -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-views-json, .gemini/skills/figma-to-views-json, .github/skills/figma-to-views-json and .opencode/skills/figma-to-views-json in your project.
What does Figma To Views JSON need to run?
SKILL.md names no scripts, command-line tools or credentials: Figma To Views JSON is instructions for the agent only.
Does Figma To Views JSON 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 Views JSON 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 Views JSON use?
Figma To Views JSON 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 Views JSON use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Views JSON?
Skills that share tags, products or a category with Figma To Views JSON: 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 Views JSON?
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 10, 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.