Ignite UI for Angular

May 28, 2026 · View on GitHub

Prerequisites

  • Angular 20+ project
  • @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
  • The Ignite UI CLI MCP server (igniteui-cli) is available as a tool provider

AGENT INSTRUCTION — MCP Server Setup (REQUIRED)

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

Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in references/mcp-setup.md. Read that file for editor-specific configuration steps and verification.

MANDATORY AGENT PROTOCOL — YOU MUST FOLLOW THIS BEFORE PRODUCING ANY OUTPUT

This file is a routing hub only. It contains NO code examples and NO API details.

DO NOT write any component selectors, import paths, input names, output names, or directive names from memory. Component APIs change between versions. Anything generated without reading the reference files will be incorrect.

You are required to complete ALL of the following steps before producing any component-related code or answer:

STEP 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 reading both form-controls.md AND feedback.md).

STEP 2 — Read every identified reference file in full (PARALLEL). Call read_file (or equivalent) on all reference files identified in Step 1 in a single parallel batch — do NOT read them one at a time sequentially. You must do this even if you believe you already know the answer. Do not skip, skim, or partially read a reference file.

STEP 3 — Only then produce output. Base your code and explanation exclusively on what you read. If the reference files do not cover something, say so explicitly rather than guessing.

Task → Reference File

TaskReference file to read
App setup, app.config.ts providers, provideAnimations(), entry-point imports, convenience directive arraysreferences/setup.md
Input Group, Combo, Simple Combo, Select, Date Picker, Date Range Picker, Time Picker, Calendar, Checkbox, Radio, Switch, Slider, Autocomplete, reactive/template-driven formsreferences/form-controls.md
Tabs, Bottom Navigation, Stepper, Accordion, Expansion Panel, Splitter, Navigation Drawerreferences/layout.md
List, Tree, Card, Chips, Avatar, Badge, Icon, Carousel, Paginator, Progress Indicators, Chatreferences/data-display.md
Dialog, Snackbar, Toast, Bannerreferences/feedback.md
Button, Icon Button, Button Group, Ripple, Tooltip, Drag and Dropreferences/directives.md
Layout Manager (igxLayout, igxFlex directives), Dock Manager (igc-dockmanager web component), Tile Manager (igc-tile-manager web component)references/layout-manager.md
Charts (Area, Bar, Column, Stock/Financial, Pie), chart configuration, chart features (animation, tooltips, markers, highlighting, zooming), data bindingreferences/charts.md

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

PackageInstallWho uses it
igniteui-angularnpm install igniteui-angularOpen-source / community
@infragistics/igniteui-angularRequires private @infragistics registryLicensed / enterprise users

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.