igniteui-cli 15.8.1 → 15.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (38) hide show
  1. package/package.json +4 -4
  2. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/client-scripts.md +7 -7
  3. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/form-controls.md +65 -18
  4. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/setup.md +1 -1
  5. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/component-mapping.md +5 -5
  6. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/gotchas.md +23 -4
  7. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/references/editing.md +4 -3
  8. package/templates/react/igr-ts/constants.d.ts +1 -1
  9. package/templates/react/igr-ts/constants.js +1 -1
  10. package/templates/webcomponents/igc-ts/constants.d.ts +1 -1
  11. package/templates/webcomponents/igc-ts/constants.js +1 -1
  12. package/templates/webcomponents/igc-ts/projects/_base_with_home/files/package.json +1 -1
  13. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/README.md +15 -15
  14. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/SKILL.md +36 -36
  15. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/reference/mcp-setup.md +8 -6
  16. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/SKILL.md +62 -60
  17. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/references/mcp-setup.md +8 -6
  18. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/SKILL.md +107 -94
  19. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/asset-extraction.md +32 -32
  20. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-provenance.md +32 -30
  21. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-token-bridge.md +84 -71
  22. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-component-map.md +45 -44
  23. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-exploration.md +57 -51
  24. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/mcp-setup.md +23 -23
  25. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/project-setup.md +28 -26
  26. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/theme-generation.md +45 -35
  27. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/validation-patterns.md +38 -29
  28. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/SKILL.md +63 -63
  29. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/component-mapping.md +12 -12
  30. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/gotchas.md +24 -24
  31. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-grids/SKILL.md +23 -23
  32. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/SKILL.md +23 -23
  33. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/angular.md +10 -10
  34. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/react.md +9 -9
  35. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vanilla-js.md +9 -9
  36. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vue.md +11 -11
  37. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-migrate-grid-lite-to-premium/SKILL.md +18 -18
  38. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-optimize-bundle-size/SKILL.md +78 -48
@@ -1,57 +1,68 @@
1
1
  ---
2
2
  license: MIT
3
3
  name: igniteui-wc-figma-to-app
4
- description: "Builds Ignite UI Web Components views from Figma designs, supporting Indigo.Design kits, third-party kits (Material 3, Fluent 2, shadcn/ui, Untitled UI, in-house), and plain frames. Uses the Figma, Ignite UI CLI, Ignite UI Theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design, artboard, or Figma URL with Ignite UI Web Components, including inside React, Angular, or Vue apps. WHEN NOT TO USE: screenshots or mockups without a Figma file (use igniteui-wc-generate-from-image-design), component selection or theme-only changes (use igniteui-wc-choose-components or igniteui-wc-customize-component-theme), or the native Ignite UI for Angular or Blazor packages."
4
+ description: "Builds Ignite UI Web Components views from Figma designs. Supports Indigo.Design kits, third-party kits (Material 3, Fluent 2, shadcn/ui, Untitled UI, in-house), and plain frames. Uses the Figma, Ignite UI CLI, Ignite UI Theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design, artboard, or Figma URL with Ignite UI Web Components, including inside React, Angular, or Vue apps. WHEN NOT TO USE: screenshots or mockups without a Figma file (use igniteui-wc-generate-from-image-design), component selection or theme-only changes (use igniteui-wc-choose-components or igniteui-wc-customize-component-theme), or the native Ignite UI for Angular or Blazor packages."
5
5
  user-invocable: true
6
6
  ---
7
7
 
8
8
  # Ignite UI for Web Components — Figma to App
9
9
 
10
- 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):
10
+ 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 classify every component separately (Phase 1f):
11
11
 
12
12
  | Tier | Source | How it maps to Ignite UI |
13
13
  | --- | --- | --- |
14
14
  | **A** | The Infragistics **Indigo.Design UI Kits** (Material, Fluent, Bootstrap, Indigo variants, light and dark) | Directly, by kit layer name. The kit variant *is* the Ignite UI design system. |
15
- | **B** | Any other component library: public kits such as Material 3, Fluent 2, Bootstrap, shadcn/ui, Untitled UI, or Ant, and in-house design systems | Variant properties are normalized to a canonical role, then mapped. The theme is fitted to a closest baseline design system. |
16
- | **C** | Plain frames, groups, and detached instances | The role is inferred from structure and visuals, with lower confidence, and the user confirms it. |
15
+ | **B** | Any other component library: public kits such as Material 3, Fluent 2, Bootstrap, shadcn/ui, Untitled UI, or Ant, and in-house design systems | The skill normalizes the variant properties to a canonical role, then maps the role. It fits the theme to the closest baseline design system. |
16
+ | **C** | Plain frames, groups, and detached instances | The skill infers the role from structure and visuals, with lower confidence. The user confirms the role. |
17
17
 
18
- 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.
18
+ Tier A gives the highest fidelity for the least effort. For Tiers B and C, token overrides give high fidelity. Do not hide the remaining **anatomy deltas** (structural differences between the design's components and Ignite UI's). Record them for the user to approve.
19
19
 
20
- > **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.
20
+ > **Web Components ≠ Angular.** The frameworks share the kits, but not the implementation. The tags are `igc-*`. You must register components with `defineComponents(...)`. Theming is **CSS-custom-property-first** (Sass is optional). Every component renders in **shadow DOM**, which changes how you style and how you measure. Each phase identifies these differences.
21
21
 
22
22
  ---
23
23
 
24
24
  ## Required Workflow
25
25
 
26
- 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.
26
+ Complete all phases in order. Do not skip phases, and do not generate component code from memory. Take every tag name, attribute, slot, and import path from `get_doc` / `get_api_reference` results. The reference files of the sibling `igniteui-wc-choose-components` skill are also a valid source. Never guess these values.
27
27
 
28
- Read [references/project-setup.md](references/project-setup.md) before Phase 0b (and its layout section in Phase 4). Read [references/figma-exploration.md](references/figma-exploration.md) before Phase 1. Read [references/design-provenance.md](references/design-provenance.md) before Phase 1f. Read [references/asset-extraction.md](references/asset-extraction.md) before Phase 1h. Read [references/figma-component-map.md](references/figma-component-map.md) before Phase 2. Read [references/theme-generation.md](references/theme-generation.md) before Phase 3. Read [references/design-token-bridge.md](references/design-token-bridge.md) before Phase 3. Read [references/validation-patterns.md](references/validation-patterns.md) before Phase 5.
28
+ Read each reference file before the phase that uses it:
29
+
30
+ - [references/project-setup.md](references/project-setup.md): before Phase 0b (and its layout section in Phase 4)
31
+ - [references/figma-exploration.md](references/figma-exploration.md): before Phase 1
32
+ - [references/design-provenance.md](references/design-provenance.md): before Phase 1f
33
+ - [references/asset-extraction.md](references/asset-extraction.md): before Phase 1h
34
+ - [references/figma-component-map.md](references/figma-component-map.md): before Phase 2
35
+ - [references/theme-generation.md](references/theme-generation.md): before Phase 3
36
+ - [references/design-token-bridge.md](references/design-token-bridge.md): before Phase 3
37
+ - [references/validation-patterns.md](references/validation-patterns.md): before Phase 5
29
38
 
30
39
  ---
31
40
 
32
41
  ## Phase 0 — Prerequisites
33
42
 
34
- > **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.
43
+ > **Tool naming:** this skill writes MCP tool names as `<server>_<tool>` (for example, `figma_get_metadata`, `theming_create_theme`). The exact name depends on the client. Claude Code shows them as `mcp__<server>__<tool>` (for example, `mcp__figma__get_metadata`). Find each tool by its base name on the connected server.
35
44
 
36
45
  ### 0a: Verify All Four MCP Servers
37
46
 
38
- 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.
47
+ Run these checks **silently** in parallel. If a server is not connected, its verification call does nothing. Do not show raw errors to the user at this step.
39
48
 
40
49
  | Server | Verification call | Success signal |
41
50
  | --------------------- | --------------------------------------------------- | -------------------------------- |
42
- | **Figma** | Inspect the Figma tools (no call — quotas are small) | Tools listed. The configured server URL (or `fileKey` in the tool schema) tells remote from desktop |
51
+ | **Figma** | Inspect the Figma tools (no call — quotas are small) | The tools are listed. The configured server URL (or `fileKey` in the tool schema) shows if the server is remote or desktop |
43
52
  | **Ignite UI CLI** | `list_components` with `framework: "webcomponents"` | Returns component list |
44
53
  | **Ignite UI Theming** | `theming_detect_platform` | Returns `webcomponents` platform |
45
54
  | **Playwright** | `playwright_browser_navigate` to `about:blank` | Navigates without error |
46
55
 
47
- 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](references/mcp-setup.md). Newly configured MCP servers require an editor/session reload before their tools appear — ask the user to reload, then stop.
56
+ If **any server fails**, fix the setup **for that server only** before you continue. Configure `igniteui-cli` and `igniteui-theming` yourself: run `npx -y igniteui-cli ai-config` (or `ig ai-config`) from the project root. This command configures both servers. Also add a missing Playwright entry yourself.
57
+
58
+ The Figma servers need the user's action, so guide the user through the Figma setup. The user enables the desktop server in the Figma desktop app, and signs in to the remote server through Figma OAuth. [references/mcp-setup.md](references/mcp-setup.md) has the full setup instructions for all servers. The tools of a newly configured MCP server appear only after an editor/session reload. Ask the user to reload, then stop.
48
59
 
49
60
  ### 0b: Detect or Scaffold a Web Components Project
50
61
 
51
62
  Check whether the working directory contains a `package.json` that lists `igniteui-webcomponents`, and a `src/` entry module.
52
63
 
53
- - **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.
54
- - **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.
64
+ - **Project found:** note the package layout. `igniteui-webcomponents` is MIT, and grids, charts, and dock manager come as trial or `@infragistics` licensed packages. Note the host setup (plain Lit/vanilla, or a React/Angular/Vue wrapper). Note whether Sass is configured, because it decides the Phase 3 output format. Make sure that the MCP configuration has all four server entries.
65
+ - **No project found:** offer to scaffold a project with `npx -y igniteui-cli new`, or to use an existing project directory. Wait for the user's choice.
55
66
 
56
67
  Read [references/project-setup.md](references/project-setup.md) for the detection checklist, the exact messages to show the user, template selection, and the scaffolding steps.
57
68
 
@@ -59,33 +70,33 @@ Read [references/project-setup.md](references/project-setup.md) for the detectio
59
70
 
60
71
  ## Phase 1 — Figma Design Exploration
61
72
 
62
- **Goal:** understand the full design structure and capture all data needed for implementation and validation before writing any code.
73
+ **Goal:** understand the full design structure, and capture all data for implementation and validation before you write code.
63
74
 
64
- Read [references/figma-exploration.md](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:
75
+ Read [references/figma-exploration.md](references/figma-exploration.md) in full before the first Figma MCP call. It contains the call budget and how to identify the two Figma servers. It also contains the exact tool arguments, the extraction checklists, and the table templates for each step:
65
76
 
66
77
  | Step | What to do |
67
78
  | ---- | ---------- |
68
- | **1a** | Discover pages and artboards with `figma_get_metadata`. Record each target artboard's width and height — Phase 5 resizes the browser to them |
69
- | **1b** | List the artboards and wait for the user to choose which to implement |
70
- | **1c** | Capture one reference screenshot per artboard — the ground truth for Phase 5 |
71
- | **1d** | Extract design context per artboard: layers and variant props, layout, typography, surfaces, input variants, chart colors, color census, control heights, action controls, provenance signals |
79
+ | **1a** | Find the pages and artboards with `figma_get_metadata`. Record the width and height of each target artboard. Phase 5 resizes the browser to these dimensions |
80
+ | **1b** | List the artboards. Wait for the user to choose the artboards to implement |
81
+ | **1c** | Capture one reference screenshot for each artboard. The screenshots are the ground truth for Phase 5 |
82
+ | **1d** | Extract the design context for each artboard: layers and variant props, layout, typography, surfaces, input variants, chart colors, color census, control heights, action controls, provenance signals |
72
83
  | **1e** | Extract design tokens with `figma_get_variable_defs`, once per target page |
73
- | **1f** | Classify every component's provenance (Tier A Indigo.Design kit / B other library / C plain frames) and normalize it to a canonical role; check Code Connect mappings |
74
- | **1g** | Build Table A (Ignite UI components, with tier, confidence, token work, and suspected anatomy deltas) and Table B (layout surfaces), then present both for review — low-confidence mappings first |
75
- | **1h** | Extract every image asset to the project's assets directory — zero-placeholder policy |
84
+ | **1f** | Classify the provenance of every component (Tier A Indigo.Design kit / B other library / C plain frames). Normalize it to a canonical role. Check the Code Connect mappings |
85
+ | **1g** | Build Table A (Ignite UI components, with tier, confidence, token work, and suspected anatomy deltas) and Table B (layout surfaces). Show both tables to the user for review, with low-confidence mappings first |
86
+ | **1h** | Extract every image asset to the assets directory of the project (zero-placeholder policy) |
76
87
 
77
88
  Key constraints:
78
89
 
79
- - **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.
80
- - **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.
90
+ - **Rate limits:** the limits depend on the Figma **seat**. A View/Collab seat allows 6 calls a month (20 on Starter). This quota possibly does not cover one artboard. Before you start, compare the call estimate with the user's quota. Use `figma_get_metadata` first to find the structure.
91
+ - **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 that is open in the Figma desktop app. With the desktop server, pass the node ID from a frame link and check the response. Alternatively, ask the user to select each artboard, and do not batch those calls.
81
92
  - **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.
82
- - **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.
93
+ - **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.
83
94
 
84
95
  ---
85
96
 
86
97
  ## Phase 2 — Component Discovery (Ignite UI CLI MCP)
87
98
 
88
- **Goal:** look up exact tags, attributes, slots, events, and registration requirements for every component identified in Phase 1. Never generate component code from memory.
99
+ **Goal:** find the exact tags, attributes, slots, events, and registration requirements for every component from Phase 1. Never generate component code from memory.
89
100
 
90
101
  ### 2a: Read the Component Map
91
102
 
@@ -94,23 +105,23 @@ Read [references/figma-component-map.md](references/figma-component-map.md) in f
94
105
  - **Tier A:** find the Indigo.Design kit name in the kit tables.
95
106
  - **Tier B/C:** find the canonical role in the **Canonical Role Index**, then the row it points to in the named section.
96
107
 
97
- 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.
108
+ That row gives the tag, the component class, the package, and a `get_doc` starting point. It also gives the key attributes and slots that you set most frequently from Figma variants.
98
109
 
99
110
  ### 2b: Fetch Component Docs
100
111
 
101
- > **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`.
112
+ > **Doc names are not tag names** (`navigation-drawer`, `text-area`, `data-grid`, `overview` for combo). Never guess a doc name. See `figma-component-map.md § Doc-name rules you will hit immediately`.
102
113
 
103
114
  Call `list_components({ framework: "webcomponents" })` **once** to get the live catalog, then:
104
115
 
105
- - 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.
106
- - 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.
107
- - `get_project_setup_guide({ framework: "webcomponents" })` confirms registration, theme import, and package wiring when needed.
116
+ - Find the exact doc `name` of each component in that list. Then call `get_doc({ framework: "webcomponents", name: "<doc-name>" })` for all components in a single parallel batch. Never make these calls sequentially. `get_doc` gives usage patterns, HTML examples, and slot names.
117
+ - For the full property/method/event API, call `get_api_reference({ platform: "webcomponents", component: "<ClassName>" })`. If you do not know the exact class name, use `search_api({ platform: "webcomponents", query: "<keyword>" })` first. Use the `section` or `member` parameters to keep the responses small.
118
+ - When necessary, use `get_project_setup_guide({ framework: "webcomponents" })` to confirm registration, theme import, and package wiring.
108
119
 
109
120
  Do **not** write any component markup until you have read its doc or API entry.
110
121
 
111
122
  ### 2c: Search for Feature Docs
112
123
 
113
- Use `search_docs` for feature-level questions raised by the artboard, for example:
124
+ Use `search_docs` for feature-level questions about the artboard, for example:
114
125
 
115
126
  ```
116
127
  search_docs({ framework: "webcomponents", query: "grid row editing" })
@@ -122,14 +133,14 @@ Feature docs are mandatory when the artboard shows grid editing, filtering, sort
122
133
 
123
134
  ### 2d: Document the Final Component Plan
124
135
 
125
- After reading all docs, confirm or revise the Phase 1g table with:
136
+ After you read all docs, confirm or revise the Phase 1g table with:
126
137
 
127
- - Exact tags (e.g. `<igc-grid>`, `<igc-navbar>`) and component classes
128
- - 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
129
- - 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`)
130
- - Any additional theme CSS a package requires (the grid packages ship their own)
138
+ - Exact tags (for example, `<igc-grid>`, `<igc-navbar>`) and component classes
139
+ - The **package** of each component. For the commercial packages (grids, charts, dock manager), record whether the project uses the trial package or the `@infragistics` licensed package
140
+ - The **registration** that each component needs. See the registration cheat sheet in `figma-component-map.md` (`defineComponents(...)`, `IgcXxxComponent.register()`, `IgcGridLite.register()`, `ModuleManager.register(...)`, and `defineComponents` from `igniteui-dockmanager`)
141
+ - Any additional theme CSS that a package requires (the grid packages have their own theme CSS)
131
142
 
132
- **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:
143
+ **Anatomy delta ledger (Tier B and C).** The anatomy of some mapped components differs from the design. If tokens, `::part(...)`, or slotted content **cannot** close the difference, add a ledger entry:
133
144
 
134
145
  | Component | Design shows | Ignite UI renders | Options | Decision |
135
146
  | --- | --- | --- | --- | --- |
@@ -137,34 +148,34 @@ After reading all docs, confirm or revise the Phase 1g table with:
137
148
  | _e.g._ M3 segmented button | Check icon on the selected segment | `igc-toggle-button`, no check icon | Slot an `igc-icon` in the selected item / accept | ask |
138
149
  | _e.g._ Bottom sheet | Sheet sliding from the bottom | No sheet component | `igc-dialog` styled / custom markup | ask |
139
150
 
140
- 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.
151
+ Do not add ledger entries for differences that tokens *can* close. Color, radius, border, casing, height, and spacing are implementation work, not deltas. For every interactive control, the Ignite UI component with a recorded delta is better than hand-built markup. The keyboard, focus, ARIA, and form behavior of the component are more important than a pixel-exact but inert copy. Phase 5 classifies approved entries as **Accepted**.
141
152
 
142
- 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.
153
+ If you need new packages (including an icon package for a third-party kit), identify the exact packages and versions. Then **ask for approval before installing**. Show this updated plan, with the ledger, to the user. Wait for confirmation before Phase 3.
143
154
 
144
155
  ---
145
156
 
146
157
  ## Phase 3 — Theme Generation (Ignite UI Theming MCP)
147
158
 
148
- **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).
159
+ **Goal:** produce theming code that matches the visual language of the Figma design. Use the kit variables from Phase 1e (Path A), or the color census and measurements from Phase 1d (Path B).
149
160
 
150
- Read [references/theme-generation.md](references/theme-generation.md) and [references/design-token-bridge.md](references/design-token-bridge.md) in full before running any theming tool. The steps are:
161
+ Read [references/theme-generation.md](references/theme-generation.md) and [references/design-token-bridge.md](references/design-token-bridge.md) in full before you run a theming tool. The steps are:
151
162
 
152
163
  | Step | What to do |
153
164
  | ---- | ---------- |
154
- | **3a** | Inspect the entry point and global stylesheet. The CLI scaffold's starter theme counts as no theme. Reuse an app's own theme only if its variant, design system, and primary color all match the design; otherwise ask before changing it |
155
- | **3b** | Choose the path from the dominant Phase 1f tier. **Path A** (Indigo.Design kits): resolve the design system with the strict precedence order. **Path B** (other kits or none): pick the closest baseline — the user's request, then the kit's direct counterpart, then input label placement, then control heights. In a mixed file, count only rows that map to a component |
156
- | **3c** | CSS path: import the pre-built theme for the design system and variant, then add `theming_create_palette` overrides. Sass path: one `theming_create_theme` call (plus `theming_create_palette` for `gray` or status colors). **Path B:** seed from the color census, then override the type styles that differ (including button casing) with `--ig-<style>-<property>` CSS variables. Do not rely on `customScale`: `theming_create_typography` accepts it, but its generators ignore it |
157
- | **3d** | Map per-component tokens for every Ignite UI component in the plan, always passing `designSystem` and `variant`. Path B also sets radius, border, shadow, and state tokens, and picks `--ig-size` per component family from measured heights |
158
- | **3e** | Validate chart series colors with `theming_get_chart_series_colors` and assign them to the chart's brush properties (`brushes`/`outlines`; `brush` on sparkline, `fillBrushes` on treemap, the ring series on doughnut) |
165
+ | **3a** | Inspect the entry point and the global stylesheet. The starter theme of the CLI scaffold counts as no theme. Reuse the app's own theme only if its variant, design system, and primary color all match the design. Otherwise, ask before you change it |
166
+ | **3b** | Use the dominant Phase 1f tier to choose the path. **Path A** (Indigo.Design kits): use the strict precedence order to resolve the design system. **Path B** (other kits or none): choose the closest baseline. Use the user's request, then the kit's direct counterpart, then input label placement, then control heights. In a mixed file, count only the rows that map to a component |
167
+ | **3c** | CSS path: import the pre-built theme for the design system and variant. Then add `theming_create_palette` overrides. Sass path: make one `theming_create_theme` call (plus `theming_create_palette` for `gray` or status colors). **Path B:** seed the palette from the color census. Then use `--ig-<style>-<property>` CSS variables to override the type styles that differ (including button casing). Do not use `customScale`: `theming_create_typography` accepts it, but its generators ignore it |
168
+ | **3d** | Map the per-component tokens for every Ignite UI component in the plan. Always pass `designSystem` and `variant`. Path B also sets radius, border, shadow, and state tokens. It also uses the measured heights to choose `--ig-size` for each component family |
169
+ | **3e** | Validate the chart series colors with `theming_get_chart_series_colors`. Assign them to the brush properties of the chart (`brushes`/`outlines`; `brush` on sparkline, `fillBrushes` on treemap, the ring series on doughnut) |
159
170
 
160
171
  Key constraints:
161
172
 
162
- - **Output format:** CSS by default; Sass only when the project is configured for it. Never use the Angular-only `core()` / `theme()` mixins.
163
- - `theming_create_palette` takes `primary`/`secondary`/`surface`/`gray`/`success`/`warn`/`error`/`info` and `variant`, while `theming_create_theme` takes `primaryColor`/`secondaryColor`/`surfaceColor` (no `gray`).
164
- - `theming_create_elevations` takes `designSystem` (`material` or `indigo`); there is no `preset` parameter.
173
+ - **Output format:** CSS is the default. Use Sass only when the project is configured for it. Never use the Angular-only `core()` / `theme()` mixins.
174
+ - `theming_create_palette` takes `primary`/`secondary`/`surface`/`gray`/`success`/`warn`/`error`/`info` and `variant`. `theming_create_theme` takes `primaryColor`/`secondaryColor`/`surfaceColor` (no `gray`).
175
+ - `theming_create_elevations` takes `designSystem` (`material` or `indigo`). It has no `preset` parameter.
165
176
  - Never use the font name as the primary design-system signal.
166
- - 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).
167
- - **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.
177
+ - 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 chooses the nearest step for each component family (3d).
178
+ - **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`. Thus, seed the secondary color with the button color.
168
179
 
169
180
  ---
170
181
 
@@ -174,49 +185,51 @@ Key constraints:
174
185
 
175
186
  ### Implementation Rules
176
187
 
177
- 1. **Never generate component markup without reading its doc or API entry first** — the `get_doc` result, or the skill reference file when the catalog has no doc (Phase 2b).
188
+ 1. **Never generate component markup before you read its doc or API entry.** Use the `get_doc` result, or the skill reference file when the catalog has no doc (Phase 2b).
178
189
  2. **Section by section** — layout → navigation → primary content → secondary → data.
179
- 3. **Register every custom element you use, once, in the right place.**
190
+ 3. **Register every custom element that you use, once, in the correct place.**
180
191
  ```typescript
181
192
  import { defineComponents, IgcNavbarComponent, IgcCardComponent } from 'igniteui-webcomponents';
182
193
  defineComponents(IgcNavbarComponent, IgcCardComponent);
183
194
  ```
184
- Grids use `IgcGridComponent.register()`, Grid Lite `IgcGridLite.register()`, charts and gauges `ModuleManager.register(IgcCategoryChartModule, …)` from `igniteui-webcomponents-core`, and the dock manager `defineComponents(IgcDockManagerComponent)` from `igniteui-dockmanager` (trial) or `@infragistics/igniteui-dockmanager` (licensed). In a framework-wrapped app, follow [`igniteui-wc-integrate-with-framework`](../igniteui-wc-integrate-with-framework/SKILL.md) instead. Registering components you do not use inflates the bundle — see [`igniteui-wc-optimize-bundle-size`](../igniteui-wc-optimize-bundle-size/SKILL.md).
185
- 4. **Respect the shadow DOM boundary.** Page CSS does not reach a component's internals. In order of preference: component **design tokens** (Phase 3d) → documented `::part(...)` selectors → slotted content you style yourself. Never target internal class names. CSS custom properties **do** inherit through shadow roots, which is why all color work goes through palette variables.
186
- 5. **Slots, not attributes, carry content.** `igc-list-item` uses `start` / `title` / `subtitle` / `end`; `igc-navbar` uses `start` / `end`; `igc-card` composes `igc-card-header`, `igc-card-content`, `igc-card-actions`, `igc-card-media`. Confirm the slot names from `get_doc` before writing markup.
187
- 6. **Bind non-primitive values as properties, not attributes.** Arrays, objects, and functions (grid `data`, chart `dataSource`, combo `data`) must be assigned on the element (`.data=${rows}` in Lit, `el.dataSource = rows` in plain JS). A serialized attribute silently fails. Assign chart brushes as properties too.
188
- 7. **Events are `igc*`-prefixed** (`igcChange`, `igcInput`, `igcClosing`, …) — take the exact names from `get_api_reference`, and remember there is no two-way binding.
189
- 8. Use CSS Grid first to match Figma frame proportions; add Flexbox for sub-regions.
190
- 9. Apply theming via the tokens and palette variables generated in Phase 3 — no raw hex values in view code.
195
+ Grids use `IgcGridComponent.register()`, and Grid Lite uses `IgcGridLite.register()`. Charts and gauges use `ModuleManager.register(IgcCategoryChartModule, …)` from `igniteui-webcomponents-core`. The dock manager uses `defineComponents(IgcDockManagerComponent)` from `igniteui-dockmanager` (trial) or `@infragistics/igniteui-dockmanager` (licensed). In a framework-wrapped app, follow [`igniteui-wc-integrate-with-framework`](../igniteui-wc-integrate-with-framework/SKILL.md) instead. If you register components that you do not use, the bundle becomes larger (see [`igniteui-wc-optimize-bundle-size`](../igniteui-wc-optimize-bundle-size/SKILL.md)).
196
+ 4. **Respect the shadow DOM boundary.** Page CSS does not reach the internals of a component. Use these methods in this order of preference: component **design tokens** (Phase 3d) → documented `::part(...)` selectors → slotted content that you style yourself. Never target internal class names. CSS custom properties **do** inherit through shadow roots. For this reason, all color work goes through palette variables.
197
+ 5. **Slots, not attributes, carry content.** `igc-list-item` uses `start` / `title` / `subtitle` / `end`. `igc-navbar` uses `start` / `end`. `igc-card` contains `igc-card-header`, `igc-card-content`, `igc-card-actions`, `igc-card-media`. Before you write markup, confirm the slot names from `get_doc`.
198
+ 6. **Bind non-primitive values as properties, not attributes.** Assign arrays, objects, and functions (grid `data`, chart `dataSource`, combo `data`) on the element (`.data=${rows}` in Lit, `el.dataSource = rows` in plain JS). A serialized attribute fails silently. Also assign chart brushes as properties.
199
+ 7. **Events are `igc*`-prefixed** (`igcChange`, `igcInput`, `igcClosing`, …). Take the exact names from `get_api_reference`. There is no two-way binding.
200
+ 8. Use CSS Grid first to match the Figma frame proportions. Add Flexbox for sub-regions.
201
+ 9. Apply theming through the tokens and palette variables from Phase 3. Do not put raw hex values in view code.
191
202
  10. Use typed mock data that matches the design's density and domain.
192
- 11. Keep layout, spacing, and typography in stylesheets (or the component's `static styles`) — not inline styles.
193
- 12. **Input variants:** the Indigo.Design kits express `line` / `box` / `border` input types; Web Components expose a single boolean **`outlined`** attribute on `igc-input`, `igc-textarea`, `igc-select`, `igc-combo`, `igc-date-picker`, `igc-date-range-picker`, and the other input-base components. Map `_Input/Border` → `outlined`; map `_Input/Line` and `_Input/Box` → default (no `outlined`). For other kits, map the normalized style: **outlined** → `outlined`; **filled** / **underlined** → default. Label placement comes from the baseline design system (3b), not from an attribute. There is **no** global injection token equivalent — set the attribute on each control, and close any remaining gap with `input-group` component tokens rather than internal CSS.
194
- 13. **Layout surfaces:** for every entry in the Phase 1g Table B (Layout Surfaces), add a CSS class with the recorded `background`, `border-radius`, `padding`, `border`, and `box-shadow`. Never leave a section transparent if the Figma surface has a background; never add a background to a section that floats on the page background in the design.
195
- 14. **Implement only controls that appear in the Figma artboard.** Do not add toolbar buttons, actions, or UI elements that look useful but are not in the design context output for that artboard.
203
+ 11. Keep layout, spacing, and typography in stylesheets (or the component's `static styles`), not in inline styles.
204
+ 12. **Input variants:** the Indigo.Design kits have `line` / `box` / `border` input types. Web Components have a single boolean **`outlined`** attribute on `igc-input`, `igc-textarea`, `igc-select`, `igc-combo`, `igc-date-picker`, `igc-date-range-picker`, and the other input-base components. Map `_Input/Border` → `outlined`, and map `_Input/Line` and `_Input/Box` → default (no `outlined`). For other kits, map the normalized style: **outlined** → `outlined`; **filled** / **underlined** → default. Label placement comes from the baseline design system (3b), not from an attribute.
205
+
206
+ There is **no** global injection token equivalent, so set the attribute on each control. Close any remaining gap with `input-group` component tokens, not with internal CSS.
207
+ 13. **Layout surfaces:** every entry in the Phase 1g Table B (Layout Surfaces) needs a CSS class. Give the class the recorded `background`, `border-radius`, `padding`, `border`, and `box-shadow`. If the Figma surface has a background, never leave the section transparent. If a section floats on the page background in the design, never add a background to it.
208
+ 14. **Implement only controls that appear in the Figma artboard.** Do not add toolbar buttons, actions, or UI elements that are not in the design context output for that artboard. This rule also applies when they look useful.
196
209
  15. After each major section, check it in the browser if the dev server is running.
197
210
 
198
211
  ### Layout and File Structure
199
212
 
200
- Translate Figma frame dimensions into CSS Grid first, matching desktop proportions before adding breakpoints, and place each view where the project expects it. The grid pattern, the Lit host-display pitfall, and the per-view file layout are in [references/project-setup.md § Implementation Layout](references/project-setup.md#implementation-layout).
213
+ Translate the Figma frame dimensions into CSS Grid first. Match the desktop proportions before you add breakpoints. Put each view where the project expects it. [references/project-setup.md § Implementation Layout](references/project-setup.md#implementation-layout) has the grid pattern, the Lit host-display pitfall, and the per-view file layout.
201
214
 
202
215
  ---
203
216
 
204
217
  ## Phase 5 — Visual Validation (Playwright MCP)
205
218
 
206
- **Goal:** measure and compare the running app against the Figma reference screenshots from Phase 1c. Use the measurement-driven loop — compare numbers, not impressions.
219
+ **Goal:** measure the running app and compare it with the Figma reference screenshots from Phase 1c. Use the measurement-driven loop: compare numbers, not impressions.
207
220
 
208
- Read [references/validation-patterns.md](references/validation-patterns.md) in full before running any Playwright tool.
221
+ Read [references/validation-patterns.md](references/validation-patterns.md) in full before you run a Playwright tool.
209
222
 
210
223
  ### 5a: Ensure the Dev Server Is Running
211
224
 
212
- Ask the user for the local dev URL if not already known (Vite default: `http://localhost:5173`).
225
+ If you do not know the local dev URL, ask the user for it (Vite default: `http://localhost:5173`).
213
226
 
214
227
  ```
215
228
  playwright_browser_navigate({ url: "http://localhost:5173" })
216
229
  playwright_browser_console_messages() // check for startup errors
217
230
  ```
218
231
 
219
- Unregistered custom elements are a silent failure mode: the element renders as an empty inline box with no console error. If a section is missing, check `defineComponents` first.
232
+ An unregistered custom element fails silently. It renders as an empty inline box, and the console shows no error. If a section is missing, check `defineComponents` first.
220
233
 
221
234
  ### 5b: Match Viewport to Artboard Dimensions
222
235
 
@@ -225,7 +238,7 @@ playwright_browser_resize({ width: <artboard.width>, height: <artboard.height> }
225
238
  playwright_browser_navigate({ url: "<target route>" }) // re-navigate after resize
226
239
  ```
227
240
 
228
- > **Always re-navigate after resize.** The browser may reset to `about:blank` on viewport change. This is a known Playwright MCP pitfall.
241
+ > **Always re-navigate after resize.** The browser can reset to `about:blank` when the viewport changes. This is a known Playwright MCP problem.
229
242
 
230
243
  ### 5c: Capture and Compare Screenshots
231
244
 
@@ -236,19 +249,19 @@ For **each target artboard** (run the full 5c–5f loop once per page):
236
249
  ```
237
250
  playwright_browser_take_screenshot({ type: "png" })
238
251
  ```
239
- 3. Do a **section-by-section** comparison against the Phase 1c reference file: top bar → sidebar → **every section in the Phase 1g Table B** → footer.
240
- 4. Do **not** advance to the next artboard until only Cosmetic and Accepted items remain on the current one.
252
+ 3. Do a **section-by-section** comparison with the Phase 1c reference file: top bar → sidebar → **every section in the Phase 1g Table B** → footer.
253
+ 4. Do **not** go to the next artboard until only Cosmetic and Accepted items remain on the current artboard.
241
254
 
242
255
  ### 5d: Measure Computed Styles
243
256
 
244
- For each section with visible differences — and **mandatorily for every entry in the Phase 1g Table B** — use `playwright_browser_evaluate` to extract exact values. Pass code as a **plain JavaScript function string** using the `function` parameter.
257
+ Use `playwright_browser_evaluate` to get exact values for each section with visible differences. **You must also do this for every entry in the Phase 1g Table B.** Pass the code as a **plain JavaScript function string** in the `function` parameter.
245
258
 
246
- > **Shadow DOM changes every measurement.** `document.querySelector('igc-card .title')` returns `null` — the inner nodes live in a shadow root. Measure the host element for box metrics, and pierce with `el.shadowRoot.querySelector(...)` (or `::part` targets) for internals. `references/validation-patterns.md` provides a reusable deep-query helper — use it instead of writing ad-hoc selectors.
259
+ > **Shadow DOM changes every measurement.** `document.querySelector('igc-card .title')` returns `null`, because the inner nodes are in a shadow root. Measure the host element for box metrics. For internals, pierce the shadow root with `el.shadowRoot.querySelector(...)` (or `::part` targets). `references/validation-patterns.md` has a reusable deep-query helper. Use it, not ad-hoc selectors.
247
260
 
248
- Run the three mandatory audits from `validation-patterns.md` on every page, and compare all returned values against the Figma spec from Phase 1d:
261
+ Run the three mandatory audits from `validation-patterns.md` on every page. Compare all returned values with the Figma spec from Phase 1d:
249
262
 
250
- - **Surfaces audit** — every Table B section has the recorded background (or none, when it floats on the page), and encloses the children shown inside it in Figma.
251
- - **Action controls audit** — every visible control, shadow roots included, is in the Phase 1d inventory. Anything else is fabricated and must be removed.
263
+ - **Surfaces audit** — every Table B section has the recorded background (or no background, when it floats on the page). Each section encloses the children that Figma shows inside it.
264
+ - **Action controls audit** — every visible control, shadow roots included, is in the Phase 1d inventory. Any other control is fabricated. Remove it.
252
265
  - **Registration audit** — every `igc-*` tag on the page is a defined custom element.
253
266
 
254
267
  ### 5e: Classify and Report Mismatches
@@ -262,9 +275,9 @@ Run the three mandatory audits from `validation-patterns.md` on every page, and
262
275
  | **Cosmetic** | Rounding only | `rgb(51, 51, 51)` vs `#333333`; ≤ 4px size | Report only |
263
276
  | **Accepted** | Approved delta | A ledger entry the user approved | Report only; not a retry |
264
277
 
265
- The full table and the definitions are in `validation-patterns.md § Mismatch Severity Classification`. A visibly different color is Major, not Cosmetic. **Accepted** needs the user's approval of a ledger entry, from Phase 2d or added during Phase 5.
278
+ `validation-patterns.md § Mismatch Severity Classification` has the full table and the definitions. A visibly different color is Major, not Cosmetic. **Accepted** needs the user's approval of a ledger entry. The entry comes from Phase 2d, or you add it during Phase 5.
266
279
 
267
- For each mismatch, produce:
280
+ For each mismatch, write this report:
268
281
 
269
282
  ```
270
283
  ISSUE: <description>
@@ -277,7 +290,7 @@ FIX: <specific code change>
277
290
 
278
291
  ### 5f: Apply Corrections
279
292
 
280
- Fix Critical, Major, and Minor issues. After applying fixes, re-navigate and take a fresh screenshot to confirm:
293
+ Fix Critical, Major, and Minor issues. After you apply the fixes, re-navigate and take a new screenshot to confirm them:
281
294
 
282
295
  ```
283
296
  playwright_browser_navigate({ url: "<target route>" })
@@ -302,20 +315,20 @@ Check that:
302
315
 
303
316
  ## Critical Rules
304
317
 
305
- - **Phase 0 is not optional.** Never skip MCP verification, and establish which Figma MCP server is connected before Phase 1.
318
+ - **Phase 0 is not optional.** Never skip MCP verification. Before Phase 1, identify which Figma MCP server is connected.
306
319
  - **Classify provenance per instance (Phase 1f).** Do not assume the Indigo.Design kits. A third-party kit's names and variables are evidence to normalize, not to copy.
307
- - **Never import from Code Connect of another library.** Code Connect snippets that point at shadcn, MUI, or an in-house package confirm the role only. The code is always Ignite UI.
320
+ - **Never import from Code Connect of another library.** Code Connect snippets that point to shadcn, MUI, or an in-house package confirm the role only. The code is always Ignite UI.
308
321
  - **Seed the palette from usage on Path B.** Use the color painted on the component, not the variable named `…/500`. On a `material` baseline, controls use `secondary`.
309
- - **Ledger what tokens cannot fix; fix what they can.** Structural anatomy deltas go to the user in Phase 2d. Color, radius, casing, and height mismatches get fixed.
310
- - **Phase 2b before code.** Never write a tag, attribute, or slot you have not read from a doc or API entry (or the skill reference file when no doc exists). Doc names are not tag names.
322
+ - **Record in the ledger what tokens cannot fix. Fix what tokens can fix.** Send structural anatomy deltas to the user in Phase 2d. Fix color, radius, casing, and height mismatches.
323
+ - **Phase 2b before code.** Never write a tag, attribute, or slot that you did not read in a doc or API entry. When no doc exists, use the skill reference file. Doc names are not tag names.
311
324
  - **Register what you use.** An unregistered element fails silently.
312
- - **Phase 1c screenshots are immutable ground truth.** Save them; never overwrite them.
313
- - **Re-navigate after resize** in Phase 5 to avoid Playwright's browser reset bug.
314
- - **Respect the shadow boundary** — tokens and parts, never internal class names.
315
- - **Match the theming output format to the project** — CSS by default, Sass only when configured.
316
- - **Rate-limit Figma MCP calls.** Use `figma_get_metadata` for discovery, then targeted `figma_get_design_context` per artboard, and `figma_get_variable_defs` once per target page. On the desktop server, check that each response describes the requested artboard. When you rely on the selection, ask the user to select each artboard first and do not batch those calls.
317
- - **Fail fast on 3 retries.** If the same correction fails three times, stop, report the issue to the user, and ask for guidance.
318
- - **Do not modify dependency manifests or lock files without asking.** Identify the exact packages and versions required, then get approval before installing.
325
+ - **Phase 1c screenshots are immutable ground truth.** Save them. Never overwrite them.
326
+ - **Re-navigate after resize** in Phase 5 to prevent the Playwright browser reset bug.
327
+ - **Respect the shadow boundary.** Use tokens and parts, never internal class names.
328
+ - **Match the theming output format to the project.** Use CSS by default. Use Sass only when the project is configured for it.
329
+ - **Rate-limit Figma MCP calls.** Use `figma_get_metadata` for discovery. Then make one targeted `figma_get_design_context` call for each artboard, and one `figma_get_variable_defs` call for each target page. On the desktop server, make sure that each response describes the requested artboard. When you use the selection, first ask the user to select each artboard. Do not batch those calls.
330
+ - **Fail fast on 3 retries.** If the same correction fails three times, stop. Report the issue to the user, and ask for guidance.
331
+ - **Do not change dependency manifests or lock files without asking.** Identify the exact packages and versions that are necessary. Then get approval before you install them.
319
332
 
320
333
  ---
321
334
 
@@ -325,4 +338,4 @@ Check that:
325
338
  - [`igniteui-wc-customize-component-theme`](../igniteui-wc-customize-component-theme/SKILL.md) — source of truth for palette behavior, global theme rules, and the theming system
326
339
  - [`igniteui-wc-integrate-with-framework`](../igniteui-wc-integrate-with-framework/SKILL.md) — registration and binding in React, Angular, Vue, or vanilla JS hosts
327
340
  - [`igniteui-wc-generate-from-image-design`](../igniteui-wc-generate-from-image-design/SKILL.md) — fallback when no Figma file is available (static image input)
328
- - [`igniteui-wc-optimize-bundle-size`](../igniteui-wc-optimize-bundle-size/SKILL.md) — keeping registrations and package imports lean
341
+ - [`igniteui-wc-optimize-bundle-size`](../igniteui-wc-optimize-bundle-size/SKILL.md) — keep registrations and package imports small