Skip to content

Commit 6b4704f

Browse files
radomirchevradomirchev
authored
Merge pull request #1969 from IgniteUI/ganastasov/ai-mcp-links-and-formatting
fix(docs): correct MCP links, formatting, and conditional references
2 parents ac47f0b + 78aec09 commit 6b4704f

5 files changed

Lines changed: 26 additions & 32 deletions

File tree

‎doc/en/components/ai/ai-assisted-development-overview.md‎

Lines changed: 12 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,6 @@ namespace: Infragistics.Controls
99
mentionedTypes: []
1010
---
1111

12-
<!-- schema: Article -->
13-
<!-- cspell:words igniteui mcpservers npx theming -->
14-
15-
<!-- feature-meta
16-
name: AI-Assisted Development
17-
category: toolchain
18-
tools: [agent-skills, cli-mcp, theming-mcp, design-to-code]
19-
frameworks: [Angular, React, WebComponents]
20-
clients: [VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, JetBrains AI Assistant]
21-
mcp-transport: STDIO
22-
-->
23-
2412
# AI-Assisted Development with Ignite UI
2513

2614
Ignite UI for Angular, React, and Web Components provides a three-part AI toolchain - Agent Skills, the Ignite UI CLI MCP server, and the Ignite UI Theming 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 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 exposes the Ignite UI Theming Engine as queryable agent context. All three components work with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.
@@ -149,21 +137,21 @@ Add the `igniteui-theming` entry to the same MCP configuration file, alongside `
149137

150138
For configuration details and theming workflows, see [Theming MCP](theming-mcp.md).
151139

140+
## Additional Resources
141+
152142
<!-- React -->
153-
For a single end-to-end example that combines project work, documentation questions, and theming in one conversation, see [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md).
143+
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md)
154144
<!-- end: React -->
155145
<!-- WebComponents -->
156-
For a single end-to-end example that combines project work, documentation questions, and theming in one conversation, see [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md).
146+
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md)
157147
<!-- end: WebComponents -->
148+
- [Agent Skills](./skills.md)
149+
- [Ignite UI CLI MCP](./cli-mcp.md)
150+
- [Ignite UI Theming MCP](./theming-mcp.md)
158151

159-
## Related Topics
152+
<div class="divider--half"></div>
160153

161-
- [Agent Skills](skills.md) - Full setup guide for loading and wiring Skill packages in VS Code, Cursor, Windsurf, and JetBrains
162-
- [CLI MCP](cli-mcp.md) - Full setup guide for Ignite UI CLI MCP, including recommended CLI-first setup and client-specific configuration
163-
<!-- React -->
164-
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md) - A concrete combined workflow from project work to documentation questions to theming in one chat session
165-
<!-- end: React -->
166-
<!-- WebComponents -->
167-
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md) - A concrete combined workflow from project work to documentation questions to theming in one chat session
168-
<!-- end: WebComponents -->
169-
- [Theming MCP](theming-mcp.md) - Theming MCP server setup and theming workflow examples
154+
Our community is active and always welcoming to new ideas.
155+
156+
- [{ProductName} **Forums**]({ForumsLink})
157+
- [{ProductName} **GitHub**]({GithubLink})

‎doc/en/components/ai/cli-mcp.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "{Platform} Ignite UI CLI MCP | Infragistics"
3-
_description: "Connect Ignite UI CLI MCP to your AI client to scaffold projects, modify existing apps, create and update components, and ask documentation questions for {ProductName}. Learn the setup options for VS Code, GitHub, Cursor, Claude Desktop, Claude Code, JetBrains, and other MCP clients."
4-
_keywords: "{Platform}, {ProductName}, Infragistics, Ignite UI CLI MCP, Ignite UI Theming MCP, MCP, Model Context Protocol, AI, agent, GitHub Copilot, Cursor, Claude, JetBrains"
2+
title: {Platform} Ignite UI CLI MCP | Infragistics
3+
_description: Connect Ignite UI CLI MCP to your AI client to scaffold projects, modify existing apps, create and update components, and ask documentation questions for {ProductName}. Learn the setup options for VS Code, GitHub, Cursor, Claude Desktop, Claude Code, JetBrains, and other MCP clients.
4+
_keywords: {Platform}, {ProductName}, Infragistics, Ignite UI CLI MCP, Ignite UI Theming MCP, MCP, Model Context Protocol, AI, agent, GitHub Copilot, Cursor, Claude, JetBrains
55
_language: en
66
_license: MIT
77
_canonicalLink: "{environment:dvUrl}/components/ai/cli-mcp"
@@ -453,13 +453,13 @@ Validate that the JSON uses the `mcpServers` structure and that each local serve
453453

454454
## Additional Resources
455455

456-
- [AI-Assisted Development with Ignite UI](./ai-assisted-development-overview.md)
457456
<!-- React -->
458457
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md)
459458
<!-- end: React -->
460459
<!-- WebComponents -->
461460
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md)
462461
<!-- end: WebComponents -->
462+
- [AI-Assisted Development with Ignite UI](./ai-assisted-development-overview.md)
463463
- [{ProductName} Skills](./skills.md)
464464
- [Ignite UI Theming MCP](./theming-mcp.md)
465465

‎doc/en/components/ai/skills.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -386,6 +386,9 @@ For more information on the Theming MCP, refer to the [Ignite UI Theming MCP](./
386386
- <a href="https://www.infragistics.com/products/ignite-ui-angular/angular/components/general/getting-started">Getting Started with {ProductName}</a>
387387
- <a href="https://www.infragistics.com/products/ignite-ui-angular/angular/components/general/cli-overview">Angular Schematics & Ignite UI CLI</a>
388388
<!-- end: Angular -->
389+
- [AI-Assisted Development with Ignite UI](./ai-assisted-development-overview.md)
390+
- [Ignite UI CLI MCP](./cli-mcp.md)
391+
- [Ignite UI Theming MCP](./theming-mcp.md)
389392

390393
<div class="divider--half"></div>
391394
Our community is active and always welcoming to new ideas.

‎doc/en/components/ai/theming-mcp.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -380,7 +380,9 @@ Also confirm that `core()` is called before any other theming mixin in your `sty
380380
<!-- WebComponents -->
381381
- [Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP](../general-how-to-mcp-e2e.md)
382382
<!-- end: WebComponents -->
383+
- [AI-Assisted Development with Ignite UI](./ai-assisted-development-overview.md)
383384
- [{ProductName} Skills](./skills.md)
385+
- [Ignite UI CLI MCP](./cli-mcp.md)
384386

385387
<!-- Ideally these should be included once documentation is combined
386388
- [Theming Overview](../themes/index.md)

‎doc/en/components/general-how-to-mcp-e2e.md‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP - {ProductName}"
3-
_description: "Follow an end-to-end {ProductName} workflow with Ignite UI CLI MCP and Ignite UI Theming MCP: start CLI-first, connect both MCP servers, create or extend the app through chat, ask documentation questions, and apply a custom theme."
4-
_keywords: "{Platform}, {ProductName}, Infragistics, Ignite UI CLI MCP, Ignite UI Theming MCP, MCP, Model Context Protocol, AI, workflow, theming, prompt"
2+
title: Build an App End-to-End with Ignite UI CLI MCP and Ignite UI Theming MCP - {ProductName}
3+
_description: Follow an end-to-end {ProductName} workflow with Ignite UI CLI MCP and Ignite UI Theming MCP start CLI-first, connect both MCP servers, create or extend the app through chat, ask documentation questions, and apply a custom theme.
4+
_keywords: {Platform}, {ProductName}, Infragistics, Ignite UI CLI MCP, Ignite UI Theming MCP, MCP, Model Context Protocol, AI, workflow, theming, prompt
55
_language: en
66
_license: MIT
77
_canonicalLink: "{environment:dvUrl}/components/general-how-to-mcp-e2e"
@@ -265,9 +265,10 @@ In practice, the most effective pattern is to use CLI MCP for project and compon
265265

266266
## Related Topics
267267

268+
- [AI-Assisted Development with Ignite UI](ai/ai-assisted-development-overview.md)
269+
- [{ProductName} Skills](ai/skills.md)
268270
- [Ignite UI CLI MCP](ai/cli-mcp.md)
269271
- [Ignite UI Theming MCP](ai/theming-mcp.md)
270-
- [AI-Assisted Development with Ignite UI](ai/ai-assisted-development-overview.md)
271272

272273
<div class="divider--half"></div>
273274

0 commit comments

Comments
 (0)