igniteui-cli 15.0.0 → 15.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "igniteui-cli",
-  "version": "15.0.0",
+  "version": "15.0.1",
   "description": "CLI tool for creating Ignite UI projects",
   "keywords": [
     "CLI",
@@ -66,11 +66,10 @@
     "all": true
   },
   "dependencies": {
-    "@igniteui/angular-templates": "~21.2.1500",
-    "@igniteui/cli-core": "~15.0.0",
-    "@igniteui/mcp-server": "~15.0.0",
+    "@igniteui/angular-templates": "~21.2.1501",
+    "@igniteui/cli-core": "~15.0.1",
+    "@igniteui/mcp-server": "~15.0.1",
     "@inquirer/prompts": "^7.9.0",
-    "@types/yargs": "^17.0.33",
     "chalk": "^5.3.0",
     "glob": "^11.0.0",
     "open": "^10.1.0",
@@ -85,6 +84,7 @@
     "@schematics/angular": "^21.0.0",
     "@types/jasmine": "^5.1.4",
     "@types/node": "^22.5.5",
+    "@types/yargs": "^17.0.33",
     "browser-sync": "^3.0.3",
     "coveralls-next": "^4.2.1",
     "jasmine": "^5.12.0",

package/templates/react/igr-ts/grid/basic/index.js

@@ -14,7 +14,7 @@ class GridTemplate extends IgniteUIForReactTemplate_1.IgniteUIForReactTemplate {
         this.projectType = "igr-ts";
         this.components = ["Grid"];
         this.controlGroup = "Data Grids";
-        this.packages = ["igniteui-react-grids@~19.6.1"];
+        this.packages = ["igniteui-react-grids@~19.6.2"];
         this.hasExtraConfiguration = false;
     }
 }

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/README.md

@@ -10,9 +10,10 @@ Skills are structured instructions that help AI agents understand and execute co
 
 | Skill | Description | Use When |
 | --- | --- | --- |
-| [igniteui-react-components](./igniteui-react-components/SKILL.md) | Identify the right React components (`Igr*`) for a UI pattern, then install, import, and use them — JSX patterns, events, refs, forms | Choosing components or setting up and using them in React |
+| [igniteui-react-components](./igniteui-react-components/SKILL.md) | Identify the right React components (`Igr*`) for a UI pattern, then install, import, and use them - JSX patterns, events, refs, forms | Choosing components or setting up and using them in React |
 | [igniteui-react-customize-theme](./igniteui-react-customize-theme/SKILL.md) | Customize styling using CSS custom properties, Sass, and the theming system in a React context | Applying custom brand colors/styles |
 | [igniteui-react-optimize-bundle-size](./igniteui-react-optimize-bundle-size/SKILL.md) | Reduce bundle size with granular imports, tree-shaking, and lazy loading | Optimizing production performance |
+| [igniteui-react-generate-from-image-design](./igniteui-react-generate-from-image-design/SKILL.md) | Build a React view from a screenshot or mockup using Ignite UI components plus MCP-first theming and token mapping | Converting a design image into a working Ignite UI React page or dashboard |
 
 ## How to Use
 
@@ -22,6 +23,7 @@ When working with an AI agent like GitHub Copilot, reference skills by name or a
 
 - "How do I add a data grid to my React app?"
 - "What Ignite UI component should I use for a date picker?"
+- "Build this dashboard screenshot in Ignite UI React"
 - "Help me customize the button colors to match my brand"
 - "My bundle size is too large, how can I reduce it?"
 - "How do I handle events on IgrCombo?"
@@ -29,6 +31,7 @@ When working with an AI agent like GitHub Copilot, reference skills by name or a
 ### Direct Skill Reference
 
 - "Follow the igniteui-react-components skill for setting up my project"
+- "Use the igniteui-react-generate-from-image-design skill for this mockup"
 - "Use the igniteui-react-customize-theme skill to help me style components"
 - "Apply the igniteui-react-optimize-bundle-size skill to reduce my bundle"
 
@@ -65,6 +68,9 @@ Copy the skill files into your project's `.agents/skills/` directory:
       reference/
     igniteui-react-optimize-bundle-size/
       SKILL.md
+    igniteui-react-generate-from-image-design/
+      SKILL.md
+      references/
 ```
 
 ### Claude Code
@@ -82,6 +88,9 @@ Copy the skill files into your project's `.claude/skills/` directory:
       reference/
     igniteui-react-optimize-bundle-size/
       SKILL.md
+    igniteui-react-generate-from-image-design/
+      SKILL.md
+      references/
 ```
 
 ### Other Agents (Cursor, Windsurf, etc.)

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-components/SKILL.md

@@ -6,14 +6,24 @@ user-invocable: true
 
 # Ignite UI for React Components
 
-This skill covers everything from identifying the right component for a UI requirement to installing, setting up, and using Ignite UI for React components — including JSX patterns, event handling, refs, controlled/uncontrolled form components, and TypeScript.
+## Prerequisites
 
-## Before You Answer
+- The **Ignite UI CLI MCP server** (`igniteui-cli`) available as a tool provider
 
-- Do not guess package names or import paths from memory.
-- First identify the component family, then read the relevant reference files from the Content Guide below.
-- Check `package.json` and keep public or licensed package names consistent.
-- If the required package is not present in `package.json`, add or install the correct Ignite UI dependency first. Absence from `package.json` does not mean the package is invalid.
+> **AGENT INSTRUCTION — MCP Server Setup (REQUIRED)**
+>
+> Before using the Ignite UI CLI MCP tools, you MUST verify the MCP server is available
+> by calling `list_components`. If the tool is not available or the call fails,
+> you MUST automatically configure it by following the setup process steps described below.
+>
+> After writing the file, inform the user that the MCP server has been
+> configured and they may need to reload the editor for the tools to activate.
+> Start the MCP server and wait for that MCP server to start before continuing the component-related work.
+> Do NOT skip this step or ask the user to do it manually.
+
+## Setting Up the Ignite UI CLI MCP Server
+
+> **Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in [`reference/MCP-SERVER.md`](./reference/MCP-SERVER.md).** Read that file for editor-specific configuration steps and verification.
 
 ### Package Routing
 
@@ -76,11 +86,9 @@ This skill is organized into focused reference files. Load the appropriate file
 
 ---
 
-## Quick Start (Core UI Example)
-
-This example uses the core UI package `igniteui-react`. For grids, Grid Lite, charts, gauges, and maps, use the package routing table above first.
+## Quick Start
 
-### 1. Install Core UI Package
+### 1. Install
 
 ```bash
 npm install igniteui-react
@@ -163,7 +171,7 @@ Use [COMPONENT-CATALOGUE.md](./reference/COMPONENT-CATALOGUE.md) to map any UI n
 
 ## Best Practices
 
-1. **Use the package routing table first**
+1. **Start with the MIT package** (`igniteui-react`) — it covers most common UI needs
 2. **Import theme CSS first** — components need it to render correctly
 3. **Register chart/gauge/map modules** — call `.register()` at module level
 4. **Wrap charts/gauges/maps in sized containers** — they need explicit dimensions

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-components/reference/CHARTS-GRIDS.md

@@ -1,5 +1,8 @@
 # Charts, Gauges, Maps & Grid Lite
 
+## Overview
+This reference gives high-level guidance on charts and grids, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific chart, or grid component, or feature you're interested in.
+
 ## Module Registration
 
 > **⚠️ IMPORTANT:** Unlike core UI components (from `igniteui-react`), chart, gauge, and map components from `igniteui-react-charts`, `igniteui-react-gauges`, and `igniteui-react-maps` **require explicit module registration** before use. You must import the corresponding `*Module` class and call `.register()` at the module level (outside the component function).

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-components/reference/COMPONENT-CATALOGUE.md

@@ -1,5 +1,8 @@
 # Component Catalogue
 
+## Overview
+This reference gives high-level guidance on Ignite UI for React components, their key features, and common use cases. For a full list of components, call `list_components` from `igniteui-cli` with the specific chart, or grid component, or feature you're interested in.
+
 ## Available Packages
 
 Ignite UI for React is distributed across several packages depending on your needs:

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-components/reference/MCP-SERVER.md

@@ -0,0 +1,77 @@
+# Setting Up the Ignite UI CLI MCP Server
+
+> **Part of the [`igniteui-react-components`](../SKILL.md) skill hub.**
+
+## Contents
+
+- [VS Code](#vs-code)
+- [Cursor](#cursor)
+- [Claude Desktop](#claude-desktop)
+- [WebStorm / JetBrains IDEs](#webstorm--jetbrains-ides)
+- [Verifying the Setup](#verifying-the-setup)
+
+The Ignite UI CLI MCP server enables AI assistants to generate production-ready theming code. It must be configured in your editor before the theming tools become available.
+
+## VS Code
+
+Create or edit `.vscode/mcp.json` in your project:
+
+```json
+{
+  "servers": {
+    "igniteui-cli": {
+      "command": "npx",
+      "args": ["-y", "igniteui-cli", "mcp"]
+    }
+  }
+}
+```
+
+This works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry — `npx -y` handles both cases.
+
+## Cursor
+
+Create or edit `.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "igniteui-cli": {
+      "command": "npx",
+      "args": ["-y", "igniteui-cli", "mcp"]
+    }
+  }
+}
+```
+
+## Claude Desktop
+
+Edit the Claude Desktop config file:
+- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
+- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
+
+```json
+{
+  "mcpServers": {
+    "igniteui-cli": {
+      "command": "npx",
+      "args": ["-y", "igniteui-cli", "mcp"]
+    }
+  }
+}
+```
+
+## WebStorm / JetBrains IDEs
+
+1. Go to **Settings → Tools → AI Assistant → MCP Servers**
+2. Click **+ Add MCP Server**
+3. Set Command to `npx` and Arguments to `-y igniteui-cli mcp`
+4. Click OK and restart the AI Assistant
+
+## Verifying the Setup
+
+After configuring the MCP server, ask your AI assistant:
+
+> "List all available Ignite UI components"
+
+If the MCP server is running, the `list_components` tool will return all available components for the detected framework.

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-customize-theme/SKILL.md

@@ -1,17 +1,33 @@
 ---
 name: igniteui-react-customize-theme
-description: This skill customizes Ignite UI for React component styling using CSS custom properties, Sass, and the full theming system and should be used when applying brand colors, dark mode, component-level overrides, or scoped themes in a React application
+description: This skill customizes Ignite UI for React component styling using CSS custom properties and the full theming system and should be used when applying brand colors, dark mode, component-level overrides, or scoped themes in a React application
 user-invocable: true
 ---
 
 # Ignite UI for React — Theming Skill
 
+## Prerequisites
+
+- A React project with `igniteui-react` installed
+- A theme CSS file imported in your entry point (see [igniteui-react-components](../igniteui-react-components/SKILL.md))
+- The **Ignite UI Theming MCP server** (`igniteui-theming`)
+
+> **AGENT INSTRUCTION — MCP Server Setup (REQUIRED)**
+>
+> Before using any theming tools, you MUST verify the MCP server is available
+> by calling `detect_platform`. If the tool is not available or the call fails,
+> you MUST automatically configure it by following the setup process steps described below.
+>
+> After writing the file, inform the user that the MCP server has been
+> configured and they may need to reload the editor for the tools to activate.
+> Start the MCP server and wait for that MCP server to start before continuing the theming related work.
+> Do NOT skip this step or ask the user to do it manually.
+
 ## Description
 
-This skill teaches AI agents how to theme Ignite UI for React applications. Two approaches are supported:
+This skill teaches AI agents how to theme Ignite UI for React applications. One approach is supported:
 
 - **CSS custom properties** — works in any project without additional build tooling
-- **Sass** — available when the project has Sass configured; provides the full palette/typography/elevation API
 
 The skill also covers component-level theming, layout controls (spacing, sizing, roundness), and how to use the **Ignite UI Theming MCP server** for AI-assisted code generation — all in a React application context.
 
@@ -23,12 +39,9 @@ The skill also covers component-level theming, layout controls (spacing, sizing,
 - "How do I scope a theme to a specific section of my React app?"
 - "Set up Material Design theming for Ignite UI components"
 
-## Prerequisites
+## Setting Up the Theming MCP Server
 
-- A React project with `igniteui-react` installed
-- A theme CSS file imported in your entry point (see [igniteui-react-components](../igniteui-react-components/SKILL.md))
-- **Optional**: Sass configured in the project (enables the Sass-based theming API)
-- **Optional**: The **Ignite UI Theming MCP server** (`igniteui-theming`) for AI-assisted code generation
+> **Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in [`reference/MCP-SERVER.md`](./reference/MCP-SERVER.md).** Read that file for editor-specific configuration steps and verification.
 
 ## Related Skills
 
@@ -52,7 +65,6 @@ This skill is organized into focused sections. Refer to the appropriate file for
 | Topic | File | When to Use |
 |---|---|---|
 | CSS Theming | [CSS-THEMING.md](./reference/CSS-THEMING.md) | Pre-built themes, CSS custom properties, scoped overrides, layout controls, light/dark switching |
-| Sass Theming | [SASS-THEMING.md](./reference/SASS-THEMING.md) | Sass-based theming with palette(), component theme functions |
 | MCP Server | [MCP-SERVER.md](./reference/MCP-SERVER.md) | AI-assisted theming code generation |
 | Troubleshooting | [TROUBLESHOOTING.md](./reference/TROUBLESHOOTING.md) | Common issues and solutions |
 
@@ -169,9 +181,7 @@ See [CSS-THEMING.md](./reference/CSS-THEMING.md) for approaches: class toggle, m
 3. **Always call `get_component_design_tokens` before `create_component_theme`**
 4. **Palette shades**: 50 = lightest, 900 = darkest
 5. **Surface color must match variant** — light color for `light`, dark for `dark`
-6. **Sass**: Use `@use 'igniteui-theming'` — not `igniteui-angular/theming`
-7. **Sass**: Component themes use `@include tokens($theme)` inside a selector
-8. **Never hardcode colors after palette generation**
+6. **Never hardcode colors after palette generation**
 
 ## Additional Resources
 

package/templates/react/igr-ts/projects/_base/files/__dot__claude/skills/igniteui-react-generate-from-image-design/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: igniteui-react-generate-from-image-design
+description: Implement React application views from design images using Ignite UI for React components. Uses MCP servers (igniteui-cli, igniteui-theming) and tools for component discovery, docs lookup, and theming to choose components, generate theme tokens, and follow React-specific best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working React view with Ignite UI for React. Also triggers when the user asks to "implement this design", "build this UI", "convert this mockup", or "create a page from this image" in an Ignite UI React project.
+user-invocable: true
+---
+
+# Implementing Ignite UI React Views from Design Images
+
+## MANDATORY AGENT PROTOCOL
+
+Before writing any implementation code, you must complete these steps in order:
+
+1. Analyze the image and identify all visible regions and UI patterns.
+2. Read [reference/component-mapping.md](reference/component-mapping.md) and [reference/gotchas.md](reference/gotchas.md).
+3. This skill is React-only. Check package routing, theme CSS imports, or licensing only when imports, packages, or theming depend on it.
+4. To apply a theme, use the theming workflow from this skill and the dedicated `igniteui-react-customize-theme` skill; use the `igniteui-theming` MCP tools instead of styling from memory. This skill is React-only, so hardcode `platform: "react"` in theme-generation calls.
+5. Call `get_doc` for every chosen component family before using it.
+6. Only then start coding.
+
+## Workflow
+
+1. **Analyze the design image** - Read the image, identify every UI section, component, and layout structure.
+2. **Confirm package routing or theme setup if needed** - this skill is React-only; check package routing, theme CSS imports, or licensing only when imports, packages, or theming depend on it.
+3. **Discover components** - Call `list_components` with targeted filters to find matching components for each UI pattern.
+4. **Look up component docs** - Call `get_doc` for every chosen component family before coding.
+5. **Generate theme** - (a) To generate a theme, first extract colors and create a color palette using `create_palette` or `create_custom_palette` depending on the scenario. Then extract elevations and call `create_elevations`. Then extract typography and call `create_typography`. Then call `create_theme` with the palette, elevations, and typography. (b) After a theme exists, prefer design tokens, or scoped semantic CSS variables over raw literals. (c) For every Ignite UI component, call `get_component_design_tokens`, map extracted image tokens to token roles, then call `create_component_theme` with the tokens differing from the global theme for the specific component.
+6. **Implement** - Build the screenshot-first layout, data, and view components.
+7. **Refine** - Use the `set_size`, `set_spacing`, and `set_roundness` tools to refine the view's visual fidelity against the image, then iterate on implementation and theming until the view matches the design closely.
+8. **Validate** - Build, test, run, compare against the image, and fix differences.
+
+## Step 1: Analyze the Design Image
+
+Read the input image carefully. For each visual section, identify:
+
+- **Layout structure**: grid rows/columns, sidebar, navbar, content area proportions, and estimated fixed widths or percentages for major regions.
+> Note: Do not guess the exact CSS properties at this stage; just identify the high-level structure and relative proportions. Do not try to fit the view into exact breakpoints or pixel values. Try to generate a flexible layout that preserves the observed proportions and can adapt to different screen sizes. You will refine the exact CSS rules in Step 8 after building a first version of the view.
+- **Component type**: chart, list, card, map, gauge, table, form, etc.
+- **Color palette**: primary, secondary, surface/background, accent, text colors
+- **Typography**: font sizes, weights, letter-spacing patterns
+- **Surface styling**: borders, border-radius, shadows, elevation, divider treatments
+- **Data patterns**: what mock data is needed (time series, lists, KPIs, geographic)
+- **Spacing system**: translate observed padding and gaps into a small reusable scale derived from the design
+
+Before writing code, create a decomposition table with one row per visible region containing:
+
+| Region | Visual role | Candidate component | Custom CSS required | Data type |
+|---|---|---|---|---|
+| Example: sidebar item list | repeated rows with icon + label | `IgrList` | yes - item height, icon size | domain-appropriate mock data |
+| Example: top bar | brand + tabs + search | `IgrNavbar` | yes - multi-zone flex layout | n/a |
+| Example: side panel | always-visible navigation | `IgrNavDrawer` | yes - width, item styling | n/a |
+
+Start every region with the most appropriate Ignite UI component from [reference/component-mapping.md](reference/component-mapping.md). Only fall back to plain semantic HTML when the component DOM structure is fundamentally incompatible with the design after CSS overrides are considered. Document the reason for any plain-HTML fallback in a code comment.
+
+Before writing code, produce a compact implementation brief that captures:
+
+- chosen components per region
+- fallback HTML regions
+- theme strategy
+- package needs
+- major assumptions
+
+After the table, translate the image into CSS Grid rows and columns first. Preserve desktop proportions before adding responsive behavior, then define explicit breakpoint stacking rules for smaller screens.
+
+## Step 2-3: Use MCP Tools for Discovery
+
+This skill is React-only. Check package routing, theme CSS imports, or licensing only when imports, packages, or theming depend on it.
+
+Then call `list_components` with `framework: "react"` and relevant filters to find components matching each UI pattern. Common filters:
+
+- `chart`, `sparkline` - for data visualization
+- `list view`, `card`, `avatar`, `badge` - for data display
+- `nav`, `navbar`, `drawer` - for navigation
+- `progress`, `gauge` - for metrics
+- `map` - for geographic displays
+- `grid`, `grid lite` - for tabular data
+
+Use narrow search terms to reduce noisy MCP results. Search for the specific UI pattern you need, such as `list view` instead of `list`.
+
+For component-to-Ignite-UI mapping, see [reference/component-mapping.md](reference/component-mapping.md).
+
+## Step 4: Look Up Component API
+
+For every chosen component category, call `get_doc` with the doc name from `list_components` results (e.g., `name: "card"`, `framework: "react"`). Use the doc `name` field from the MCP results, not the result title shown in the list. This is mandatory before coding and gives exact React usage patterns, prop names, slot structure, event signatures, and any required module registration.
+
+Call `search_docs` for feature-based questions (e.g., "how to configure [component] for [specific behavior or styling need]").
+
+## Step 5: Generate Theme with MCP
+
+Use this skill for the image-to-view theming workflow only. The dedicated [`igniteui-react-customize-theme`](../igniteui-react-customize-theme/SKILL.md) skill remains the source of truth for palette-token behavior, global theme rules, and broader theming-system guidance.
+
+### 5a - Existing app guard (always run first)
+
+Before generating any theme code, inspect the app entry points and shared global styles. Typical files include `main.tsx`, `index.tsx`, `App.tsx`, `app/layout.tsx`, `src/index.css`, and other shared CSS files. Look for:
+
+- existing theme CSS imports such as `igniteui-webcomponents/themes/...`
+- grid theme imports such as `igniteui-react-grids/grids/themes/...`
+- existing palette-token overrides or semantic CSS variables already used by the app
+
+Treat a plain stock theme CSS import as required baseline setup, not as evidence of an already customized design system.
+
+- **Existing customized theme found** -> the app already has meaningful palette or token overrides. Do **not** call `create_theme` or `create_palette` unless the user explicitly wants a global theme change. Instead:
+  1. Inspect the existing theme definition and any exposed palette tokens or semantic CSS variables
+  2. Reuse the current design system, variant, and palette tokens wherever they already match the design image
+  3. Skip to **5c** and apply only minimal scoped overrides for the new view's components
+- **Only stock theme CSS import found** -> keep the import in place and proceed with **5b** to generate the minimal override layer needed for the design
+- **No theme import found** -> add the required theme CSS import first, then proceed with **5b**
+
+### 5b - Global theme generation (new projects)
+
+Follow this order - MCP guidance first, image extraction second:
+
+1. **Read MCP guidance first** - call `theming://guidance/colors/rules` (or `get_theming_guidance`) before looking at the image. This tells you the available theme inputs and any luminance or variant constraints.
+2. **Resolve the design system** - infer it from the existing workspace, explicit user request, or the closest visual match in the design. Do not assume one if a stronger signal exists.
+3. **Extract from the image** - now that you know the available slots, extract values only for the inputs you actually need.
+4. **Call `create_theme` or `create_palette`** with the extracted seed values.
+
+```
+create_theme({
+  primaryColor: "<color extracted from image for primary slot>",
+  secondaryColor: "<color extracted from image for secondary slot>",
+  surfaceColor: "<color extracted from image for surface/background slot>",
+  variant: "<resolved theme variant>",
+  platform: "react",
+  fontFamily: "<font extracted from image or existing app>",
+  designSystem: "<resolved design system>"
+})
+```
+
+Read and act on any luminance warnings returned. If the design needs multiple surface depths that a single generated surface color does not cover, use `create_custom_palette` or define semantic CSS variables for the additional depths in the app's global stylesheet.
+
+Use `create_palette` for straightforward designs with a small, coherent color system. Use `create_custom_palette` when the design has multiple distinct surface depths, several accent families, or when the generated palette cannot reliably match the screenshot.
+
+### 5c - Per-component token discovery and mapping (always run)
+
+> **Scope:** this step applies only to **core Ignite UI React components** (grid, grid lite, list, navbar, nav drawer, card, inputs, chips, avatar, etc.). DV components - charts, maps, gauges, and sparklines - do not use the component-token theme generation flow in this skill. Skip this step for them and set their visual properties exclusively via component props as described in [reference/gotchas.md](reference/gotchas.md) and in Step 7.
+
+For **every** core Ignite UI component chosen in Steps 3-4, follow this MCP-first loop - query MCP before touching the image:
+
+1. **Discover (MCP first)** - call `get_component_design_tokens(component)` before looking at the image for that component. Read the full token list with names, types, and descriptions. Identify which tokens correspond to visible surfaces, text, borders, icons, and interaction states.
+2. **Extract (image second)** - now that you know the exact token names, go to the image region for that component and read the exact token value for each relevant token slot. Do not guess; zoom into the component region.
+3. **Generate** - call `create_component_theme(component, platform, licensed, tokens)` passing only the tokens whose resolved value differs from the global theme. This produces scoped CSS or SCSS with the minimal override set.
+
+**Example - theming a grid:**
+- `get_component_design_tokens("grid")` returns `header-background`, `content-background`, `row-hover-background` among many others
+- Look at the grid region in the image -> extract the color intent for header, row background, and hover state
+- Resolve each value to a palette token or local semantic CSS variable
+- Call `create_component_theme("grid", ...)` with only `{ "header-background": "<resolved token>", "content-background": "<resolved token>", "row-hover-background": "<resolved token>" }`
+
+Apply the generated theme blocks in CSS using a scoped wrapper and the underlying web component selectors shown in the MCP output. In selectors, use the rendered `igc-*` tags or `::part()` hooks where applicable.
+
+Do not run `create_component_theme` for regions built with custom HTML/CSS only.
+
+### 5d - Theming sequence summary
+
+Apply in this exact order:
+
+1. Inspect the entry point and shared styles -> customized theme, stock theme only, or missing import?
+2. Create or update the global theme layer: add the required theme CSS import if missing, then `create_theme` or `create_palette` as needed (Step 5b)
+3. For each Ignite UI component: `get_component_design_tokens` -> map image design tokens -> resolve values to design tokens or semantic CSS variables -> `create_component_theme` (Step 5c)
+4. Use `get_color` after palette generation whenever a palette token can represent the final color intent
+
+## Step 6: Install Additional Packages
+
+Core UI components ship with `igniteui-react`. Grid Lite requires both `igniteui-react` and `igniteui-grid-lite`. Advanced grids, charts, maps, and gauges use separate React package families and may also appear under `@infragistics/igniteui-react-*` in licensed workspaces. These packages are version-sensitive: determine the installed Ignite UI version, resolve the compatible published package version, and install only the package set required by the selected components. See [reference/component-mapping.md](reference/component-mapping.md) for package names and import patterns.
+
+Theme CSS imports are also required:
+
+- core components -> `igniteui-webcomponents/themes/<variant>/<design-system>.css`
+- grids -> `igniteui-react-grids/grids/themes/<variant>/<design-system>.css`
+
+If packages are missing, identify the exact packages and versions required first, then ask for approval before installing packages or changing dependency manifests.
+
+Charts, maps, and gauges also require explicit `*.register()` calls at module level in React files. Grid Lite does **not** require registration.
+
+## Step 7: Implement
+
+### Structure
+
+- **Layout**: use Ignite UI layout and data-display components as the starting point for standard regions, then apply CSS Grid/Flexbox and component overrides to match the screenshot. Only substitute plain semantic HTML when an Ignite UI component remains structurally incompatible after a genuine attempt.
+- **Data**: use typed mock data that matches the design's density and domain; add models, helpers, or hooks only when they help the implementation.
+- **View**: keep layout, spacing, typography, and surface styling in CSS modules or shared CSS rather than inline styles wherever practical.
+- **Theming**: apply the resolved design system and theme variant from Step 5, and keep color usage aligned with palette tokens, or local semantic CSS variables.
+
+### Implementation Checks
+
+- Follow the surrounding repo conventions and the existing React skills in this repo, especially [`igniteui-react-components`](../igniteui-react-components/SKILL.md) and [`igniteui-react-customize-theme`](../igniteui-react-customize-theme/SKILL.md)
+- Use [reference/component-mapping.md](reference/component-mapping.md) for component-choice and semantic-fallback rules
+- Use [reference/gotchas.md](reference/gotchas.md) for components, theming, and API edge cases instead of re-encoding those rules inline
+- Favor Ignite UI components over custom HTML when both approaches can reach similar visual fidelity
+- Ensure the required theme CSS imports are present before component usage
+- Preserve spacing, hierarchy, and data density before adding extra interactivity
+- Avoid generic placeholders when the image shows domain-specific content
+- Document brief assumptions when the image is ambiguous instead of silently guessing
+
+## Step 8: Refine
+
+After the first implementation pass, use the `set_size`, `set_spacing`, and `set_roundness` tools to adjust the view's visual properties and close the gap with the image. Focus on the most visually distinctive elements first (e.g., panel proportions, chart shape, button prominence) before tuning smaller details (e.g., row heights, spacing between regions).
+
+## Step 9: Validate
+
+Use this validation loop explicitly:
+
+1. Build
+2. Test
+3. Run the app
+4. Visually compare against the image
+5. Adjust and repeat
+
+In terminal-only environments, the user performs the visual comparison and provides feedback on any mismatches. Only perform the visual check directly when the environment has browser and screenshot capabilities available to the agent.
+
+Use this checklist during the first visual comparison:
+
+- panel proportions
+- control density
+- chart shape
+- legend placement
+- button prominence
+- row heights
+- spacing between regions
+
+Fix TypeScript, JSX, styling, or runtime errors immediately during the build/test steps. Use the build output, component docs, [reference/gotchas.md](reference/gotchas.md), and the user's visual feedback to close the remaining gaps. Typical adjustments include:
+
+- revisiting chart data density, smoothing, marker visibility, or missing module registration
+- adjusting layout ratios, region spacing, or row heights
+- correcting navigation mode, panel chrome, or component choice
+- tuning map/filter treatment and dark-surface hierarchy
+- re-examining the original design for overlooked sections, missing theme imports, or missing packages
+
+After the build succeeds with zero errors, refine layout proportions, color values, missing sections, and typography until the view matches closely.