Golemui
golemui/golemui
Build, validate, and debug GolemUI forms in React, Angular, Vue, Lit, or vanilla JS.
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)…
Install Igniteui Angular Components
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-components --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/igniteui-angular-components .claude/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .claude/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-componentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-components --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/igniteui-angular-components .agents/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .agents/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-components --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/igniteui-angular-components .cursor/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .cursor/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/IgniteUI/igniteui-angular.git --path skills/igniteui-angular-components--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-components --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/igniteui-angular-components .gemini/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .gemini/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-componentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/igniteui-angular-components .github/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .github/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgniteUI/igniteui-angular igniteui-angular-components --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/igniteui-angular-components .opencode/skills/igniteui-angular-components && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-angular-components" agent skill from https://github.com/IgniteUI/igniteui-angular/tree/master/skills/igniteui-angular-components into .opencode/skills/igniteui-angular-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-angular-components", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
igniteui-angular-components- GitHub stars
- 599
- Token cost
- ~1.7k tokens
- SKILL.md length
- 690 words
- Files
- 10 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
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)…
- Works in 3 steps: Configure it yourself — do not just… → Ask the user to reload the editor or… → Continue without the server only if the…
- Tasks that involve Theming and dark mode
- SKILL.md covers Prerequisites, Ignite UI CLI MCP Server…, Required Workflow and Package Variants, plus 1 more section
- Calls npm and npx
What it does
Igniteui Angular Components is an agent skill from IgniteUI/igniteui-angular. 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…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/charts.md`, `references/data-display.md` and `references/directives.md`).
It sits in Frontend & Design, covering Theming and dark mode and Project scaffolding. It works with Angular and Model Context Protocol. The repository describes itself as: Ignite UI for Angular is a complete library of Angular UI components with the fastest grids and charts, dock manager, and more. The licence is MIT.
When your agent uses it
- Tasks that involve Theming and dark mode
- Tasks that involve Project scaffolding
Example prompts
- “Use the igniteui-angular-components skill to cover all non-grid Ignite UI for Angular UI components: application scaffolding and setup, form…”
- “/igniteui-angular-components”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Configure it yourself — do not just suggest it. From the project root, run npx -y igniteui-cli ai-config (or ig ai-config when…
- Ask the user to reload the editor or agent session, then stop. MCP tools cannot be loaded into a running session.
- Continue without the server only if the user explicitly asks to. In that case, use the reference files and mark every selector, import…
What it can do on your machine
Read from SKILL.md and the folder at commit 436e825. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Igniteui Angular Components loads about 1.7k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 229 tokens; SKILL.md has 690 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from IgniteUI/igniteui-angular at commit 436e825, republished under its MIT licence (© IgniteUI). 690 words, ~1,694 tokens.
Download SKILL.mdSave it as
.claude/skills/igniteui-angular-components/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- igniteui-angular-components
- description
- 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).
- license
- MIT
- user-invocable
- true
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 (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:
- Configure it yourself — do not just suggest it. From the project root, run
npx -y igniteui-cli ai-config(orig ai-configwhenigniteui-cliis installed globally). It configures both theigniteui-cliandigniteui-themingMCP servers, preserves existing server entries, and copies the Agent Skills. If the client is not covered, add the entries manually fromreferences/mcp-setup.md— the server command isnpx -y igniteui-cli mcp(orig mcp). - Ask the user to reload the editor or agent session, then stop. MCP tools cannot be loaded into a running session.
- 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.
- 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_docs/search_api. Never guess — if the MCP server cannot answer it, state explicitly that the detail is unverified.
Show full SKILL.md (232 more words)Show less
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
© IgniteUI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references) in skills/igniteui-angular-components of IgniteUI/igniteui-angular.
- SKILL.md
- references/charts.md
- references/data-display.md
- references/directives.md
- references/feedback.md
- references/form-controls.md
- references/layout-manager.md
- references/layout.md
- references/mcp-setup.md
- references/setup.md
Open the folder on GitHubat commit 436e825
Compare with similar skills
Igniteui Angular Components next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Igniteui Angular Components this skillIgniteUI/igniteui-angular | 599 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Golemuigolemui/golemui | 113 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Igniteui Wc Figma To AppIgniteUI/igniteui-webcomponents | 170 | — | ~7.2k | Automated safety check: Pass | MIT | |
| MCP Developmentcoollabsio/coolify | 63k | 1 repos | ~949 | Automated safety check: Pass | MIT | |
| UI UX Pro Maxsaoudi-h/solar-icons | 182 | 18 repos | ~11k | Automated safety check: Notes | Custom licence | |
| Create Docsvictorgarciaesgi/nuxt-typed-router | 413 | 2 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Igniteui Wc Figma To App
IgniteUI/igniteui-webcomponents
Builds Ignite UI Web Components views from Figma designs, supporting Indigo.Design kits, third-party kits (Material 3, Fluent 2, shadcn/ui, Untitled UI, in-house), and plain frames.
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
Create Docs
victorgarciaesgi/nuxt-typed-router
Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.
Figma Build
awdr74100/figwright
Build a Figma design from code or a description — the reverse of figma-codegen.
More from IgniteUI/igniteui-angular
All 9 skills in this repoIgniteui Angular Build
IgniteUI/igniteui-angular
Quick-reference for building the core Ignite UI for Angular library and related packages.
Igniteui Angular Linting
IgniteUI/igniteui-angular
Quick-reference for linting the core Ignite UI for Angular library.
Igniteui Angular Generate From Image Design
IgniteUI/igniteui-angular
Implements Angular application views from design images using Ignite UI Angular components.
Igniteui Angular Theming
IgniteUI/igniteui-angular
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.
Igniteui Angular Figma To App
IgniteUI/igniteui-angular
Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames.
Igniteui Angular Testing
IgniteUI/igniteui-angular
Quick-reference for running Ignite UI for Angular test suites.
Related
Works with
Categories
Questions about Igniteui Angular Components
What does Igniteui Angular Components 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)…. Igniteui Angular Components is an agent skill from IgniteUI/igniteui-angular.
When should I use Igniteui Angular Components?
Igniteui Angular Components fits situations like: tasks that involve Theming and dark mode; tasks that involve Project scaffolding.
How do I install Igniteui Angular Components in Claude Code?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a claude-code`. Or copy the skill folder (skills/igniteui-angular-components in IgniteUI/igniteui-angular) into .claude/skills/igniteui-angular-components in your project. Claude Code loads it when a task matches its description.
How do I install Igniteui Angular Components in Codex?
Run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a codex`. Or copy the skill folder (skills/igniteui-angular-components in IgniteUI/igniteui-angular) into .agents/skills/igniteui-angular-components in your project. Codex loads it when a task matches its description.
Can I use Igniteui Angular Components in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add IgniteUI/igniteui-angular --skill igniteui-angular-components -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/igniteui-angular-components, .gemini/skills/igniteui-angular-components, .github/skills/igniteui-angular-components and .opencode/skills/igniteui-angular-components in your project.
What does Igniteui Angular Components need to run?
Going by SKILL.md and its folder, Igniteui Angular Components needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.
Does Igniteui Angular Components access the network?
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Igniteui Angular Components safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Igniteui Angular Components use?
Igniteui Angular Components is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Igniteui Angular Components use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.
What are the alternatives to Igniteui Angular Components?
Skills that share tags, products or a category with Igniteui Angular Components: Golemui (golemui/golemui, 113 stars), Igniteui Wc Figma To App (IgniteUI/igniteui-webcomponents, 170 stars), MCP Development (coollabsio/coolify, 63k stars) and UI UX Pro Max (saoudi-h/solar-icons, 182 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Igniteui Angular Components?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-angular, which has 599 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.
Source: IgniteUI/igniteui-angular on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.