Ignite UI for Angular — UI Components

Prerequisites

• An Angular project on the major version matching the installed igniteui-angular package (igniteui-angular majors track Angular majors)
• @angular/cli installed
• 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 below.
• A theme applied to the application (see igniteui-angular-theming).
• provideAnimations() in app.config.ts — required before using any overlay or animated component

Ignite UI CLI MCP Server (recommended, not required)

The igniteui-cli MCP server provides list_components, get_doc, search_docs, search_api, and get_api_reference. Its full component docs cover a subset of components (the catalog grows over releases — call list_components once to see what exists; e.g. Combo, Simple Combo, Chat, Tooltip, and grid toolbar/export docs). Where a get_doc doc exists, prefer it over the reference files below. search_api/get_api_reference cover API members (inputs, outputs, methods) for all components — use them for member-level lookups. For everything else, the reference files below are the primary guidance.

If the tools are not available, do not block the task — use the reference files. Suggest that the user run npx -y igniteui-cli ai-config from the project root (it configures both the igniteui-cli and igniteui-theming MCP servers and copies the agent skill files) and reload the editor. MCP servers cannot be started mid-session; the configuration takes effect on the next session. Editor-specific details are in references/mcp-setup.md.

Required Workflow

This file is a routing hub only. It contains no code examples and no API details. Component APIs change between releases, so never write component selectors, import paths, input/output names, or directive names from memory — read the relevant reference files first.

1. Identify every component or feature involved. Map the user's request to one or more rows in the Task → Reference File table below. A single request often spans multiple categories (e.g., a form inside a Dialog requires both form-controls.md and feedback.md).
2. Read every identified reference file in full, in a single parallel batch of file reads — even if you believe you already know the answer.
3. Then produce output, based only on what you read. If something is not covered by the reference files, look it up with get_doc/search_docs when the MCP tools are available; otherwise state explicitly that the detail is unverified instead of guessing.

Task → Reference File

When in doubt, read more rather than fewer reference files. The cost of an unnecessary file read is negligible; the cost of hallucinated API usage is a broken application.

Package Variants

Both packages share identical entry-point paths. Check package.json and use that package name as the prefix for every import. Never import from the root barrel of either package. Both packages can be added to the project using @angular/cli with the following commands: ng add igniteui-angular or ng add @infragistics/igniteui-angular.

Related Skills

• igniteui-angular-grids — Data Grids (Flat Grid, Tree Grid, Hierarchical Grid, Pivot Grid, Grid Lite)
• igniteui-angular-theming — Theming & Styling