Igniteui Angular Components logo

Igniteui Angular Components

Organization
IgniteUI
igniteui-angular-components

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. WHEN TO USE: 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. WHEN NOT TO USE: data grids, tables, or tabular data (use igniteui-angular-grids); theming or styling (use igniteui-angular-theming).

Overview

PublisherIgniteUI
Repositoryigniteui-angular
Skill nameigniteui-angular-components
Stars
599
Forks
161
Bundled files
9
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by IgniteUI on GitHub. Read the source before you install it.

Installation

Install the Igniteui Angular Components AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git /tmp/igniteui-angular
mkdir -p .claude/skills
cp -r /tmp/igniteui-angular/skills/igniteui-angular-components .claude/skills/igniteui-angular-components
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Igniteui Angular Components in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Igniteui Angular Components on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Igniteui Angular Components is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 (required)

The igniteui-cli MCP server is the version-accurate source for Ignite UI APIs. It 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 every member-level lookup. For everything else, the reference files below are the primary guidance.

Verify the server before any other step by calling list_components with framework: "angular". If the tool is not available:

  1. Configure it yourself — do not just suggest it. From the project root, run npx -y igniteui-cli ai-config (or ig ai-config when igniteui-cli is installed globally). It configures both the igniteui-cli and igniteui-theming MCP servers, preserves existing server entries, and copies the Agent Skills. If the client is not covered, add the entries manually from references/mcp-setup.md — the server command is npx -y igniteui-cli mcp (or ig mcp).
  2. Ask the user to reload the editor or agent session, then stop. MCP tools cannot be loaded into a running session.
  3. Continue without the server only if the user explicitly asks to. In that case, use the reference files and mark every selector, import path, and member name you could not verify through the MCP server as unverified.

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/search_api. Never guess — if the MCP server cannot answer it, state explicitly that the detail is unverified.

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.


Related Skills

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Igniteui Angular Components AI skill do?

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. WHEN TO USE: users ask about any Ignite...

Why use Igniteui Angular Components on TypingMind?

Because you install it once and use it with any model. Igniteui Angular Components is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Igniteui Angular Components in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Igniteui Angular Components?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Igniteui Angular Components?

As many as you like. As long as a model supports skills, you can use Igniteui Angular Components with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Igniteui Angular Components AI skill free?

Yes. It is published on GitHub by IgniteUI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇