igniteui/igniteui-angular-build
.github/skills/igniteui-angular-build/SKILL.md
Quick-reference for building the core Ignite UI for Angular library and related packages. Covers the full production build (`build:lib`), individual partial builds (styles, extras, migrations, schematics, i18n, elements), and the combined build-all command. Use when an agent needs to compile the library, produce a dist output, or verify that code changes compile cleanly. Do NOT use for running tests — use igniteui-angular-testing instead. Do NOT use for linting — use igniteui-angular-linting instead.
$ install --global
skillsauthnpx skillsauth add igniteui/igniteui-angular igniteui-angular-buildInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 8:05 PM13.8s1 file scanned
SKILL.md
- name:
- igniteui-angular-build
- description:
- Quick-reference for building the core Ignite UI for Angular library and related packages. Covers the full production build (`build:lib`), individual partial builds (styles, extras, migrations, schematics, i18n, elements), and the combined build-all command. Use when an agent needs to compile the library, produce a dist output, or verify that code changes compile cleanly. Do NOT use for running tests — use igniteui-angular-testing instead. Do NOT use for linting — use igniteui-angular-linting instead.
- user-invocable:
- true
Ignite UI for Angular — Build
Quick-reference card for the core library and related build commands in this repository.
Prerequisites
- Run
npm installat the repo root before any build command.
Full Build
npm run build
Runs all sub-builds in sequence (library, elements, schematics, migrations, i18n, extras). Use this when you need a complete publishable output or before running the full CI pipeline locally. Check package.json for the exact sequence.
Library Build (most common)
npm run build:lib
This is the primary build command. It does two things:
ng build igniteui-angular --configuration production— compiles the library with ng-packagr using Angular Package Format. Usesng-package.prod.json(production config).npm run build:styles— runsnode scripts/build-styles.mjsto compile and bundle Sass themes into distributable CSS.
Output: dist/igniteui-angular/
When to use build:lib
- After implementing a feature or fix, to verify the code compiles.
- Before checking that new public symbols are correctly exported.
- When another project needs to consume a local build of the library.
Partial Builds
| Command | What it does |
|---|---|
| npm run build:styles | Compiles Sass themes only (scripts/build-styles.mjs). Already included in build:lib. |
| npm run build:extras | Builds the extras package and then runs extras migrations. |
| npm run build:schematics | Copies and compiles ng add schematics (projects/igniteui-angular/schematics/). |
| npm run build:migrations | Copies and compiles ng update migration schematics (projects/igniteui-angular/migrations/). |
| npm run build:i18n | Compiles the i18n package (projects/igniteui-angular-i18n/). |
| npm run build:elements | Builds the Angular Elements package + bundling + style copy. |
| npm run build:docs | Generates TypeDoc + SassDoc documentation. |
When to use partial builds
build:schematics— after editing files underprojects/igniteui-angular/schematics/.build:migrations— after editing files underprojects/igniteui-angular/migrations/. Required before runningtest:schematics.build:extras— after editing the extras package or when validating the full rootbuildflow.build:i18n— after changing i18n resource strings.build:elements— when working on the Angular Elements wrapper.
Key Paths
| Path | Purpose |
|---|---|
| projects/igniteui-angular/ | Library source root |
| projects/igniteui-angular/ng-package.prod.json | Production ng-packagr config |
| projects/igniteui-angular/ng-package.json | Dev ng-packagr config (preserves dest) |
| dist/igniteui-angular/ | Build output |
| scripts/build-styles.mjs | Sass theme compilation script |
Related Skills
igniteui-angular-testing— Running testsigniteui-angular-linting— Linting code and styles
Related Skills
igniteui/igniteui-angular-theming
tools
VerifiedTrustedCommunity
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.
598SKILL.mdUpdated Apr 5, 2026
igniteui/igniteui-angular-grids
tools
VerifiedTrustedCommunity
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.
598SKILL.mdUpdated Apr 5, 2026
igniteui/igniteui-angular-components
tools
VerifiedTrustedCommunity
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.
598SKILL.mdUpdated Apr 5, 2026
igniteui/igniteui-angular-testing
development
VerifiedTrustedCommunity
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.
598SKILL.mdUpdated Apr 5, 2026