igniteui-angular-components

name: igniteui-angular-components description: "All Ignite UI Angular UI components: application setup and architecture, form controls (Input Group, Combo, Select, Date/Time Pickers, Calendar, Checkbox, Radio, Switch, Slider, reactive forms), layout (Tabs, Bottom Navigation, Stepper, Accordion, Splitter, Navigation Drawer, Layout Manager directives), data display (List, Tree, Card, Chips, Avatar, Badge, Icon, Carousel, Paginator, Progress, Chat), feedback/overlays (Dialog, Snackbar, Toast, Banner), directives (Button, Ripple, Tooltip, Drag and Drop), Dock Manager, and Charts (Area Chart, Bar Chart, Column Chart, Stock/Financial Chart, Pie Chart, IgxCategoryChart, IgxFinancialChart, IgxDataChart, IgxPieChart). Use for any non-grid Ignite UI Angular UI question." user-invokable: true

Ignite UI for Angular — UI Components

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. Call read_file (or equivalent) on each reference file identified in Step 1. 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 — Check app setup. If the component is new to the project (or you're scaffolding a new feature), also read references/setup.md to verify the correct providers and entry-point import patterns. Missing provideAnimations() is the most common source of runtime failures.

STEP 4 — 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

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.

Prerequisites

• Angular 20+ project
• igniteui-angular installed via npm install igniteui-angular, or @infragistics/igniteui-angular for licensed users
• A theme applied (see igniteui-angular-theming)
• provideAnimations() in app.config.ts — required before using any overlay or animated component

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.

Related Skills

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