igniteui-angular 22.2.0-rc.0 → 22.2.0-rc.2

package/skills/igniteui-angular-components/SKILL.md

@@ -1,7 +1,7 @@
 ---
 license: MIT
 name: igniteui-angular-components
-description: "Covers all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider), layout containers (tabs, stepper, accordion, splitter, navigation drawer), data-display components (list, tree, card, chips, carousel, paginator, progress indicators, chat), feedback overlays (dialog, snackbar, toast, banner), directives (button, icon button, button group, ripple, tooltip, drag-and-drop), Dock Manager, Layout Manager, Tile Manager, and Charts. Use when users ask about any Ignite UI Angular component that is NOT a data grid — such as forms, dropdowns, pickers, dialogs, navigation, lists, trees, cards, charts, or initial project setup. Do NOT use for data grids, tables, or tabular data — use igniteui-angular-grids instead. Do NOT use for theming or styling — use igniteui-angular-theming instead."
+description: "Covers all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider), layout containers (tabs, stepper, accordion, splitter, navigation drawer), data-display components (list, tree, card, chips, carousel, paginator, progress indicators, chat), feedback overlays (dialog, snackbar, toast, banner), directives (button, icon button, button group, ripple, tooltip, drag-and-drop), Dock Manager, Layout Manager, Tile Manager, and Charts. WHEN TO USE: users ask about any Ignite UI Angular component that is NOT a data grid, such as forms, dropdowns, pickers, dialogs, navigation, lists, trees, cards, charts, or initial project setup. WHEN NOT TO USE: data grids, tables, or tabular data (use igniteui-angular-grids); theming or styling (use igniteui-angular-theming)."
 user-invocable: true
 ---
 
@@ -14,11 +14,15 @@ user-invocable: true
 - A theme applied to the application (see [`igniteui-angular-theming`](../igniteui-angular-theming/SKILL.md)).
 - `provideAnimations()` in `app.config.ts` — **required before using any overlay or animated component**
 
-## Ignite UI CLI MCP Server (recommended, not required)
+## Ignite UI CLI MCP Server (required)
 
-The `igniteui-cli` MCP server provides `list_components`, `get_doc`, `search_docs`, `search_api`, and `get_api_reference`. Its **full component docs cover a subset of components** (the catalog grows over releases — call `list_components` once to see what exists; e.g. Combo, Simple Combo, Chat, Tooltip, and grid toolbar/export docs). Where a `get_doc` doc exists, prefer it over the reference files below. `search_api`/`get_api_reference` cover API members (inputs, outputs, methods) for all components — use them for member-level lookups. For everything else, the reference files below are the primary guidance.
+The `igniteui-cli` MCP server is the version-accurate source for Ignite UI APIs. It provides `list_components`, `get_doc`, `search_docs`, `search_api`, and `get_api_reference`. Its **full component docs cover a subset of components** (the catalog grows over releases — call `list_components` once to see what exists; e.g. Combo, Simple Combo, Chat, Tooltip, and grid toolbar/export docs). Where a `get_doc` doc exists, prefer it over the reference files below. `search_api`/`get_api_reference` cover API members (inputs, outputs, methods) for all components — use them for every member-level lookup. For everything else, the reference files below are the primary guidance.
 
-If the tools are not available, do not block the task — use the reference files. Suggest that the user run `npx -y igniteui-cli ai-config` from the project root (it configures both the `igniteui-cli` and `igniteui-theming` MCP servers and copies the agent skill files) and reload the editor. MCP servers cannot be started mid-session; the configuration takes effect on the next session. Editor-specific details are in [`references/mcp-setup.md`](./references/mcp-setup.md).
+**Verify the server before any other step** by calling `list_components` with `framework: "angular"`. If the tool is not available:
+
+1. **Configure it yourself — do not just suggest it.** From the project root, run `npx -y igniteui-cli ai-config` (or `ig ai-config` when `igniteui-cli` is installed globally). It configures both the `igniteui-cli` and `igniteui-theming` MCP servers, preserves existing server entries, and copies the Agent Skills. If the client is not covered, add the entries manually from [`references/mcp-setup.md`](./references/mcp-setup.md) — the server command is `npx -y igniteui-cli mcp` (or `ig mcp`).
+2. **Ask the user to reload the editor or agent session, then stop.** MCP tools cannot be loaded into a running session.
+3. **Continue without the server only if the user explicitly asks to.** In that case, use the reference files and mark every selector, import path, and member name you could not verify through the MCP server as unverified.
 
 ## Required Workflow
 
@@ -26,7 +30,7 @@ If the tools are not available, do not block the task — use the reference file
 
 1. **Identify every component or feature involved.** Map the user's request to one or more rows in the Task → Reference File table below. A single request often spans multiple categories (e.g., a form inside a Dialog requires both `form-controls.md` and `feedback.md`).
 2. **Read every identified reference file in full**, in a single parallel batch of file reads — even if you believe you already know the answer.
-3. **Then produce output**, based only on what you read. If something is not covered by the reference files, look it up with `get_doc`/`search_docs` when the MCP tools are available; otherwise state explicitly that the detail is unverified instead of guessing.
+3. **Then produce output**, based only on what you read. If something is not covered by the reference files, look it up with `get_doc`/`search_docs`/`search_api`. Never guess — if the MCP server cannot answer it, state explicitly that the detail is unverified.
 
 ### Task → Reference File
 

package/skills/igniteui-angular-components/references/form-controls.md

@@ -41,7 +41,7 @@ Types: `line` (default), `border`, `box`, `search`.
 
 ## Combo (Multi-Select Dropdown)
 
-> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "combo" })` covers data binding, selection APIs, forms support, keyboard behavior, and known issues. Prefer it over this snippet when available.
+> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "combo" })` covers data binding, selection APIs, forms support, keyboard behavior, and known issues. Prefer it over this snippet.
 
 ```typescript
 import { IgxComboComponent } from 'igniteui-angular/combo';

package/skills/igniteui-angular-components/references/mcp-setup.md

@@ -2,10 +2,18 @@
 
 > **Part of the [`igniteui-angular-components`](../SKILL.md) skill hub.**
 
-The Ignite UI CLI MCP server exposes `list_components`, `get_doc`, `search_docs`, and `search_api` so AI assistants can discover Ignite UI components and read version-accurate documentation. It must be configured in the editor/agent before these tools become available, and the editor or agent session must be restarted afterwards — MCP servers cannot be hot-loaded into a running session.
+The Ignite UI CLI MCP server exposes `list_components`, `get_doc`, `search_docs`, `search_api`, and `get_api_reference` so AI assistants can discover Ignite UI components and read version-accurate documentation. **It is required by the Ignite UI Agent Skills.** It must be configured in the editor/agent before these tools become available, and the editor or agent session must be restarted afterwards — MCP servers cannot be hot-loaded into a running session.
 
 > Depending on the client, MCP tool names may appear with a server prefix (e.g. `mcp__igniteui-cli__list_components` in Claude Code). This skill refers to tools by their bare names.
 
+## Agent Responsibilities
+
+When the `list_components` tool is not available, the agent configures the server itself — it does not only suggest the setup to the user:
+
+1. Run the one-command setup below from the project root.
+2. Ask the user to reload the editor or agent session, then stop.
+3. Continue without the server only if the user explicitly asks to, and mark every API detail that could not be verified through the server as unverified.
+
 ## Recommended: One-Command Setup
 
 From the project root:
@@ -16,6 +24,8 @@ npx -y igniteui-cli ai-config
 
 This configures **both** the `igniteui-cli` and `igniteui-theming` MCP servers, copies the Ignite UI Agent Skills into the project, and preserves any existing server entries in the config files. Inline options such as `--agents claude copilot` and `--assistants vscode cursor` select which agents and editors to configure.
 
+When `igniteui-cli` is installed globally (`npm install -g igniteui-cli`), use `ig ai-config` instead.
+
 Projects created with `npx igniteui-cli new` already have the `igniteui-cli` MCP entry configured.
 
 ## Manual Configuration (fallback)
@@ -35,7 +45,7 @@ Use these only when `ai-config` is unavailable or your editor is not covered by
 }
 ```
 
-`npx -y` works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry.
+`npx -y` works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry. With a global install, `ig mcp` starts the same server — use `"command": "ig", "args": ["mcp"]` in any of the entries on this page.
 
 ### Claude Code
 
@@ -43,6 +53,8 @@ Use these only when `ai-config` is unavailable or your editor is not covered by
 claude mcp add igniteui-cli -- npx -y igniteui-cli mcp
 ```
 
+Or add the entry to the project's `.mcp.json` at the repository root, using the `mcpServers` key shown for Cursor below.
+
 ### Cursor — `.cursor/mcp.json`
 
 ```json