igniteui-cli 15.8.1 → 15.8.3-alpha.0
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.
- package/lib/MultiTemplateComponent.d.ts +1 -1
- package/lib/TemplateManager.d.ts +1 -1
- package/lib/cli.d.ts +1 -1
- package/lib/cli.js +2 -2
- package/lib/commands/doc.js +1 -1
- package/lib/commands/list.js +1 -1
- package/lib/commands/types.d.ts +2 -2
- package/lib/commands/upgrade.js +4 -1
- package/lib/project-utility/GridHelper.d.ts +6 -2
- package/lib/templates/IgniteUIForReactTemplate.d.ts +9 -5
- package/lib/templates/IgniteUIForReactTemplate.js +2 -2
- package/lib/templates/IgniteUIForWebComponentsTemplate.d.ts +8 -4
- package/lib/templates/IgniteUIForWebComponentsTemplate.js +8 -4
- package/lib/templates/jQueryTemplate.d.ts +8 -4
- package/lib/templates/jQueryTemplate.js +1 -1
- package/package.json +5 -4
- package/templates/blazor/igb/projects/ai-config/files/skills/AGENTS.md +7 -2
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/client-scripts.md +7 -7
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/data-display.md +2 -2
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/form-controls.md +65 -18
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/setup.md +2 -2
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/component-mapping.md +5 -5
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/gotchas.md +24 -5
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/SKILL.md +1 -1
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/references/editing.md +4 -3
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/references/grid-migration.md +1 -1
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/references/types.md +1 -1
- package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-theming/references/common-patterns.md +1 -1
- package/templates/blazor/igb/projects/ai-config/index.d.ts +1 -1
- package/templates/blazor/igb/projects/ai-config/index.js +1 -0
- package/templates/blazor/igb/projects/empty/index.d.ts +1 -1
- package/templates/jquery/js/projects/empty/index.js +1 -0
- package/templates/react/ReactTypeScriptFileUpdate.js +4 -4
- package/templates/react/igr-ts/constants.d.ts +1 -1
- package/templates/react/igr-ts/constants.js +1 -1
- package/templates/react/igr-ts/projects/_base/index.d.ts +1 -1
- package/templates/react/igr-ts/projects/_base/index.js +1 -0
- package/templates/react/igr-ts/projects/ai-config/index.d.ts +1 -1
- package/templates/webcomponents/WebComponentsTypeScriptFileUpdate.js +2 -2
- package/templates/webcomponents/igc-ts/category-chart/default/files/src/app/__path__/__filePrefix__.test.ts +9 -0
- package/templates/webcomponents/igc-ts/category-chart/default/files/src/app/__path__/__filePrefix__.ts +37 -0
- package/templates/webcomponents/igc-ts/category-chart/default/index.d.ts +1 -0
- package/templates/webcomponents/igc-ts/category-chart/default/index.js +21 -0
- package/templates/webcomponents/igc-ts/category-chart/index.d.ts +1 -0
- package/templates/webcomponents/igc-ts/category-chart/index.js +12 -0
- package/templates/webcomponents/igc-ts/constants.d.ts +1 -1
- package/templates/webcomponents/igc-ts/constants.js +1 -1
- package/templates/webcomponents/igc-ts/doughnut-chart/default/files/src/app/__path__/__filePrefix__.test.ts +9 -0
- package/templates/webcomponents/igc-ts/doughnut-chart/default/files/src/app/__path__/__filePrefix__.ts +52 -0
- package/templates/webcomponents/igc-ts/doughnut-chart/default/index.d.ts +1 -0
- package/templates/webcomponents/igc-ts/doughnut-chart/default/index.js +21 -0
- package/templates/webcomponents/igc-ts/doughnut-chart/index.d.ts +1 -0
- package/templates/webcomponents/igc-ts/doughnut-chart/index.js +12 -0
- package/templates/webcomponents/igc-ts/projects/_base/index.d.ts +4 -2
- package/templates/webcomponents/igc-ts/projects/_base_with_home/files/package.json +1 -1
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/README.md +15 -15
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/SKILL.md +36 -36
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/reference/mcp-setup.md +8 -6
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/SKILL.md +62 -60
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/references/mcp-setup.md +8 -6
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/SKILL.md +107 -94
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/asset-extraction.md +32 -32
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-provenance.md +32 -30
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-token-bridge.md +84 -71
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-component-map.md +45 -44
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-exploration.md +57 -51
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/mcp-setup.md +23 -23
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/project-setup.md +28 -26
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/theme-generation.md +45 -35
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/validation-patterns.md +38 -29
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/SKILL.md +63 -63
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/component-mapping.md +12 -12
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/gotchas.md +24 -24
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-grids/SKILL.md +23 -23
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/SKILL.md +23 -23
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/angular.md +10 -10
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/react.md +9 -9
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vanilla-js.md +9 -9
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vue.md +11 -11
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-migrate-grid-lite-to-premium/SKILL.md +18 -18
- package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-optimize-bundle-size/SKILL.md +78 -48
- package/templates/webcomponents/igc-ts/projects/ai-config/index.d.ts +1 -1
- package/templates/webcomponents/igc-ts/projects/ai-config/index.js +1 -0
|
@@ -2,32 +2,32 @@
|
|
|
2
2
|
|
|
3
3
|
> **Part of the [`igniteui-wc-figma-to-app`](../SKILL.md) skill.**
|
|
4
4
|
>
|
|
5
|
-
> Use this file in Phase 3 to translate Figma variable values (from `figma_get_variable_defs`) into Ignite UI Theming MCP inputs. Read
|
|
5
|
+
> Use this file in Phase 3 to translate Figma variable values (from `figma_get_variable_defs`) into Ignite UI Theming MCP inputs. Read all of it before you call a theming tool. For the theming system (palette semantics, token rules, compound components), the source of truth is [`igniteui-wc-customize-component-theme`](../../igniteui-wc-customize-component-theme/SKILL.md).
|
|
6
6
|
|
|
7
|
-
> **Tool names:** like SKILL.md, this file refers to theming tools by their base name.
|
|
7
|
+
> **Tool names:** like SKILL.md, this file refers to theming tools by their base name. Find each tool by its base name (`create_palette`, `create_theme`, `create_component_theme`, …) on the connected `igniteui-theming` server. Your client can show them as `mcp__igniteui-theming__create_palette` or a similar name. The `licensed` parameter is for Angular only. Do not pass it for Web Components.
|
|
8
8
|
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
## Two Paths
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
The provenance tiers that you recorded in Phase 1f ([design-provenance.md](design-provenance.md)) tell you which path to use:
|
|
14
14
|
|
|
15
15
|
| Path | When | What sets the look |
|
|
16
16
|
| --- | --- | --- |
|
|
17
17
|
| **A — Indigo.Design UI Kit** | Most components are Tier A | The kit variant **is** an Ignite UI design system. Palette and font come from the kit variables. Component proportions are already calibrated, so leave size, spacing, and roundness at their defaults. |
|
|
18
18
|
| **B — Any other kit, or no kit** | Most components are Tier B or C | The design system is only the **closest baseline**. Fidelity comes from palette seeds inferred from usage, type-style overrides, per-component radius tokens, and a measured `--ig-size`. See [Path B](#path-b--any-other-kit-or-no-kit). |
|
|
19
19
|
|
|
20
|
-
**Mixed files.** Count only the Table A rows that map to an Ignite UI component. Decorative Tier C frames that stay plain HTML do not count. The larger group
|
|
20
|
+
**Mixed files.** Count only the Table A rows that map to an Ignite UI component. Decorative Tier C frames that stay plain HTML do not count. The larger group sets the path for the global theme. If the groups are equal, ask the user. Then style the other group through component themes scoped to **those instances only**:
|
|
21
21
|
|
|
22
|
-
- Put a class on the minority instances (for example `class="kit-b"`), and pass it as `selector` to `create_component_theme`. Do not scope by the tag alone
|
|
23
|
-
-
|
|
24
|
-
-
|
|
22
|
+
- Put a class on the minority instances (for example, `class="kit-b"`), and pass it as `selector` to `create_component_theme`. Do not scope by the tag alone. A Tier A button and a Tier B button are both `igc-button`, so a tag scope restyles both.
|
|
23
|
+
- In a Path A app, Tier B/C instances get the Path B token work (B2, B5–B8) in those scoped component themes.
|
|
24
|
+
- In a Path B app, Tier A instances get their **kit's** design system. Pass that kit's `designSystem` to their scoped component themes. Do not give them Path B treatment.
|
|
25
25
|
|
|
26
26
|
---
|
|
27
27
|
|
|
28
28
|
## Path A — How the Indigo.Design UI Kits Organize Variables
|
|
29
29
|
|
|
30
|
-
The **Indigo.Design UI Kits** are Figma component libraries
|
|
30
|
+
The **Indigo.Design UI Kits** are Figma component libraries from Infragistics. Designers use these kits as shared libraries to build their own app frames in Figma. The kits have four design-system variants. Each variant has light and dark themes:
|
|
31
31
|
|
|
32
32
|
| Kit variant | Figma library name pattern | `designSystem` value |
|
|
33
33
|
| ---------------------- | ----------------------------------------------- | -------------------- |
|
|
@@ -36,20 +36,20 @@ The **Indigo.Design UI Kits** are Figma component libraries published by Infragi
|
|
|
36
36
|
| Bootstrap | `Indigo.Design UI Kit for Bootstrap` | `"bootstrap"` |
|
|
37
37
|
| Indigo | `Indigo.Design UI Kit` / `Indigo.Design System` | `"indigo"` |
|
|
38
38
|
|
|
39
|
-
**Identifying the active kit variant** is the first task in Phase 3 because it sets the design system for the whole app. Use these signals in **strict precedence order
|
|
39
|
+
**Identifying the active kit variant** is the first task in Phase 3 because it sets the design system for the whole app. Use these signals in **strict precedence order**. Stop at the first clear match:
|
|
40
40
|
|
|
41
|
-
1. **Explicit user request** — "make it Material"
|
|
42
|
-
2. **Library source name** — `figma_get_design_context` / `figma_get_metadata`
|
|
43
|
-
3. **Variable collection name** — `figma_get_variable_defs`
|
|
41
|
+
1. **Explicit user request** — for example, "make it Material" or "use Fluent".
|
|
42
|
+
2. **Library source name** — `figma_get_design_context` / `figma_get_metadata` can reference the source library file name.
|
|
43
|
+
3. **Variable collection name** — `figma_get_variable_defs` can return collection names that include the design system (for example, `Material/color/primary`).
|
|
44
44
|
4. **Elevation variable structure** — inspect `Elevations/*`:
|
|
45
45
|
- **Three-layer DROP_SHADOW** (umbra + penumbra + ambient, `Elevations/Shadow 01-03`) → **Material**
|
|
46
46
|
- **Single-layer DROP_SHADOW** → Indigo, Fluent, or Bootstrap
|
|
47
47
|
5. **Palette shade naming** — `primary/500`, `primary/100`–`primary/900` follows the Material 100–900 convention → likely **Material**.
|
|
48
48
|
6. **Visual heuristics** — see the [Design System Detection table](#design-system-detection-from-figma).
|
|
49
49
|
|
|
50
|
-
> **Never use font name as a primary signal.** "Titillium Web" is the default body font in the Indigo.Design UI Kit for Material
|
|
50
|
+
> **Never use font name as a primary signal.** "Titillium Web" is the default body font in the Indigo.Design UI Kit for Material. It is not specific to one kit variant.
|
|
51
51
|
|
|
52
|
-
All four kit variants
|
|
52
|
+
All four kit variants use the same variable naming conventions:
|
|
53
53
|
|
|
54
54
|
```
|
|
55
55
|
Primitives collection → raw palette values (e.g. blue/500 = #6200EE)
|
|
@@ -61,26 +61,26 @@ Component collection → per-component overrides (e.g. button/background = ali
|
|
|
61
61
|
|
|
62
62
|
## The Web Components Theming Contract
|
|
63
63
|
|
|
64
|
-
Before
|
|
64
|
+
Before you map a value, learn what controls a Web Components theme. This is the largest difference from the Angular flow.
|
|
65
65
|
|
|
66
66
|
| Layer | What it is | How it gets set |
|
|
67
67
|
| --- | --- | --- |
|
|
68
|
-
| **Design system + variant** | `--ig-theme`, `--ig-theme-variant` on `:root` | A pre-built theme CSS import or the `:root` block
|
|
69
|
-
| **Palette** | `--ig-<family>-<shade>` and `--ig-<family>-<shade>-contrast` custom properties | `create_palette` / `create_theme`, or
|
|
68
|
+
| **Design system + variant** | `--ig-theme`, `--ig-theme-variant` on `:root` | A pre-built theme CSS import, or the `:root` block that `create_theme` generates. `configureTheme(ds, variant)` switches component themes at runtime, but it does not rewrite these CSS variables |
|
|
69
|
+
| **Palette** | `--ig-<family>-<shade>` and `--ig-<family>-<shade>-contrast` custom properties | `create_palette` / `create_theme`, or a manual override of the `*-500` base shade |
|
|
70
70
|
| **Typography** | `--ig-font-family` plus the type scale | `create_typography`, or plain CSS in a CSS-only project |
|
|
71
71
|
| **Elevations** | shadow custom properties | `create_elevations` (`designSystem: "material" \| "indigo"`) |
|
|
72
72
|
| **Layout** | `--ig-size`, `--ig-spacing`, `--ig-radius-factor` | `set_size` / `set_spacing` / `set_roundness` |
|
|
73
73
|
| **Per component** | component design tokens | `get_component_design_tokens` → `create_component_theme` |
|
|
74
74
|
|
|
75
|
-
Components read the design system **at runtime from CSS variables
|
|
75
|
+
Components read the design system **at runtime from CSS variables**. When these variables are not present, components fall back to `bootstrap` / `light`. If the palette is correct but `--ig-theme` is missing, you get the correct colors on the wrong component anatomy.
|
|
76
76
|
|
|
77
|
-
**Every theming tool that generates code (`create_*`, `set_size`, `set_spacing`, `set_roundness`) accepts `output: "css" | "sass"
|
|
77
|
+
**Every theming tool that generates code (`create_*`, `set_size`, `set_spacing`, `set_roundness`) accepts `output: "css" | "sass"`. The default is CSS.** Choose the output once in Phase 3, from whether the project has Sass. Then use the same output for all calls. The Web Components Sass API is `@use 'igniteui-theming'` with individual `palette()`, `typography()`, `elevations()`, and `spacing()` mixins. The Angular `core()` / `theme()` mixins do not exist in Web Components.
|
|
78
78
|
|
|
79
79
|
---
|
|
80
80
|
|
|
81
81
|
## Path B — Any Other Kit (or No Kit)
|
|
82
82
|
|
|
83
|
-
A third-party kit
|
|
83
|
+
A third-party kit does not target Ignite UI. Its variable names do not follow Ignite UI conventions. Its component proportions, radii, and type ramp are different from all Ignite UI design systems. Treat theming as **fitting a baseline**: choose the closest design system, then override the values that you measure as different in the design.
|
|
84
84
|
|
|
85
85
|
### B1 — Choose the Baseline Design System by Anatomy
|
|
86
86
|
|
|
@@ -97,38 +97,40 @@ Use the first rule that gives a clear answer:
|
|
|
97
97
|
| Default input height | 48px | 40px | 38px | 28px |
|
|
98
98
|
| Button label casing in the type preset | UPPERCASE | Capitalize | none | UPPERCASE |
|
|
99
99
|
|
|
100
|
-
The label position is the strongest signal.
|
|
100
|
+
The label position is the strongest signal. Do **not** use `material` for a design with labels above its fields (shadcn, Untitled UI, Ant, Tailwind-style kits, most in-house kits), even if its colors look "Material-like". Among the label-above systems, choose the one whose default heights are closest to the measured controls. When the buttons are approximately 36–40px and the inputs approximately 36–44px, `bootstrap` or `fluent` is usually the better starting point. You can override casing (B4), so use casing only to choose between two equal systems.
|
|
101
101
|
|
|
102
|
-
These numbers come from the `igniteui-theming` component schemas and type presets at the default `--ig-size`. If a result looks
|
|
102
|
+
These numbers come from the `igniteui-theming` component schemas and type presets at the default `--ig-size`. If a result looks incorrect, confirm it with `get_component_design_tokens`.
|
|
103
103
|
|
|
104
104
|
### B2 — Infer Color Roles From Usage, Not Names
|
|
105
105
|
|
|
106
|
-
Third-party variable names do not tell you which Ignite UI palette slot they fill. Kits call the brand color `primary`, `brand/600`, `colorBrandBackground`, `md.sys.color.primary`, or
|
|
106
|
+
Third-party variable names do not tell you which Ignite UI palette slot they fill. Kits call the brand color `primary`, `brand/600`, `colorBrandBackground`, `md.sys.color.primary`, or give it no name. Build a **color census** from the design context of the target artboards. Take each seed from the location where the design **uses** it:
|
|
107
107
|
|
|
108
108
|
| Ignite UI palette input | Take the color from |
|
|
109
109
|
| --- | --- |
|
|
110
110
|
| `primary` | The fill of high-emphasis buttons. If there are none, the active tab indicator, checked checkbox/switch, or focused-field accent. |
|
|
111
|
-
| `secondary` | A second accent
|
|
111
|
+
| `secondary` | A second accent that the components use: tonal/secondary buttons, selected chips, FAB. If none exists, use `primary` again. Do not invent one. |
|
|
112
112
|
| `surface` | The page / artboard background. Additional depths (cards, sidebars) → B6. |
|
|
113
|
-
| `gray` |
|
|
113
|
+
| `gray` | Do not pass it at first. Pass it only if the generated grays are visibly different from the design's borders and secondary text. |
|
|
114
114
|
| `error` / `warn` / `success` / `info` | Destructive buttons, error-state fields, alert and status colors |
|
|
115
115
|
|
|
116
|
-
In the **CSS path
|
|
116
|
+
In the **CSS path**, all of these colors go to `create_palette`, which takes `gray` and the status colors. In the **Sass path**, `create_theme` takes only `primaryColor`, `secondaryColor`, and `surfaceColor`. To set `gray` or a status color, also call `create_palette` (or `create_custom_palette`). Put its output **after** the theme output, so that its `:root` palette variables override the generated variables.
|
|
117
117
|
|
|
118
|
-
**Seed-shade rule.** Ignite UI components paint their main fills with the **500** shade of a palette color. Pass the color that is *visible on the component* as the seed, whatever the kit
|
|
118
|
+
**Seed-shade rule.** Ignite UI components paint their main fills with the **500** shade of a palette color. Pass the color that is *visible on the component* as the seed, whatever its name in the kit. Examples: Untitled UI buttons use `Brand/600`, Tailwind-style kits use `blue-600`, and Material 3 uses the tone-40 `primary`. If the buttons use `…/600` and you pass the kit's own `…/500` variable, every component is one step too light.
|
|
119
119
|
|
|
120
|
-
**Material baseline trap.** In the Ignite UI `material` schema, **control accents use the `secondary` palette**: contained-button fill, flat-button text, checkbox fill, and switch thumb. The navbar and tab indicators use `primary`. `fluent`, `bootstrap`, and `indigo` use `primary` for those controls.
|
|
120
|
+
**Material baseline trap.** In the Ignite UI `material` schema, **control accents use the `secondary` palette**: contained-button fill, flat-button text, checkbox fill, and switch thumb. The navbar and tab indicators use `primary`. `fluent`, `bootstrap`, and `indigo` use `primary` for those controls.
|
|
121
121
|
|
|
122
|
-
|
|
122
|
+
Most third-party kits, including Material 3, paint buttons and checkboxes with their primary color. Thus, on a `material` baseline, also seed `secondary` with the brand color from the buttons. Seed `primary` with the color from app bars and tab indicators, which is frequently the same color. If you do not, every button shows an unrelated accent color. Check the resolved roles with `read_resource({ uri: "theming://guidance/colors/roles" })`.
|
|
123
123
|
|
|
124
|
-
|
|
124
|
+
When the variables are available, resolve their alias chains. Use them to *name* and *confirm* what the census found. If the variables and the census do not agree, use the census: it shows what the designer drew.
|
|
125
|
+
|
|
126
|
+
**Full ramps.** If the design visibly uses several shades of one color (hover, pressed, tinted backgrounds), use `create_custom_palette` with `mode: "explicit"` for that color. The explicit mode needs **all 14 shades** (`50`–`900` plus `A100`, `A200`, `A400`, `A700`). Align the kit's stops by lightness, not by label (Tailwind and Untitled UI have `25` and `950` stops that Ignite UI does not have). Derive the accent shades from the neighboring stops. Use `mode: "shades"` for every color whose ramp the design does not show.
|
|
125
127
|
|
|
126
128
|
**Dark variant.** Decide it from the page background, as in [Light vs Dark Mode Detection](#light-vs-dark-mode-detection). Material 3 tonal surfaces (`surface-container-low` … `-highest`) are multiple surface depths. Handle them with B6, not with a lighter `surface` seed.
|
|
127
129
|
|
|
128
130
|
### B3 — Typography
|
|
129
131
|
|
|
130
|
-
1. **Family:** take it from the text styles
|
|
131
|
-
2. **Scale:** map the kit's ramp to Ignite UI type styles **by role and size ranking**, not by name. Override only the styles that differ (see [B4](#b4--button-casing-and-other-type-driven-anatomy) for
|
|
132
|
+
1. **Family:** take it from the text styles that the design uses (the design context `font-['…']` classes). Load it in the app. Kits frequently use Inter, Geist, Roboto Flex, or SF Pro. SF Pro is licensed for Apple platforms only. Use a different web font instead, and tell the user.
|
|
133
|
+
2. **Scale:** map the kit's ramp to Ignite UI type styles **by role and size ranking**, not by name. Override only the styles that differ (see [B4](#b4--button-casing-and-other-type-driven-anatomy) for the procedure):
|
|
132
134
|
|
|
133
135
|
| Kit role (examples) | Ignite UI type style |
|
|
134
136
|
| --- | --- |
|
|
@@ -142,9 +144,9 @@ When the variables are available, resolve their alias chains and use them to *na
|
|
|
142
144
|
|
|
143
145
|
### B4 — Button Casing and Other Type-Driven Anatomy
|
|
144
146
|
|
|
145
|
-
The `material` and `indigo` type presets set `button` to `text-transform: uppercase`. `fluent` uses `capitalize`.
|
|
147
|
+
The `material` and `indigo` type presets set `button` to `text-transform: uppercase`. `fluent` uses `capitalize`. Almost all current third-party kits, including Material 3, use sentence case. If the design does not show uppercase labels, set the button's text transform to `none`. Also set its measured size and weight.
|
|
146
148
|
|
|
147
|
-
**How to override type styles.** The theme's typography writes
|
|
149
|
+
**How to override type styles.** The theme's typography writes each property of each type style to a CSS variable on `:root`, named `--ig-<style>-<property>`. The components read those variables inside their shadow roots. Add a `:root` block **after** the theme import or theme output. In this block, set only the values that differ:
|
|
148
150
|
|
|
149
151
|
```css
|
|
150
152
|
/* After the theme import in styles.css */
|
|
@@ -165,19 +167,19 @@ Ignite UI components read these variables inside their own shadow roots, so the
|
|
|
165
167
|
|
|
166
168
|
### B5 — Radius: Per-Component Tokens, Not a Global Factor
|
|
167
169
|
|
|
168
|
-
`set_roundness` sets a single `radiusFactor` (0–1) that interpolates each component between **its own** minimum and maximum radius
|
|
170
|
+
`set_roundness` sets a single `radiusFactor` (0–1) that interpolates each component between **its own** minimum and maximum radius. These ranges are different for each component. For example, the button range is 0–20px, the card 0–24px, the dialog 0–36px, and the chip 0–16px. Thus one factor cannot reproduce the radius style of a kit, such as "everything is 8px" or "pill buttons, 12px cards".
|
|
169
171
|
|
|
170
|
-
Instead, set the radius tokens that `get_component_design_tokens` returns
|
|
172
|
+
Instead, set the radius tokens of each component to the **measured px value**. Use the tokens that `get_component_design_tokens` returns (`border-radius`, or variants such as `box-border-radius` / `border-border-radius` on `input-group`). Set them in the same `create_component_theme` call as the component's colors. For a pill shape, use half the control height or a large value such as `9999px`.
|
|
171
173
|
|
|
172
174
|
### B6 — Surfaces and Elevation
|
|
173
175
|
|
|
174
|
-
- **Depths:** kits
|
|
175
|
-
- **Shadows:** `create_elevations` only has the `material` and `indigo` presets.
|
|
176
|
+
- **Depths:** kits that use borders instead of shadows (shadcn, Untitled UI, Fluent 2) use 2–4 surface tones. Express them with `create_custom_palette` surface shades or semantic variables (`--surface-1`, `--surface-2`), as in [Multiple Surface Depths](#multiple-surface-depths).
|
|
177
|
+
- **Shadows:** `create_elevations` only has the `material` and `indigo` presets. If the design is flat or border-first, keep the global elevations. Set the components' shadow/elevation tokens to `none` or to the measured `box-shadow` value. If the design uses shadows, pick the closer preset. Then verify the depth of cards, menus, and dialogs in Phase 5.
|
|
176
178
|
- **Borders:** a 1px neutral border on cards, inputs, and menus is part of the anatomy of most modern kits. Set it through the components' border tokens, bound to a gray or surface palette variable.
|
|
177
179
|
|
|
178
180
|
### B7 — Density
|
|
179
181
|
|
|
180
|
-
Choose `--ig-size` **per component family**. Compare the measured height of each family (buttons, inputs, list rows, …) with that family's size steps in the baseline. Each component has its **own default step**. For example, on `material
|
|
182
|
+
Choose `--ig-size` **per component family**. Compare the measured height of each family (buttons, inputs, list rows, …) with that family's size steps in the baseline. Each component has its **own default step**. For example, on `material`, the button default is large (36px), and the input default is medium (48px). Thus a design with 36px buttons and 48px inputs already matches both defaults and needs no change. The steps (default in bold):
|
|
181
183
|
|
|
182
184
|
| Design system | Button small / medium / large | Input small / medium / large |
|
|
183
185
|
| --- | --- | --- |
|
|
@@ -186,17 +188,19 @@ Choose `--ig-size` **per component family**. Compare the measured height of each
|
|
|
186
188
|
| `bootstrap` | 32 / **38** / 48px | 32 / **38** / 48px |
|
|
187
189
|
| `indigo` | 24 / **28** / 32px | 24 / **28** / 32px |
|
|
188
190
|
|
|
189
|
-
For other families, read the steps and the default from `get_component_design_tokens`.
|
|
191
|
+
For other families, read the steps and the default from `get_component_design_tokens`. If the nearest step of a family differs from its default, call `set_size` with that `component`. Set `--ig-size` globally only when **every** family moves in the same direction.
|
|
192
|
+
|
|
193
|
+
If a 2–4px mismatch remains, close it with the component's padding or height tokens, if the component has them. If it does not, do not change the mismatch: Phase 5 rates a difference of 4px or less as Cosmetic. It is never an anatomy delta. The `set_spacing` rule does not change: never convert a Figma pixel value into a multiplier.
|
|
190
194
|
|
|
191
195
|
### B8 — States and Focus
|
|
192
196
|
|
|
193
|
-
Hover, pressed, disabled, and error variants in the kit are **token inputs**. Map their colors
|
|
197
|
+
Hover, pressed, disabled, and error variants in the kit are **token inputs**. Map their colors to the matching state tokens (`hover-background`, `focus-*`, `disabled-*`, …) in the same component theme. Focus rings are very different between kits (a 2–3px offset ring in shadcn and Untitled UI, a bottom accent in Fluent). If the design specifies a focus ring, set it in the component tokens. Always keep focus visible, whatever the design shows: accessibility is not optional.
|
|
194
198
|
|
|
195
199
|
---
|
|
196
200
|
|
|
197
201
|
## Global Palette Mapping
|
|
198
202
|
|
|
199
|
-
> Path A name patterns. For Path B, use
|
|
203
|
+
> These tables show Path A name patterns. For Path B, use them only to *label* a variable after the color census (B2) sets its role.
|
|
200
204
|
|
|
201
205
|
### Primary Color
|
|
202
206
|
|
|
@@ -207,7 +211,7 @@ Hover, pressed, disabled, and error variants in the kit are **token inputs**. Ma
|
|
|
207
211
|
| `Primary/Default` | `primary` | Alternative naming in some kit versions |
|
|
208
212
|
| `palette/primary/500` | `primary` | Prefixed naming pattern |
|
|
209
213
|
|
|
210
|
-
> **Parameter names differ between tools.** `create_palette` takes `primary`, `secondary`, `surface`, `gray`, `info`, `success`, `warn`, `error`. `create_theme` takes `primaryColor`, `secondaryColor`, `surfaceColor`. Do not
|
|
214
|
+
> **Parameter names differ between tools.** `create_palette` takes `primary`, `secondary`, `surface`, `gray`, `info`, `success`, `warn`, `error`. `create_theme` takes `primaryColor`, `secondaryColor`, `surfaceColor`. Do not confuse them.
|
|
211
215
|
|
|
212
216
|
### Secondary / Accent Color
|
|
213
217
|
|
|
@@ -229,7 +233,7 @@ Hover, pressed, disabled, and error variants in the kit are **token inputs**. Ma
|
|
|
229
233
|
|
|
230
234
|
### Gray / Neutral Palette
|
|
231
235
|
|
|
232
|
-
The gray scale
|
|
236
|
+
The gray scale comes automatically from the surface color. In dark themes, **gray is inverted relative to surface**. Do not pass gray unless the Figma grays are clearly different from the generated grays. Read `theming://guidance/colors/rules` before you override gray.
|
|
233
237
|
|
|
234
238
|
### Semantic Status Colors
|
|
235
239
|
|
|
@@ -242,16 +246,16 @@ The gray scale is derived automatically from the surface color, and **gray is in
|
|
|
242
246
|
|
|
243
247
|
### Multiple Surface Depths
|
|
244
248
|
|
|
245
|
-
Designs frequently use two or three surface depths (page, panel, card) that a single generated `surface` cannot express.
|
|
249
|
+
Designs frequently use two or three surface depths (page, panel, card) that a single generated `surface` cannot express. In that case:
|
|
246
250
|
|
|
247
251
|
- use `create_custom_palette` for explicit per-shade control, or
|
|
248
252
|
- define semantic variables (`--surface-1`, `--surface-2`) alongside the palette and use them in view CSS.
|
|
249
253
|
|
|
250
|
-
Never
|
|
254
|
+
Never use a raw hex value in component styles for a second depth.
|
|
251
255
|
|
|
252
256
|
### Resolving Colors Back Out
|
|
253
257
|
|
|
254
|
-
Use `get_color({ color, variant, contrast, opacity })` to
|
|
258
|
+
Use `get_color({ color, variant, contrast, opacity })` to change a color intent into the correct `var(--ig-<family>-<shade>)` reference, including contrast colors and transparency. Do not write variable names by hand.
|
|
255
259
|
|
|
256
260
|
---
|
|
257
261
|
|
|
@@ -264,11 +268,11 @@ Use `get_color({ color, variant, contrast, opacity })` to turn a color intent in
|
|
|
264
268
|
| `typography/heading/font-family` | `fontFamily` | Use if the heading font differs |
|
|
265
269
|
| `font/primary` | `fontFamily` | Alternative naming |
|
|
266
270
|
|
|
267
|
-
`create_typography` also accepts `designSystem` (
|
|
271
|
+
`create_typography` also accepts `designSystem` (the type scale to start from). The generators currently ignore its `customScale` argument. Override individual type styles with the `--ig-<style>-<property>` variables instead (see [B4](#b4--button-casing-and-other-type-driven-anatomy)).
|
|
268
272
|
|
|
269
|
-
In a CSS-only project, apply typography as plain CSS `font-family` / `font-size` / `font-weight` rules, or the CSS output of `create_typography`. **Do not emit Sass typography mixins into an app that has no Sass.**
|
|
273
|
+
In a CSS-only project, apply typography as plain CSS `font-family` / `font-size` / `font-weight` rules, or use the CSS output of `create_typography`. **Do not emit Sass typography mixins into an app that has no Sass.**
|
|
270
274
|
|
|
271
|
-
|
|
275
|
+
The app must load web fonts (a `<link>` to the font provider or a local `@font-face`). If the browser cannot resolve a font family, it uses a fallback font without a warning, and Phase 5 fails.
|
|
272
276
|
|
|
273
277
|
---
|
|
274
278
|
|
|
@@ -276,19 +280,19 @@ Web fonts must be loaded by the app (a `<link>` to the font provider or a local
|
|
|
276
280
|
|
|
277
281
|
> **These tools are NOT equivalent to Figma spacing values.** Do not create a mapping between Figma pixel values and these tools.
|
|
278
282
|
|
|
279
|
-
`set_spacing` takes a **multiplier** (`1.0` = default, plus optional `inline` / `block` multipliers). `set_roundness` takes a `radiusFactor` between **0 and 1**. `set_size` takes a **density** (`small` / `medium` / `large`, or `1`–`3`).
|
|
283
|
+
`set_spacing` takes a **multiplier** (`1.0` = default, plus optional `inline` / `block` multipliers). `set_roundness` takes a `radiusFactor` between **0 and 1**. `set_size` takes a **density** (`small` / `medium` / `large`, or `1`–`3`). If you pass a Figma `spacing/md = 16` as `set_spacing({ spacing: 16 })`, the result is a 1600% increase.
|
|
280
284
|
|
|
281
285
|
### When to touch these tools (sparingly)
|
|
282
286
|
|
|
283
287
|
| Tool | Use only when | Never because |
|
|
284
288
|
| ---------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
|
|
285
|
-
| `set_size` | Path A: the design consistently uses a noticeably tighter or looser density than the design system default. Path B: per family, as in B7 | A Figma spacing variable
|
|
289
|
+
| `set_size` | Path A: the design consistently uses a noticeably tighter or looser density than the design system default. Path B: per family, as in B7 | A Figma spacing variable has the name "compact" |
|
|
286
290
|
| `set_spacing` | Explicitly requested, or required to match a specific density contract; start at the default | A Figma `spacing/*` pixel value looks like the multiplier number |
|
|
287
291
|
| `set_roundness` | The user explicitly asks for it. For Path B, use per-component radius tokens instead (B5) | A Figma `border-radius/md = 8` maps numerically to a multiplier |
|
|
288
292
|
|
|
289
293
|
### The correct adjustment path
|
|
290
294
|
|
|
291
|
-
Scope `--ig-size` and `--ig-spacing` to the component that needs
|
|
295
|
+
Scope `--ig-size` and `--ig-spacing` to the component that needs them. Both tools take a `component` parameter (and `scope` for a sub-component or container selector) that generates this CSS:
|
|
292
296
|
|
|
293
297
|
```
|
|
294
298
|
set_size({ component: "calendar", size: "small", platform: "webcomponents" })
|
|
@@ -309,9 +313,14 @@ igc-calendar {
|
|
|
309
313
|
}
|
|
310
314
|
```
|
|
311
315
|
|
|
312
|
-
The Indigo.Design kit's component proportions are already calibrated
|
|
316
|
+
The Indigo.Design kit's component proportions are already calibrated for each design system. Start from the defaults. Adjust them only when there is a clear visual reason.
|
|
317
|
+
|
|
318
|
+
**Path B differs.** A third-party kit's proportions are *not* calibrated to Ignite UI, so the defaults are not a safe final state. The prohibition still applies: never convert a px value into a multiplier. But make the **categorical** choices from measurements:
|
|
313
319
|
|
|
314
|
-
|
|
320
|
+
- Pick `--ig-size` from the nearest height step (B7).
|
|
321
|
+
- Set each component's radius token to the measured px value (B5).
|
|
322
|
+
|
|
323
|
+
These choices are not multiplier conversions. They use each tool the way it was designed.
|
|
315
324
|
|
|
316
325
|
---
|
|
317
326
|
|
|
@@ -321,16 +330,16 @@ The Indigo.Design kit's component proportions are already calibrated per design
|
|
|
321
330
|
| -------------------------------------------------------- | ------------------------------------------------------------------------ |
|
|
322
331
|
| Dark artboard background (`#121212`, `#1a1a1a`, similar) | `variant: "dark"` + the dark theme CSS (`themes/dark/<ds>.css`) |
|
|
323
332
|
| Light artboard background (`#fff`, `#f5f5f5`, similar) | `variant: "light"` + the light theme CSS |
|
|
324
|
-
| Multiple artboards — one light, one dark | Ask the user which variant is primary. Generate it as the global theme and run Phase 5 against it. Then add the other variant (the other pre-built theme or a second theme output) under a class or `prefers-color-scheme
|
|
333
|
+
| Multiple artboards — one light, one dark | Ask the user which variant is primary. Generate it as the global theme and run Phase 5 against it. Then add the other variant (the other pre-built theme or a second theme output) under a class or `prefers-color-scheme`. When you switch at runtime, call `configureTheme` with the same design system and variant (see `theme-generation.md § 3c`). Validate it against its own artboard |
|
|
325
334
|
| `color/mode` variable present | Its value (`light` or `dark`) is the authoritative signal |
|
|
326
335
|
|
|
327
|
-
|
|
336
|
+
The surface color must match the variant. A light surface with `variant: "dark"` makes components unreadable, and the palette tools give a luminance warning. Read the warnings.
|
|
328
337
|
|
|
329
338
|
---
|
|
330
339
|
|
|
331
340
|
## Design System Detection from Figma
|
|
332
341
|
|
|
333
|
-
> Path A (Indigo.Design kits) only. For any other kit, choose the baseline with the anatomy rubric in [B1](#b1--choose-the-baseline-design-system-by-anatomy).
|
|
342
|
+
> Use this table for Path A (Indigo.Design kits) only. For any other kit, choose the baseline with the anatomy rubric in [B1](#b1--choose-the-baseline-design-system-by-anatomy).
|
|
334
343
|
|
|
335
344
|
| Figma Visual Signal | Likely Design System | `designSystem` Value |
|
|
336
345
|
| ------------------------------------------------------------------ | -------------------------- | -------------------- |
|
|
@@ -341,7 +350,7 @@ Surface color must match the variant: a light surface with `variant: "dark"` pro
|
|
|
341
350
|
| Purple/indigo accents, rounded corners, single shadow | Infragistics Indigo | `"indigo"` |
|
|
342
351
|
| `primary/500`, `primary/900` palette shade naming | Material (100–900 palette) | `"material"` |
|
|
343
352
|
|
|
344
|
-
`create_elevations` accepts only `"material"` or `"indigo"` as its `designSystem
|
|
353
|
+
`create_elevations` accepts only `"material"` or `"indigo"` as its `designSystem`. For a Fluent or Bootstrap design, pick the closer of the two (usually `material`).
|
|
345
354
|
|
|
346
355
|
---
|
|
347
356
|
|
|
@@ -367,7 +376,7 @@ Theme keys are **not** tag names. Pass the key to `get_component_design_tokens`
|
|
|
367
376
|
|
|
368
377
|
Most other components use their obvious key (`card`, `list`, `navbar`, `chip`, `avatar`, `badge`, `calendar`, `date-picker`, `select`, `combo`, `tabs`, `stepper`, `tree`, `dialog`, `toast`, `snackbar`, `banner`, `tooltip`, `divider`, `rating`, `slider`, `switch`, `checkbox`, `radio`, `carousel`, `chat`, `expansion-panel`, `accordion`, `splitter`, `file-input`, `date-time-input`, `textarea`, `icon`, `ripple`, `highlight`).
|
|
369
378
|
|
|
370
|
-
**Keys with no standalone Web Components selector in the theming tool
|
|
379
|
+
**Keys with no standalone Web Components selector in the theming tool:** do not call the theming tools for `action-strip`, `bottom-nav`, `column-actions`, `overlay`, `query-builder`, `time-picker`, `date-range-start`, `date-range-end`. (The `grid` theme derives `action-strip` and `column-actions`, so theme them through the `grid` theme.) Sub-part keys (`card-header`, `list-item`, `step`, `tab-item`, `accordion-header`, `expansion-panel-header`, `drop-down-item`, `nav-drawer-item`) also have no standalone selector. Style them through the parent's tokens, their documented `::part(...)`, or slotted content.
|
|
371
380
|
|
|
372
381
|
### Step 2: Discover the tokens
|
|
373
382
|
|
|
@@ -375,11 +384,11 @@ Most other components use their obvious key (`card`, `list`, `navbar`, `chip`, `
|
|
|
375
384
|
get_component_design_tokens({ component: "<theme key>" })
|
|
376
385
|
```
|
|
377
386
|
|
|
378
|
-
The result lists every token with name, type, and description
|
|
387
|
+
The result lists every token with its name, type, and description. For compound components, it also lists the **related themes** that you must also theme.
|
|
379
388
|
|
|
380
389
|
### Step 3: Match Figma variables to token names
|
|
381
390
|
|
|
382
|
-
> **Path B:** third-party kits rarely have component variables in this form, and Tier C files usually have none. Take the component's colors, radius, borders, and state colors from the Phase 1d color census and measurements (B2, B5–B8).
|
|
391
|
+
> **Path B:** third-party kits rarely have component variables in this form, and Tier C files usually have none. Take the component's colors, radius, borders, and state colors from the Phase 1d color census and measurements (B2, B5–B8). If variables exist, use them only to confirm these values.
|
|
383
392
|
|
|
384
393
|
Kit component variables follow `<component>/<role>/<state>`:
|
|
385
394
|
|
|
@@ -389,7 +398,11 @@ Kit component variables follow `<component>/<role>/<state>`:
|
|
|
389
398
|
- `grid/header-background` → token `header-background`
|
|
390
399
|
- `navbar/background` → token `background`
|
|
391
400
|
|
|
392
|
-
Lookup process:
|
|
401
|
+
Lookup process:
|
|
402
|
+
|
|
403
|
+
1. Remove the component prefix.
|
|
404
|
+
2. Find the remainder in the token list.
|
|
405
|
+
3. If there is no exact match, pick the token whose description names the same visual role.
|
|
393
406
|
|
|
394
407
|
| Component | Figma Variable | Likely Token Name | Notes |
|
|
395
408
|
| --------- | -------------------------- | ----------------------- | ----------------------- |
|
|
@@ -411,7 +424,7 @@ Lookup process: strip the component prefix, match the remainder against the toke
|
|
|
411
424
|
|
|
412
425
|
### Step 4: Generate the component theme
|
|
413
426
|
|
|
414
|
-
Pass **only tokens that differ from the global theme
|
|
427
|
+
Pass **only tokens that differ from the global theme**. Express values as palette references, never as raw hex:
|
|
415
428
|
|
|
416
429
|
```
|
|
417
430
|
create_component_theme({
|
|
@@ -428,17 +441,17 @@ create_component_theme({
|
|
|
428
441
|
})
|
|
429
442
|
```
|
|
430
443
|
|
|
431
|
-
Apply the generated block exactly as
|
|
444
|
+
Apply the generated block exactly as the tool returns it. Use `selector` to scope an override to one region instead of every instance in the app.
|
|
432
445
|
|
|
433
446
|
### Step 5: Compound components
|
|
434
447
|
|
|
435
|
-
|
|
448
|
+
A compound component is a component whose `get_component_design_tokens` result lists related themes (for example, `combo`, `select`, the date pickers, `card`, `navbar`, `dialog`, `banner`, and the grids). Compound components render internal children with their own themes. Theme each related theme returned in Step 1, and use the parent's selector as the wrapper. If you style only the parent, dropdown surfaces, calendars, and action buttons stay off-theme. Phase 5 then fails.
|
|
436
449
|
|
|
437
450
|
---
|
|
438
451
|
|
|
439
452
|
## Chart Colors
|
|
440
453
|
|
|
441
|
-
Charts have no design tokens. Take the series colors from the Figma design context
|
|
454
|
+
Charts have no design tokens. Take the series colors from the Figma design context. Before you use them, call the theming MCP:
|
|
442
455
|
|
|
443
456
|
```
|
|
444
457
|
get_chart_series_colors({ chartType: "category-chart" }) // which properties accept a brush list
|
|
@@ -446,13 +459,13 @@ get_chart_series_colors({ customBrushes: ["#9DE772", "#6DB1FF"] }) // validate t
|
|
|
446
459
|
get_chart_series_colors({ mode: "color-blind" }) // accessible alternative palette
|
|
447
460
|
```
|
|
448
461
|
|
|
449
|
-
Assign the result to the chart's brush **properties**: `brushes` / `outlines` on most charts, `brush` on `igc-sparkline`, `fillBrushes` on `igc-treemap`, and `brushes` / `outlines` on each `igc-ring-series` of a doughnut chart.
|
|
462
|
+
Assign the result to the chart's brush **properties**: `brushes` / `outlines` on most charts, `brush` on `igc-sparkline`, `fillBrushes` on `igc-treemap`, and `brushes` / `outlines` on each `igc-ring-series` of a doughnut chart. If you do not assign them explicitly, the chart uses its own default palette and does not match the design.
|
|
450
463
|
|
|
451
464
|
---
|
|
452
465
|
|
|
453
466
|
## Variable Resolution Priority
|
|
454
467
|
|
|
455
|
-
|
|
468
|
+
If more than one Figma variable can map to the same theming input, use this priority:
|
|
456
469
|
|
|
457
470
|
1. **Component-scoped variable** (e.g. `button/background`) → per-component token
|
|
458
471
|
2. **Semantic role variable** (e.g. `color/primary`) → global palette input
|
|
@@ -465,11 +478,11 @@ When multiple Figma variables could map to the same theming input:
|
|
|
465
478
|
|
|
466
479
|
Do **not** call theming tools for:
|
|
467
480
|
|
|
468
|
-
- Chart, gauge, and map components → configure
|
|
481
|
+
- Chart, gauge, and map components → configure them through properties; get series colors from `get_chart_series_colors`
|
|
469
482
|
- Pure layout CSS (margins, grid columns, flex gaps) → write it directly in the view's styles
|
|
470
483
|
- Icon colors → set `color` on the `igc-icon` host or its parent
|
|
471
484
|
|
|
472
|
-
|
|
485
|
+
The theming tools **do** support Dock Manager: use the theme key `dock-manager` (selector `igc-dockmanager`), as for other components. It also exposes its own CSS custom properties.
|
|
473
486
|
|
|
474
487
|
---
|
|
475
488
|
|