Igniteui Wc Figma To App

Ignite UI for Web Components — Figma to App

Translate Figma app screens into production Web Components applications built with Ignite UI. The skill accepts designs from three kinds of source. A single file often mixes them, so every component is classified individually (Phase 1f):

Tier A gives the highest fidelity for the least effort. Tiers B and C reach high fidelity through token overrides, and record the remaining anatomy deltas (structural differences between the design's components and Ignite UI's) for the user to approve instead of hiding them.

Web Components ≠ Angular. The kits are shared across frameworks, but the implementation is not: tags are igc-*, components must be registered with defineComponents(...), theming is CSS-custom-property-first (Sass optional), and every component renders in shadow DOM — which changes how you style and how you measure. These differences are called out in each phase.

Required Workflow

Complete all phases in order — do not skip phases or generate component code from memory. Every tag name, attribute, slot, and import path must come from get_doc / get_api_reference results, or from the reference files of the sibling igniteui-wc-choose-components skill — never guessed.

Read references/project-setup.md before Phase 0b (and its layout section in Phase 4). Read references/figma-exploration.md before Phase 1. Read references/design-provenance.md before Phase 1f. Read references/asset-extraction.md before Phase 1h. Read references/figma-component-map.md before Phase 2. Read references/theme-generation.md before Phase 3. Read references/design-token-bridge.md before Phase 3. Read references/validation-patterns.md before Phase 5.

Phase 0 — Prerequisites

Tool naming: this skill writes MCP tool names as <server>_<tool> (e.g. figma_get_metadata, theming_create_theme). The exact name depends on the client — Claude Code exposes them as mcp__<server>__<tool> (e.g. mcp__figma__get_metadata). Match by the tool's base name on whatever server is connected.

0a: Verify All Four MCP Servers

Run these checks silently in parallel. Each verification call is a no-op if the server is not connected; do not surface raw errors to the user at this point.

If any server fails, fix setup for that server only before continuing. For igniteui-cli and igniteui-theming, configure them yourself — run npx -y igniteui-cli ai-config (or ig ai-config) from the project root, which configures both. Add a missing Playwright entry yourself as well. The Figma servers need the user's action — the desktop server is enabled in the Figma desktop app, and the remote server signs in through Figma OAuth — so guide the user through the Figma setup. Full setup instructions for all servers are in references/mcp-setup.md. Newly configured MCP servers require an editor/session reload before their tools appear — ask the user to reload, then stop.

0b: Detect or Scaffold a Web Components Project

Check whether the working directory contains a package.json that lists igniteui-webcomponents, and a src/ entry module.

• Project found: note the package layout (igniteui-webcomponents is MIT; grids, charts, and dock manager come as trial or @infragistics licensed packages), the host setup (plain Lit/vanilla, or a React/Angular/Vue wrapper), and whether Sass is configured (it decides the Phase 3 output format). Confirm the MCP configuration has all four server entries.
• No project found: offer to scaffold one with npx -y igniteui-cli new, or to use an existing project directory, and wait for the user's choice.

Read references/project-setup.md for the detection checklist, the exact messages to show the user, template selection, and the scaffolding steps.

Phase 1 — Figma Design Exploration

Goal: understand the full design structure and capture all data needed for implementation and validation before writing any code.

Read references/figma-exploration.md in full before the first Figma MCP call. It has the call budget, how to tell the two Figma servers apart, exact tool arguments, extraction checklists, and table templates for each step:

Key constraints:

• Rate limits: limits depend on the Figma seat. A View/Collab seat allows 6 calls a month (20 on Starter), which may not cover one artboard. Compare the call estimate with the user's quota before starting, and discover structure with figma_get_metadata first.
• Two Figma MCP servers: the remote server (mcp.figma.com) takes fileKey and nodeId, so you can move between artboards yourself. The desktop server (127.0.0.1:3845) works only on the file open in the Figma desktop app. Pass the node ID from a frame link and check the response, or ask the user to select each artboard and do not batch those calls.
• Any UI kit: do not assume the Indigo.Design kits. Classify each component in 1f. A third-party kit's names, variables, and Code Connect mappings are evidence of the component's role. Never copy them into the code.
• React + Tailwind output: figma_get_design_context returns React + Tailwind code. Read it for information only — never copy it into the project, and never use its asset URLs as final assets.

Phase 2 — Component Discovery (Ignite UI CLI MCP)

Goal: look up exact tags, attributes, slots, events, and registration requirements for every component identified in Phase 1. Never generate component code from memory.

2a: Read the Component Map

Read references/figma-component-map.md in full. For each row of the Phase 1g Table A:

• Tier A: find the Indigo.Design kit name in the kit tables.
• Tier B/C: find the canonical role in the Canonical Role Index, then the row it points to in the named section.

That row gives you the tag, the component class, the package, a get_doc starting point, and the key attributes and slots most often configured from Figma variants.

2b: Fetch Component Docs

Doc names are not tag names (navigation-drawer, text-area, data-grid, overview for combo). Never guess one — see figma-component-map.md § Doc-name rules you will hit immediately.

Call list_components({ framework: "webcomponents" }) once to get the live catalog, then:

• Resolve each component to its exact doc name from that list, and call get_doc({ framework: "webcomponents", name: "<doc-name>" }) — all in a single parallel batch, never sequentially. get_doc gives usage patterns, HTML examples, and slot names.
• For the full property/method/event API, call get_api_reference({ platform: "webcomponents", component: "<ClassName>" }). Use search_api({ platform: "webcomponents", query: "<keyword>" }) first when the exact class name is unknown, and use the section or member parameters to keep responses small.
• get_project_setup_guide({ framework: "webcomponents" }) confirms registration, theme import, and package wiring when needed.

Do not write any component markup until you have read its doc or API entry.

2c: Search for Feature Docs

Use search_docs for feature-level questions raised by the artboard, for example:

search_docs({ framework: "webcomponents", query: "grid row editing" })
search_docs({ framework: "webcomponents", query: "grid virtualization" })
search_docs({ framework: "webcomponents", query: "column pinning" })

Feature docs are mandatory when the artboard shows grid editing, filtering, sorting, pinning, or other advanced feature states.

2d: Document the Final Component Plan

After reading all docs, confirm or revise the Phase 1g table with:

• Exact tags (e.g. <igc-grid>, <igc-navbar>) and component classes
• The package each component comes from, and for the commercial packages (grids, charts, dock manager) whether the project uses the trial or the @infragistics licensed one
• The registration each one needs — see the registration cheat sheet in figma-component-map.md (defineComponents(...), IgcXxxComponent.register(), IgcGridLite.register(), ModuleManager.register(...), and defineComponents from igniteui-dockmanager)
• Any additional theme CSS a package requires (the grid packages ship their own)

Anatomy delta ledger (Tier B and C). For every mapped component whose anatomy differs from the design in a way that tokens, ::part(...), or slotted content cannot close, add a ledger entry:

Do not ledger differences that tokens can close: color, radius, border, casing, height, and spacing are implementation work, not deltas. For every interactive control, prefer the Ignite UI component with a recorded delta over hand-built markup. The component's keyboard, focus, ARIA, and form behavior are worth more than a pixel-exact but inert copy. Approved entries are classified Accepted in Phase 5.

If new packages are required (including an icon package for a third-party kit), identify exact packages and versions, then ask for approval before installing. Present this updated plan, with the ledger, to the user and wait for confirmation before Phase 3.

Phase 3 — Theme Generation (Ignite UI Theming MCP)

Goal: produce theming code that matches the Figma design's visual language, using the kit variables from Phase 1e (Path A) or the color census and measurements from Phase 1d (Path B).

Read references/theme-generation.md and references/design-token-bridge.md in full before running any theming tool. The steps are:

Key constraints:

• Output format: CSS by default; Sass only when the project is configured for it. Never use the Angular-only core() / theme() mixins.
• theming_create_palette takes primary/secondary/surface/gray/success/warn/error/info and variant, while theming_create_theme takes primaryColor/secondaryColor/surfaceColor (no gray).
• theming_create_elevations takes designSystem (material or indigo); there is no preset parameter.
• Never use the font name as the primary design-system signal.
• Never convert Figma pixel values into theming_set_spacing or theming_set_roundness multipliers. --ig-size is different: it is a size step (small / medium / large), not a multiplier. Path A keeps the default; Path B picks the nearest step per component family (3d).
• Path B: seed the palette with the color painted on the component, not the variable named …/500. On a material baseline, buttons, checkboxes, and switches use secondary, so seed it with the button color.

Phase 4 — Implementation

Goal: build the view(s) that match the artboard decomposition from Phase 2.