Conversation
Co-authored-by: radomirchev <52001020+radomirchev@users.noreply.github.com>
…ve instead Co-authored-by: radomirchev <52001020+radomirchev@users.noreply.github.com>
…nfig fix(cspell): add missing terms from agentic-workflow.md to dictionary
fix lint errors
fix lint errors
Correct heading formatting and remove outdated author note.
Updated headings for clarity and consistency, removed outdated competitive comparison section.
Removed 'Telerik' and 'Syncfusion' from cspell.json.
|
|
||
| ### Core Tools — Available Across All Frameworks | ||
|
|
||
| | Tool | What it does | |
There was a problem hiding this comment.
Currently we have the following MCP tools: detect_platform, list_components, search_docs, get_doc, generate_ignite_app , additionally we will have "search_api", "get_api_reference"
There was a problem hiding this comment.
Pull request overview
This PR adds two new AI-focused documentation topics describing Ignite UI “agentic workflows”, Agent Skills, and MCP server setup/usage, plus a small cspell dictionary update to support the new content.
Changes:
- Added a “best practices” guide for configuring the Ignite UI MCP server and registering a Skill file.
- Added a broader “AI-Assisted Development” overview topic covering Skills, MCP architecture, and getting-started steps.
- Extended
cspell.jsonwith a new allowed term used in the added docs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 13 comments.
| File | Description |
|---|---|
en/components/ai/igniteui-mcp-doc.md |
New setup/how-to topic for MCP server + Skill registration and workflow behavior. |
en/components/ai/agentic-workflow.md |
New overview/landing topic describing the Skills + MCP toolchain and getting started steps. |
cspell.json |
Adds a new allowed word used by the new documentation content. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| description: Learn how to set up the Ignite UI MCP server, register agent skills for GitHub Copilot, Claude, and Cursor, and ground AI coding assistants in correct component APIs, import paths, and scaffolding workflows for Angular, React, Blazor, and Web Components. | ||
| keywords: ignite ui mcp server, ignite ui agent skills, ai-assisted ui development, copilot angular components, cursor blazor ui library, ai component library angular react blazor, mcp server ui components, ignite ui scaffolding, github copilot ignite ui, claude code ignite ui |
| --- | ||
|
|
||
| <a name="hero"></a> | ||
| Your Developers and AI Agents, Finally Working from the Same Playbook |
|
|
||
| ### Does Ignite UI have AI support for Blazor development? | ||
|
|
||
| Yes. Ignite UI Blazor Agent Skills launch March 14, 2026 — the first dedicated agent Skills for any Blazor UI library. They cover Razor syntax, correct property bindings, and Blazor component patterns. The Blazor MCP server follows in Q3 2026. |
en/components/ai/igniteui-mcp-doc.md
Outdated
| |--------|---------| | ||
| | `igniteui-mcp-server` | Component docs: `detect_platform`, `list_components`, `search_docs`, `get_doc`, `generate_ignite_app` | | ||
|
|
||
| The `SKILL.md` file in this repository contains the orchestration instructions that tell the agent exactly when and how to call each tool, in what order, and how to self-configure if the server is not yet connected. Without the skill file the agent has access to the tools but will not follow the correct workflow. |
| description: Ignite UI provides Agent Skills, an MCP server, and a Design-to-Code pipeline that ground AI coding assistants in correct component APIs, import paths, and design tokens for Angular, React, Blazor, and Web Components. | ||
| keywords: ignite ui agent skills, ignite ui mcp server, ai-assisted ui development, copilot angular components, cursor blazor ui library, ai component library angular react blazor, mcp server ui components, design-to-code figma angular |
| 5. [Competitive Comparison](#competitive) | ||
| 6. [Getting Started](#getting-started) | ||
| 7. [FAQ](#faq) |
en/components/ai/igniteui-mcp-doc.md
Outdated
| |--------|----------------| | ||
| | GitHub Copilot | `.agents/skills/` or `.github/skills/` | | ||
| | Claude Code | `.claude/skills/` | | ||
| | Cursor | `.cursor/skills/` | |
en/components/ai/igniteui-mcp-doc.md
Outdated
|
|
||
| ### 1. MCP Server Check (automatic) | ||
|
|
||
| Before doing any work, the agent calls `list_components` to verify the MCP server is live. If the call fails, it **automatically writes the correct config file** for your editor — it does not ask you to do this manually. After writing the file it waits for the server to start before continuing. |
…ve server configuration instructions
…iteUI/igniteui-docfx into rmirchev/agentic-workflow-ai
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
|
||
| # AI-Assisted Development with Ignite UI — Agent Skills & MCP Server for Every Framework | ||
|
|
||
| Ignite UI is the only UI component library with published Agent Skills and a live MCP server across Angular, React, Blazor, and Web Components. It grounds AI coding assistants — GitHub Copilot, Cursor, Windsurf, VS Code Agent Mode — in correct component APIs, import paths, and design tokens, so agents generate production-ready code without hallucination or rework cycles. |
There was a problem hiding this comment.
This is general for all platforms, but on each individual documentation page, only applicable platform is presented. This should be moved to xplat docs. @ChronosSF
Closes #
Checklist:
preview\beta../relative/path.mdIgxSelectComponent,<igx-combo>code blocksfor the names of classes / tags / propertiescode blockspending-localizationlabel when the review of the PR is done