Skip to content

feat(skills): updating all skills with igniteui-cli mcp refs#17236

Merged
damyanpetev merged 12 commits into21.2.xfrom
skills-with-mcp-update-21-2
Apr 24, 2026
Merged

feat(skills): updating all skills with igniteui-cli mcp refs#17236
damyanpetev merged 12 commits into21.2.xfrom
skills-with-mcp-update-21-2

Conversation

@kdinev
Copy link
Copy Markdown
Member

@kdinev kdinev commented Apr 24, 2026

Closes #

Description

Motivation / Context

Type of Change (check all that apply):

  • Bug fix
  • New functionality
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactoring (no functional changes)
  • Documentation
  • Demos
  • CI/CD
  • Tests
  • Changelog
  • Skills/Agents

Component(s) / Area(s) Affected:

How Has This Been Tested?

  • Unit tests
  • Manual testing
  • Automated e2e tests

Test Configuration:

  • Angular version:
  • Browser(s):
  • OS:

Screenshots / Recordings

Checklist:

  • All relevant tags have been applied to this PR
  • This PR includes unit tests covering all the new code (test guidelines)
  • This PR includes API docs for newly added methods/properties (api docs guidelines)
  • This PR includes feature/README.MD updates for the feature docs
  • This PR includes general feature table updates in the root README.MD
  • This PR includes CHANGELOG.MD updates for newly added functionality
  • This PR contains breaking changes
  • This PR includes ng update migrations for the breaking changes (migrations guidelines)
  • This PR includes behavioral changes and the feature specification has been updated with them
  • Accessibility (ARIA, keyboard navigation, focus management) has been verified

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-cli MCP server prerequisite + setup/verification guidance to the components skill hub.
  • Introduce a new references/mcp-setup.md with 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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
## 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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
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.

Copilot uses AI. Check for mistakes.

# Ignite UI for Angular — UI Components

## Prerequisites
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
## Prerequisites
## MCP prerequisites

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
Comment on lines +15 to +24
> 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
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
> 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

Copilot uses AI. Check for mistakes.
- [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.
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar: "This reference give" should be "This reference gives".

Suggested change
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.

Copilot uses AI. Check for mistakes.
kdinev and others added 11 commits April 24, 2026 14:10
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>
@damyanpetev damyanpetev merged commit b7177e0 into 21.2.x Apr 24, 2026
5 checks passed
@damyanpetev damyanpetev deleted the skills-with-mcp-update-21-2 branch April 24, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants