IgniteUI · viktorkombov · Mar 11, 2026 · Mar 12, 2026 · Mar 23, 2026 · Mar 26, 2026
diff --git a/DOCFX-SYNC.md b/DOCFX-SYNC.md
@@ -169,6 +169,11 @@ After fixing, verify that new `<ApiLink>` additions don't conflict with the skil
 
 | File | Purpose |
 |---|---|
-| `scripts/check-mdx-quality.mjs` | Post-sync validation script |
+| `scripts/check-mdx-quality.mjs` | Post-sync validation — detects raw API links, .md extensions, lost `<ApiLink>`/`<Sample>`, callouts, schema comments, unclosed `<br>`, markdown images |
+| `scripts/merge-vnext-updates.mjs` | 3-way body-only merge of docfx vnext updates into local .mdx files; update `LAST_SYNC` after each sync |
+| `scripts/reimport-body.mjs` | Re-merge upstream body for files where initial "keep ours" resolution discarded substantive text; applies MDX transforms to resolved content |
+| `scripts/convert-callouts.mjs` | Convert `>[!NOTE/TIP/...]` callouts to `<DocsAside>` and remove `<!-- schema: -->` comments in-place |
+| `scripts/convert-img-tags.mjs` | Convert `<img class="responsive-img">` tags to `<Image>` components from `astro:assets` |
+| `scripts/migrate-vnext-new-files.mjs` | Apply full DocFX → MDX migration to newly-imported pages (frontmatter cleanup, callouts, code-view, images) |
 | `DOCFX-SYNC.md` | This guide |
 | `.github/skills/docfx-sync/SKILL.md` | AI agent skill for performing syncs |
diff --git a/docs/angular/src/content/en/components/action-strip.mdx b/docs/angular/src/content/en/components/action-strip.mdx
@@ -79,6 +79,7 @@ import { IgxIconComponent } from 'igniteui-angular/icon';
 export class HomeComponent {}
 ```
 
+
 <DocsAside type="note">
 This component uses Material Icons. Add the following link to your `index.html`: `<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">`
 </DocsAside>

diff --git a/docs/angular/src/content/en/components/ai/ai-assisted-development-overview.mdx b/docs/angular/src/content/en/components/ai/ai-assisted-development-overview.mdx
@@ -1,17 +1,18 @@
 ---
 title: AI-Assisted Development with Ignite UI - Ignite UI for Angular
-description: Configure Agent Skills, the Ignite UI MCP server, and the Theming MCP server in your Angular, React, Blazor, or Web Components project with a single command — npx igniteui-cli ai-config. Grounds GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant in correct Ignite UI APIs.
+description: Configure Agent Skills, the Ignite UI MCP server, and the Theming MCP server in your Angular, React, Blazor, or Web Components project with a single command - npx igniteui-cli@latest ai-config. Grounds GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant in correct Ignite UI APIs.
 keywords: Angular, Ignite UI for Angular, Infragistics, MCP, Model Context Protocol, Ignite UI MCP server, Ignite UI Theming MCP, Agent Skills, AI, agent, Copilot, Cursor, Claude Code, ai-config
 license: MIT
 canonicalLink: "/components/ai-assisted-development-overview"
 mentionedTypes: []
+last_updated: "2026-05-03"
 ---
 
 import DocsAside from 'igniteui-astro-components/components/mdx/DocsAside.astro';
 
 # AI-Assisted Development with Ignite UI
 
-Ignite UI for Angular provides a complete AI toolchain - Agent Skills, the Ignite UI CLI MCP server, the Ignite UI Theming MCP server and the MAKER MCP server - that grounds AI coding assistants in correct component APIs, import paths, and design tokens. Agent Skills are developer-owned instruction packages that define how AI agents use Ignite UI in a specific project. The CLI MCP server (`@igniteui/mcp-server`) exposes Ignite UI CLI scaffolding, component management, and documentation tools to the active AI agent session via the Model Context Protocol. The Theming MCP server (`igniteui-theming`) exposes the Ignite UI Theming Engine as queryable agent context. The MAKER MCP (`@igniteui/maker-mcp`) is a multi-agent AI orchestration MCP server from Infragistics that decomposes complex tasks into validated, executable step plans using a consensus-based voting algorithm across multiple AI agents. Skills, CLI MCP and Theming MCP - all three are configured by a single command: `npx igniteui-cli ai-config`
+Ignite UI for Angular provides a complete AI toolchain - Agent Skills, the Ignite UI CLI MCP server, the Ignite UI Theming MCP server and the MAKER MCP server - that grounds AI coding assistants in correct component APIs, import paths, and design tokens. Agent Skills are developer-owned instruction packages that define how AI agents use Ignite UI in a specific project. The CLI MCP server (`igniteui-cli`) exposes Ignite UI CLI scaffolding, component management, and documentation tools to the active AI agent session via the Model Context Protocol. The Theming MCP server (`igniteui-theming`) exposes the Ignite UI Theming Engine as queryable agent context. The MAKER MCP (`@igniteui/maker-mcp`) is a multi-agent AI orchestration MCP server from Infragistics that decomposes complex tasks into validated, executable step plans using a consensus-based voting algorithm across multiple AI agents. Skills, CLI MCP and Theming MCP - all three are configured by a single command: `npx igniteui-cli ai-config`
 
 The MCP servers and Agent Skills serve different purposes and have different prerequisites:
 
@@ -40,25 +41,27 @@ Without a version pin, `npx` may pull an older CLI version that does not recogni
 </DocsAside>
 
 
+If `ai-config` cannot detect the framework from your project files, it prompts you to select one - so the command works even from a project where no Ignite UI package is installed yet.
+
 After the command finishes, start the MCP servers in your AI client. The servers are configured but not yet running - the client needs to launch each server before its tools are available to the agent.
 
 ### What to Expect
 
 If Ignite UI is **not** installed in the project:
 
-```
-Ignite UI MCP servers configured in .vscode/mcp.json
-No AI skill files found. Make sure packages are installed (npm install) and your Ignite UI packages are up-to-date.
-```
+<DocsAside type="note">
+Ignite UI MCP servers configured for your selected clients
+No AI skill files found. Make sure packages are installed (`npm install`) and your Ignite UI packages are up-to-date.
+</DocsAside>
 
 The MCP servers are ready to use. Skills will be added automatically the next time you run `ai-config` after installing Ignite UI.
 
 If Ignite UI **is** installed in the project:
 
-```
-Ignite UI MCP servers configured in .vscode/mcp.json
-Agent Skills copied to .claude/skills/
-```
+<DocsAside type="note">
+Ignite UI MCP servers configured for your selected clients
+Agent Skills copied to your selected agents' skills directories
+</DocsAside>
 
 Both the MCP servers and Skills are configured.
 
@@ -93,7 +96,7 @@ npm install igniteui-angular
 npx igniteui-cli@latest ai-config
 ```
 
-The command detects that Skills are now available and copies them. The MCP server entries in `.vscode/mcp.json` are left unchanged (already up-to-date)
+The command detects that Skills are now available and copies them. The MCP configuration files for your selected clients are left unchanged (already up-to-date).
 
 ## The AI Toolchain at a Glance
 
@@ -119,13 +122,13 @@ For full setup instructions and IDE wiring, see [Agent Skills](skills.md).
 
 The Ignite UI CLI MCP server (`igniteui-cli`) is an MCP server maintained by Infragistics that exposes Ignite UI CLI scaffolding and documentation tools to the active AI agent session. Once connected, the AI assistant can create Angular, React, Blazor or Web Components projects, add and modify Ignite UI components, and answer documentation and API questions - all through natural-language prompts in the chat session.
 
-The CLI MCP server is configured via `npx` without a global install:
+The CLI MCP server runs via `npx` without a global install:
 
 ```bash
-npx igniteui-cli ai-config
+npx -y igniteui-cli mcp
 ```
 
-The server connects to VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, JetBrains AI Assistant, and any other MCP-compatible client that supports STDIO transport. The exact configuration format differs by client - see the CLI MCP setup guides below.
+Use `ai-config` to write the MCP configuration for your AI client automatically. The server connects to VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, JetBrains AI Assistant, and any other MCP-compatible client that supports STDIO transport. The exact configuration format differs by client - see [CLI MCP](cli-mcp.md) for the full setup guide.
 
 It does not generate code autonomously - it exposes tools to the AI agent, which invokes them in response to developer prompts.
 
@@ -168,7 +171,7 @@ The `ai-config` command configures MCP servers, copies framework-specific skill
 ng generate @igniteui/angular-schematics:ai-config
 ```
 
-This also registers the `@angular/cli` MCP server in `.vscode/mcp.json` alongside the Ignite UI servers.
+This also registers the `@angular/cli` MCP server alongside the Ignite UI servers for your selected clients.
 
 **Using the Ignite UI CLI:**
 
@@ -198,7 +201,11 @@ The command requires Ignite UI packages to be installed in your project (`npm in
 
 ### Step 1 - Load Agent Skills
 
-Copy the Ignite UI Skill package for your framework into your project's agent discovery path. The Skill package ships with the library in `node_modules/igniteui-{framework}/skills/`. Wire it to your IDE using the persistent setup for your client.
+Copy the Ignite UI Skill package for your framework into your project's agent discovery path.
+
+The Skill package ships with the library in `node_modules/igniteui-{framework}/skills/`.
+
+Wire it to your IDE using the persistent setup for your client.
 
 See [Agent Skills](skills.md) for the complete setup.
 
@@ -238,6 +245,8 @@ For the full setup guide, including VS Code, GitHub, Cursor, Claude Desktop, Cla
 
 Add the `igniteui-theming` entry to the same MCP configuration file, alongside `igniteui-cli`:
 
+**VS Code (`.vscode/mcp.json`):**
+
 ```json
 {
   "servers": {
@@ -249,6 +258,19 @@ Add the `igniteui-theming` entry to the same MCP configuration file, alongside `
 }
 ```
 
+**Cursor, Claude Desktop, Claude Code, JetBrains, and other MCP clients:**
+
+```json
+{
+  "mcpServers": {
+    "igniteui-theming": {
+      "command": "npx",
+      "args": ["-y", "igniteui-theming", "igniteui-theming-mcp"]
+    }
+  }
+}
+```
+
 For configuration details and theming workflows, see [Theming MCP](theming-mcp.md).
 
 ## Additional Resources

diff --git a/docs/angular/src/content/en/components/ai/cli-mcp.mdx b/docs/angular/src/content/en/components/ai/cli-mcp.mdx
@@ -5,7 +5,7 @@ keywords: Angular, Ignite UI for Angular, Infragistics, Ignite UI CLI MCP, Ignit
 license: MIT
 canonicalLink: "/components/ai/cli-mcp"
 mentionedTypes: []
-
+last_updated: "2026-04-24"
 ---
 
 import DocsAside from 'igniteui-astro-components/components/mdx/DocsAside.astro';
@@ -20,7 +20,7 @@ import DocsAside from 'igniteui-astro-components/components/mdx/DocsAside.astro'
 
 Ignite UI CLI MCP gives AI assistants direct access to Ignite UI CLI project scaffolding, component generation, project modification, and documentation-aware workflows through chat or agent mode. The server works alongside [Ignite UI Theming MCP](./theming-mcp.md). CLI MCP handles project and component workflows while Theming MCP handles palettes, themes, tokens, and styling. Most teams connect both servers in the same AI client session.
 
-The recommended setup path is to start with Ignite UI CLI first. That path creates the project, installs the required packages, and writes the initial MCP configuration for VS Code. You can also start from an empty folder and let the assistant create the project through MCP, or connect MCP to a project that already exists.
+The recommended setup path is to start with Ignite UI CLI first. That path creates the project, installs the required packages, and prompts you to choose which AI clients and agents to configure. You can also start from an empty folder and let the assistant create the project through MCP, or connect MCP to a project that already exists.
 
 **Example prompts to try once connected:**
 
@@ -72,19 +72,19 @@ The `-y` flag tells `npx` to auto-confirm the package download prompt so the ser
 You can start with Ignite UI CLI MCP in three ways:
 
 > **Recommended - CLI first**
-> Create the project with Ignite UI CLI first by using `ig new` or the matching `npx --package igniteui-cli igniteui new` command. This is the easiest setup because Ignite UI CLI scaffolds the project, installs the required packages, and writes `.vscode/mcp.json` for VS Code automatically. After that, you only need to review the generated MCP configuration and open the project in your AI client.
+> Create the project with Ignite UI CLI first by using `ig new` or the matching `npx --package igniteui-cli igniteui new` command. This is the easiest setup because Ignite UI CLI scaffolds the project, installs the required packages, and prompts you to choose which AI clients to configure for MCP and which agents to set up skill files for. After that, you only need to review the generated configuration and open the project in your AI client.
 
 > **Empty folder**
 > Start with a completely empty folder, add the MCP configuration manually, and then ask the assistant to create the project through chat. This path is useful when you want MCP to drive the project creation flow from the beginning instead of running the CLI yourself first.
 
 > **Existing project**
-> Add MCP configuration to a project you already have and continue working in the current codebase. Run `ig ai-config` (or `ng generate @igniteui/angular-schematics:ai-config` for Angular projects) to write `.vscode/mcp.json` and copy the Agent Skills into your project automatically. For other AI clients, copy the server entries from the client-specific sections below.
+> Add MCP configuration to a project you already have and continue working in the current codebase. Run `ig ai-config` (or `ng generate @igniteui/angular-schematics:ai-config` for Angular projects) to write MCP configuration for your selected AI clients and copy the Agent Skills into your project. The command prompts you to choose which clients and agents to configure.
 
 All three paths use the same MCP servers. The difference is only how the project is prepared before you start prompting:
 
 - in the **CLI-first** path, Ignite UI CLI creates the project and prepares the first MCP configuration for you
 - in the **empty-folder** path, you create the MCP configuration first and let the assistant create the project after that
-- in the **existing-project** path, run `ig ai-config` to write `.vscode/mcp.json` and copy the Agent Skills automatically, or add the configuration manually for other clients
+- in the **existing-project** path, run `ig ai-config` to write MCP configuration for your selected clients and copy the Agent Skills automatically
 
 In all cases, once the MCP servers are connected and visible in your AI client, the assistant can keep working in the same session.
 
@@ -364,7 +364,7 @@ The following setup scenarios show when to use each starting point.
 
 ### CLI-first setup
 
-Create the project with Ignite UI CLI first when you want the fastest guided setup and want `.vscode/mcp.json` generated for you automatically.
+Create the project with Ignite UI CLI first when you want the fastest guided setup. `ig new` prompts you to select which AI clients to configure for MCP and which agents to set up skill files for.
 
 Example scenarios:
 
@@ -407,9 +407,9 @@ Reload the workspace, reopen the editor, or restart the AI client. Some clients
 
 Verify that the configuration content matches the examples exactly, including key names and argument order.
 
-**The project was created, but the MCP configuration is only available for VS Code**
+**The project was created, but MCP is not configured for one of your AI clients**
 
-Ignite UI CLI writes `.vscode/mcp.json` for the CLI-first path. If you are using Cursor, Claude Desktop, Claude Code, JetBrains, GitHub, or another MCP client, copy the same server entries into that client's configuration format and location.
+`ig new` prompts you to select which clients to configure. If you skipped a client during project creation, run `ig ai-config` and select the missing clients when prompted.
 
 **The assistant is working in the wrong folder or cannot find the project files**
 

diff --git a/docs/angular/src/content/en/components/ai/maker-framework.mdx b/docs/angular/src/content/en/components/ai/maker-framework.mdx
@@ -64,23 +64,23 @@ Switch Copilot Chat to Agent mode and confirm that `plan`, `execute`, and `plan_
 ### Claude Desktop
 
 1. Open your Claude Desktop configuration file:
-    - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
-    - Windows: `%APPDATA%\Claude\claude_desktop_config.json`
+   - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
+   - Windows: `%APPDATA%\Claude\claude_desktop_config.json`
 2. Add the `maker` entry to the `mcpServers` block:
 
-    ```json
-    {
-      "mcpServers": {
-        "maker": {
-          "command": "npx",
-          "args": ["-y", "@igniteui/maker-mcp", "--stdio"],
-          "env": {
-            "Executor__AIProviderKeys__Anthropic": "<your-anthropic-key>"
-          }
-        }
-      }
-    }
-    ```
+   ```json
+   {
+     "mcpServers": {
+       "maker": {
+         "command": "npx",
+         "args": ["-y", "@igniteui/maker-mcp", "--stdio"],
+         "env": {
+           "Executor__AIProviderKeys__Anthropic": "<your-anthropic-key>"
+         }
+       }
+     }
+   }
+   ```
 
 3. Restart Claude Desktop. The first start downloads the native binary (~30 s on a typical connection).