You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/SKILL.md
+23-9Lines changed: 23 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,29 @@ user-invocable: true
6
6
7
7
# Ignite UI for Angular — UI Components
8
8
9
+
## Prerequisites
10
+
- Angular 20+ project
11
+
-`@angular/cli` installed
12
+
-`igniteui-angular` or `@infragistics/igniteui-angular` added to the project via `ng add igniteui-angular` (or the `@infragistics` variant) or `npm install` — see [Package Variants](#package-variants) below.
13
+
- A theme applied to the application (see [`igniteui-angular-theming`](../igniteui-angular-theming/SKILL.md)).
14
+
-`provideAnimations()` in `app.config.ts` — **required before using any overlay or animated component**
15
+
- The **Ignite UI CLI MCP server** (`igniteui-cli`) is available as a tool provider
16
+
17
+
> **AGENT INSTRUCTION — MCP Server Setup (REQUIRED)**
18
+
>
19
+
> Before using any Ignite UI CLI MCP tools, you MUST verify the MCP server is available
20
+
> by calling `list_components`. If the tool is not available or the call fails,
21
+
> you MUST automatically configure it by following the setup process steps described below.
22
+
>
23
+
> After writing the file, inform the user that the MCP server has been
24
+
> configured and they may need to reload the editor for the tools to activate.
25
+
> Start the MCP server and wait for that MCP server to start before continuing the component-related work.
26
+
> Do NOT skip this step or ask the user to do it manually.
27
+
28
+
## Setting Up the Ignite UI CLI MCP Server
29
+
30
+
> **Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in [`references/mcp-setup.md`](./references/mcp-setup.md).** Read that file for editor-specific configuration steps and verification.
31
+
9
32
## MANDATORY AGENT PROTOCOL — YOU MUST FOLLOW THIS BEFORE PRODUCING ANY OUTPUT
10
33
11
34
**This file is a routing hub only. It contains NO code examples and NO API details.**
@@ -41,15 +64,6 @@ Base your code and explanation exclusively on what you read. If the reference fi
41
64
42
65
---
43
66
44
-
## Prerequisites
45
-
46
-
- Angular 20+ project
47
-
-`@angular/cli` installed
48
-
-`igniteui-angular` or `@infragistics/igniteui-angular` added to the project via `ng add igniteui-angular` (or the `@infragistics` variant) or `npm install` — see [Package Variants](#package-variants) below.
49
-
- A theme applied to the application (see [`igniteui-angular-theming`](../igniteui-angular-theming/SKILL.md)).
50
-
-`provideAnimations()` in `app.config.ts` — **required before using any overlay or animated component**
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/charts.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@
15
15
## Overview
16
16
17
17
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).
18
+
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.
18
19
19
20
### Chart Component packages
20
21
-`igniteui-angular-charts` — Category Chart, Financial Chart, Data Chart, and Pie Chart components (NPM)
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.
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/directives.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,9 @@
11
11
-[Tooltip](#tooltip)
12
12
-[Drag and Drop](#drag-and-drop)
13
13
14
+
## Overview
15
+
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.
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/feedback.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,9 @@
13
13
-[Banner](#banner)
14
14
-[Key Rules](#key-rules)
15
15
16
+
## Overview
17
+
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.
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/form-controls.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,9 @@
18
18
-[Reactive Forms Integration](#reactive-forms-integration)
19
19
-[Key Rules](#key-rules)
20
20
21
+
## Overview
22
+
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.
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/layout-manager.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,9 @@
9
9
-[Dock Manager](#dock-manager)
10
10
-[Tile Manager](#tile-manager)
11
11
12
+
## Overview
13
+
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.
Copy file name to clipboardExpand all lines: skills/igniteui-angular-components/references/layout.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,9 @@
12
12
-[Splitter](#splitter)
13
13
-[Navigation Drawer](#navigation-drawer)
14
14
15
+
## Overview
16
+
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.
The Ignite UI CLI MCP server enables AI assistants to discover Ignite UI components, access component documentation, and support related Ignite UI workflows. It must be configured in your editor before these tools become available.
14
+
15
+
## VS Code
16
+
17
+
Create or edit `.vscode/mcp.json` in your project:
18
+
19
+
```json
20
+
{
21
+
"servers": {
22
+
"igniteui-cli": {
23
+
"command": "npx",
24
+
"args": ["-y", "igniteui-cli@next", "mcp"]
25
+
}
26
+
}
27
+
}
28
+
```
29
+
30
+
This works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry — `npx -y` handles both cases.
0 commit comments