Use Igniteui Blazor
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor...
Install
npx skills add dotnet/skills --skill use-igniteui-blazor -g -a claude-code -y- Repository
- dotnet/skills5.8k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,162 tokens
- Runs scripts
- No, instructions only
What it does
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
Application Setup & Component Registration
1. NuGet package
Before adding packages, inspect the target projects' target framework and existing package references. The lowest supported target framework version is .NET 8.0. If IgniteUI.Blazor or IgniteUI.Blazor.Trial is already referenced, keep that package strategy and do not add Lite or GridLite. Only switch package families when the user explicitly asks, replacing conflicting references rather than keeping both.
dotnet add package IgniteUI.Blazor.Lite # OSS core UI components (MIT)
dotnet add package IgniteUI.Blazor.GridLite # OSS lightweight grid (MIT)
Use IgniteUI.Blazor.Lite for core controls such as IgbInput, IgbCombo and IgbDialog, and IgniteUI.Blazor.GridLite for the lightweight grid. Reference both packages only when the app needs both. Do not invent per-component packages such as IgniteUI.Blazor.Combo.
Charts, maps, gauges and other premium components are not included in Lite. Check the requested component's package before recommending a reference.
2. IgniteUI.Blazor.Lite Service Registration
Usually in Program.cs:
builder.Services.AddIgniteUIBlazor(); // no modules pre-loaded; each loads on first render
Pass typeof(Igb<Name>Module) values to eagerly pre-load a specific set instead:
builder.Services.AddIgniteUIBlazor(
typeof(IgbInputModule), typeof(IgbComboModule), typeof(IgbDialogModule));
Module names always follow Igb{ComponentName}Module. Passing modules eagerly loads them during startup, increasing the initial transfer to reduce first-render latency. Components not listed still register their own modules on first render.
For a GridLite-only setup, do not call AddIgniteUIBlazor() or add manual Ignite UI script tags. Reference IgniteUI.Blazor.GridLite, add the control namespace, and link the GridLite stylesheet shown below.
