skills/igniteui-angular-components/SKILL.md
Covers all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form controls (inputs, combos, selects, date/time pickers, calendar, checkbox, radio, switch, slider), layout containers (tabs, stepper, accordion, splitter, navigation drawer), data-display components (list, tree, card, chips, carousel, paginator, progress indicators, chat), feedback overlays (dialog, snackbar, toast, banner), directives (button, icon button, button group, ripple, tooltip, drag-and-drop), Dock Manager, Layout Manager, Tile Manager, and Charts. Use when users ask about any Ignite UI Angular component that is NOT a data grid — such as forms, dropdowns, pickers, dialogs, navigation, lists, trees, cards, charts, or initial project setup. Do NOT use for data grids, tables, or tabular data — use igniteui-angular-grids instead. Do NOT use for theming or styling — use igniteui-angular-theming instead.
npx skillsauth add igniteui/igniteui-angular igniteui-angular-componentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 to read |
|---|---|
| App setup, app.config.ts providers, provideAnimations(), entry-point imports, convenience directive arrays | references/setup.md |
| Input Group, Combo, Simple Combo, Select, Date Picker, Date Range Picker, Time Picker, Calendar, Checkbox, Radio, Switch, Slider, reactive/template-driven forms | references/form-controls.md |
| Tabs, Bottom Navigation, Stepper, Accordion, Expansion Panel, Splitter, Navigation Drawer | references/layout.md |
| List, Tree, Card, Chips, Avatar, Badge, Icon, Carousel, Paginator, Progress Indicators, Chat | references/data-display.md |
| Dialog, Snackbar, Toast, Banner | references/feedback.md |
| Button, Icon Button, Button Group, Ripple, Tooltip, Drag and Drop | references/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 binding | references/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.
@angular/cli installedigniteui-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.igniteui-angular-theming).provideAnimations() in app.config.ts — required before using any overlay or animated component| Package | Install | Who uses it |
|---|---|---|
| igniteui-angular | npm install igniteui-angular | Open-source / community |
| @infragistics/igniteui-angular | Requires private @infragistics registry | Licensed / 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.
igniteui-angular-grids — Data Grids (Flat Grid, Tree Grid, Hierarchical Grid, Pivot Grid, Grid Lite)igniteui-angular-theming — Theming & Stylingtools
Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server. Use when users ask to theme, restyle, or style Ignite UI components, change colors or the color palette, switch between light and dark themes, create or apply a global theme, customize typography or elevation shadows, adjust spacing, sizing, or roundness, or configure per-component design tokens. Do NOT use for component behavior, APIs, or data binding — use igniteui-angular-components or igniteui-angular-grids instead.
tools
Provides guidance on all Ignite UI for Angular data grid types (Flat Grid, Tree Grid, Hierarchical Grid, Grid Lite, Pivot Grid) including setup, column configuration, sorting, filtering, selection, editing, grouping, summaries, toolbar, export, paging, remote data, and state persistence. Use when users ask about grids, tables, data grids, tabular data display, cell editing, batch editing, row selection, column pinning, column hiding, grouping rows, pivot tables, tree-structured data, hierarchical data, master-detail views, or exporting grid data. Do NOT use for non-grid UI components (forms, dialogs, navigation, charts) — use igniteui-angular-components instead. Do NOT use for theming or styling — use igniteui-angular-theming instead.
development
Quick-reference for running Ignite UI for Angular test suites. Covers the full test run (`test:lib`), grid-specific suites (grid, tree-grid, hierarchical-grid, pivot-grid), non-grid tests, watch mode, and auxiliary test suites (schematics, styles, i18n). Use when an agent needs to run, select, or understand the test infrastructure. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for linting — use igniteui-angular-linting instead.
development
Quick-reference for linting the core Ignite UI for Angular library. Covers the combined lint command (`lint:lib`), ESLint for TypeScript and templates, and Stylelint for Sass/SCSS styles. Use when an agent needs to run the main linters, fix lint errors, or understand the primary lint configuration. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for running tests — use igniteui-angular-testing instead.