feat(skills): updating all skills with igniteui-cli mcp refs#17236
feat(skills): updating all skills with igniteui-cli mcp refs#17236damyanpetev merged 12 commits into21.2.xfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the igniteui-angular-components skill documentation to reference and document the igniteui-cli MCP server, and adds “Overview” sections that direct agents to use MCP tools for detailed docs/API reference lookups.
Changes:
- Add
igniteui-cliMCP server prerequisite + setup/verification guidance to the components skill hub. - Introduce a new
references/mcp-setup.mdwith editor-specific MCP configuration examples. - Add “Overview” sections across multiple component reference docs pointing to
get_doc/get_api_reference.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| skills/igniteui-angular-components/SKILL.md | Adds MCP prerequisite + setup instruction block and links to setup reference. |
| skills/igniteui-angular-components/references/mcp-setup.md | New MCP setup guide for VS Code/Cursor/Claude Desktop/JetBrains + verification step. |
| skills/igniteui-angular-components/references/layout.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/layout-manager.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/form-controls.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/feedback.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/directives.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/data-display.md | Adds an Overview section directing to MCP docs/API reference tools. |
| skills/igniteui-angular-components/references/charts.md | Extends the Overview with MCP docs/API reference tool guidance. |
| - [Key Rules](#key-rules) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each form control component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each form control component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each form control component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
| - [Key Rules](#key-rules) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each feedback and overlay component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each feedback and overlay component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each feedback and overlay component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
| - [Drag and Drop](#drag-and-drop) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each directive, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific directive or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each directive, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific directive or feature you're interested in. | |
| This reference gives high-level guidance on when to use each directive, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific directive or feature you're interested in. |
| - [Chat (AI Chat Component)](#chat-ai-chat-component) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each data display component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each data display component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each data display component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
| ## Overview | ||
|
|
||
| Ignite UI for Angular Charts provides 65+ chart types for data visualization. Charts are packaged separately in `igniteui-angular-charts` (or `@infragistics/igniteui-angular-charts` for licensed users). | ||
| This reference give high-level guidance on when to use each chart type, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific chart component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each chart type, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific chart component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each chart type, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific chart component or feature you're interested in. |
| - [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. |
There was a problem hiding this comment.
The intro sentence describes the Ignite UI CLI MCP server as enabling “theming code” and refers to “theming tools”, but this file is for the igniteui-cli server (component/docs tooling). Please reword this to reflect what igniteui-cli actually provides (e.g., component listing + docs/API reference generation) and avoid implying it’s the theming MCP server.
| 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. | |
| The Ignite UI CLI MCP server enables AI assistants to list available Ignite UI components and access component documentation and API reference tooling. It must be configured in your editor before those tools become available. |
|
|
||
| # Ignite UI for Angular — UI Components | ||
|
|
||
| ## Prerequisites |
There was a problem hiding this comment.
This new prerequisite section duplicates the existing "## Prerequisites" section later in the file, which makes the document structure confusing and breaks the pattern used in other skills. Consider renaming this new section to something like "## Tooling prerequisites" / "## MCP prerequisites" or merging it into the existing prerequisites block.
| ## Prerequisites | |
| ## MCP prerequisites |
| - [Navigation Drawer](#navigation-drawer) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each layout component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each layout component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each layout component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
| > Before using any theming 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 theming related work. | ||
| > Do NOT skip this step or ask the user to do it manually. | ||
|
|
||
| ## Setting Up the Theming MCP Server |
There was a problem hiding this comment.
This MCP setup instruction block repeatedly references "theming tools" / "theming related work" and the following header says "Setting Up the Theming MCP Server", but this skill is the UI components skill and the prerequisite tool here is igniteui-cli. Please update the wording to refer to the Ignite UI CLI MCP server/tools to avoid sending agents/users to the wrong server.
| > Before using any theming 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 theming related work. | |
| > Do NOT skip this step or ask the user to do it manually. | |
| ## Setting Up the Theming MCP Server | |
| > Before using any 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 |
| - [Tile Manager](#tile-manager) | ||
|
|
||
| ## Overview | ||
| This reference give high-level guidance on when to use each layout manager component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
There was a problem hiding this comment.
Grammar: "This reference give" should be "This reference gives".
| This reference give high-level guidance on when to use each layout manager component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. | |
| This reference gives high-level guidance on when to use each layout manager component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Closes #
Description
Motivation / Context
Type of Change (check all that apply):
Component(s) / Area(s) Affected:
How Has This Been Tested?
Test Configuration:
Screenshots / Recordings
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)