igniteui-angular-components
Helps implement Angular UI components from the Ignite UI library.
Install
mkdir -p .claude/skills/igniteui-angular-components && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7175" && unzip -o skill.zip -d .claude/skills/igniteui-angular-components && rm skill.zipInstalls to .claude/skills/igniteui-angular-components
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Scaffolds UI component implementation
- →Configures reactive form controls
- →Sets up navigation and layout components
- →Integrates with Ignite UI CLI tools
How it works
Directs the user through component scaffolding and provides standard configuration patterns for Angular controls.
Inputs & outputs
When to use igniteui-angular-components
- →Adding form controls
- →Implementing UI navigation
- →Configuring UI layouts
About this skill
Ignite UI for Angular — UI Components
Prerequisites
- An Angular project on the major version matching the installed
igniteui-angularpackage (igniteui-angular majors track Angular majors) @angular/cliinstalledigniteui-angularor@infragistics/igniteui-angularadded to the project viang add igniteui-angular(or the@infragisticsvariant) ornpm install— see Package Variants below.- A theme applied to the application (see
igniteui-angular-theming). provideAnimations()inapp.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.
- 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.mdandfeedback.md). - Read every identified reference file in full, in a single parallel batch of file reads — even if you believe you already know the answer.
- 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_docswhen the MCP tools are available; otherwise state explicitly that the detail is unverified instead of guessing.
Task → Reference File
| 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, Autocomplete, 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.
Package Variants
| 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.
Related Skills
igniteui-angular-grids— Data Grids (Flat Grid, Tree Grid, Hierarchical Grid, Pivot Grid, Grid Lite)igniteui-angular-theming— Theming & Styling
When not to use it
- →Working with Ignite UI data grids
- →Configuring component styling or theming
Prerequisites
Limitations
- →Requires explicit setup of animations
- →Does not cover data grid-specific functionality
How it compares
It is scoped exclusively to non-tabular components, preventing confusion with the grid-heavy Ignite UI library.
Compared to similar skills
igniteui-angular-components side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| igniteui-angular-components (this skill) | 1 | 2mo | No flags | Intermediate |
| Mifos Web App Agent Skills | 0 | 5mo | No flags | Intermediate |
| angular | 100 | 4mo | Review | Advanced |
| angular-state-management | 8 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by igniteui
View all by igniteui →You might also like
Mifos Web App Agent Skills
openMF
Core capabilities and rules for AI agents contributing to the MifosX Web App (Angular).
angular
sickn33
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.
angular-state-management
sickn33
Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.
angular-modernization
bitwarden
Modernizes Angular code such as components and directives to follow best practices using both automatic CLI migrations and Bitwarden-specific patterns. YOU must use this skill when someone requests modernizing Angular code. DO NOT invoke for general Angular discussions unrelated to modernization.
angular-routing
analogjs
Implement routing in Angular v20+ applications with lazy loading, functional guards, resolvers, and route parameters. Use for navigation setup, protected routes, route-based data loading, and nested routing. Triggers on route configuration, adding authentication guards, implementing lazy loading, or reading route parameters with signals.
igniteui-angular-grids
igniteui
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.