Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid), covering imports, class names, HTML…
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .claude/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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.
Type 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.
skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .agents/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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.
skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .cursor/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .gemini/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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.
Installs 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).
skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .github/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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.
skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "igniteui-wc-migrate-grid-lite-to-premium" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-migrate-grid-lite-to-premium into .opencode/skills/igniteui-wc-migrate-grid-lite-to-premium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-migrate-grid-lite-to-premium", 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-wc-migrate-grid-lite-to-premium
GitHub stars
170
Token cost
~4.3k tokens
SKILL.md length
853 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT
At a glance
Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid), covering imports, class names, HTML…
Works in 9 steps: Install / Verify the Premium Package → Update Imports and Registration → Update HTML Tags → …
Tasks that involve Agent memory
SKILL.md covers Purpose, MANDATORY AGENT PROTOCOL, When to Migrate and Step 1 - Install / Verify the…, plus 10 more sections
Calls npm
What it does
Igniteui Wc Migrate Grid Lite To Premium is an agent skill from IgniteUI/igniteui-webcomponents. Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid), covering imports, class names, HTML tags, properties, events, templates, sorting, filtering, remote data, and theming API changes. WHEN TO USE: the user wants to upgrade from Grid Lite to the premium grid, or needs enterprise features Grid Lite lacks (editing, selection, paging, grouping, summaries, Excel export, state persistence). WHEN NOT TO USE…
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Agent memory, Excel spreadsheets and Theming and dark mode. It works with Microsoft Excel, Angular, Blazor and Model Context Protocol. The repository describes itself as: Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable… The licence is MIT.
When your agent uses it
Tasks that involve Agent memory
Tasks that involve Excel spreadsheets
Tasks that involve Theming and dark mode
Example prompts
“/igniteui-wc-migrate-grid-lite-to-premium”
Requirements
Node.js
Workflow steps
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 834666d. 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:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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 Wc Migrate Grid Lite To Premium loads about 4.3k tokens when it runs. Until then it costs about 212 tokens; SKILL.md has 853 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~212
When it runs· the whole SKILL.md, loaded when a task matches
~4.3k
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.
Download SKILL.mdSave it as .claude/skills/igniteui-wc-migrate-grid-lite-to-premium/SKILL.md (or your agent's skills folder).
name
igniteui-wc-migrate-grid-lite-to-premium
description
Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite>) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid>), covering imports, class names, HTML tags, properties, events, templates, sorting, filtering, remote data, and theming API changes. WHEN TO USE: the user wants to upgrade from Grid Lite to the premium grid, or needs enterprise features Grid Lite lacks (editing, selection, paging, grouping, summaries, Excel export, state persistence). WHEN NOT TO USE: starting a new grid from scratch (use choose-components), migrating between other grids (Tree Grid, Hierarchical Grid, Pivot Grid) or across major versions of the same package, the project uses igniteui-angular or Blazor grids, or the user only needs theming (use customize-component-theme).
license
MIT
user-invocable
true
Migrate from Grid Lite to Premium Data Grid (Web Components)
Purpose
This skill automates the migration from Grid Lite (igniteui-grid-lite, MIT licensed, <igc-grid-lite>) to the Premium Data Grid (igniteui-webcomponents-grids, commercially licensed, <igc-grid>). Use it when a project outgrows Grid Lite's read-only capabilities and needs enterprise features such as editing, selection, paging, grouping, summaries, Excel export, or state persistence.
MANDATORY AGENT PROTOCOL
DO NOT write any code from memory. Grid APIs change between versions.
Before producing migration code:
Identify the current Grid Lite usage - read the user's existing TypeScript and HTML files to understand their column configuration, cell templates, data binding, and any dataPipelineConfiguration usage.
Use the MCP server - call mcp_igniteui-cli_get_api_reference or mcp_igniteui-cli_get_doc (framework: webcomponents) to verify current API details when in doubt.
Only then produce output - base all code on verified references, not memory.
When to Migrate
Migrate from Grid Lite to the Premium Grid when the user needs any of these features:
Required Feature
Grid Lite
Premium Grid
Cell / Row / Batch editing
No
Yes
Row adding / deleting
No
Yes
Row / Cell / Column selection
No
Yes
Paging (client or remote)
No
Yes
GroupBy
No
Yes
Summaries (built-in & custom)
No
Yes
Column pinning
No
Yes
Column moving
No
Yes
Master-Detail rows
No
Yes
Export (Excel / CSV)
No
Yes
Toolbar
No
Yes
State persistence
No
Yes
Advanced filtering
No
Yes
Action strip
No
Yes
Row drag
No
Yes
Clipboard support
No
Yes
Cell merging
No
Yes
IMPORTANT: The upgrade path from Grid Lite is always to IgcGridComponent (<igc-grid>). Never recommend a different component type as a substitute.
Step 1 - Install / Verify the Premium Package
Grid Lite uses the separate igniteui-grid-lite npm package. The Premium Grid ships in igniteui-webcomponents-grids (or @infragistics/igniteui-webcomponents-grids for licensed builds).
AGENT INSTRUCTION: Check package.json to determine which package variant is installed. If only igniteui-grid-lite is present, the user needs to install the premium package.
import { IgcGridLite, IgcGridLiteColumn } from 'igniteui-grid-lite';
import type { BaseIgcCellContext } from 'igniteui-grid-lite';
import 'igniteui-webcomponents/themes/light/bootstrap.css';
After (Premium Grid):
typescript
// Side-effect import - registers all premium grid custom elements; must come first
import 'igniteui-webcomponents-grids/grids/combined.js';
// Type imports
import type {
IgcGridComponent,
IgcColumnComponent,
IgcCellTemplateContext,
IgcColumnTemplateContext,
IgcSortingEventArgs,
IgcFilteringEventArgs,
IgcRowSelectionEventArgs,
IgcSortingExpression,
} from 'igniteui-webcomponents-grids';
// Value imports
import {
SortingDirection,
IgcStringFilteringOperand,
IgcNumberFilteringOperand,
IgcBooleanFilteringOperand,
IgcDateFilteringOperand,
IgcFilteringExpressionsTree,
FilteringLogic,
IgcNoopSortingStrategy,
IgcNoopFilteringStrategy,
} from 'igniteui-webcomponents-grids';
// Theme — import as an inline string so it can be injected into the shadow root (requires bundler support for ?inline, e.g. Vite)
// Available: light|dark x bootstrap|material|fluent|indigo
import gridTheme from 'igniteui-webcomponents-grids/grids/themes/light/material.css?inline';
Grid inside a Shadow root — required step: A bare CSS import lands in the document head and never reaches inside a Shadow root — the grid's internal structure and elements get no styles. Inject the theme as a <style> tag inside the shadow root. For a LitElement component, at the top of render():
<!-- height is required for row virtualization; set it here or on a fixed-height parent -->
<igc-grid id="grid" auto-generate="true" allow-filtering="true" height="600px">
<igc-column field="name" sortable="true" filterable="true" resizable="true"></igc-column>
<igc-column field="price" data-type="number" sortable="true"></igc-column>
</igc-grid>
Note:allow-filtering="true" on <igc-grid> is required to enable filtering. Grid Lite had no grid-level filter toggle.
Step 4 - Update TypeScript References
typescript
// Before
const grid = document.getElementById('grid') as IgcGridLite;
const column = document.querySelector('igc-grid-lite-column[field="name"]') as IgcGridLiteColumn;
// After
const grid = document.getElementById('grid') as IgcGridComponent;
const column = document.querySelector('igc-column[field="name"]') as IgcColumnComponent;
// grid.data = myArray - unchanged
Show full SKILL.md (410 more words)Show less
Step 5 - Migrate Column Properties
Grid Lite Property
Premium Grid Property
Notes
field
field
Unchanged
header
header
Unchanged
width
width
Unchanged
hidden
hidden
Unchanged
resizable
resizable
Unchanged
sortable
sortable
Unchanged
filterable
filterable
Unchanged
dataType
dataType
Premium adds dateTime, time, currency, percent
filteringCaseSensitive
filteringIgnoreCase
Logic inverted - true becomes false
sortingCaseSensitive
sortingIgnoreCase
Logic inverted - true becomes false
sortConfiguration: { comparer }
sortStrategy
Object with a sort(...) method (see below) - no base class to extend
The Premium Grid has no exported base class for sort strategies: IgcSortingStrategy is
exported as a type only, and the built-in default strategy is internal. A column's sortStrategy is any object with this method:
It receives the whole data array and returns it sorted. Read cell values through
valueResolver, not record[fieldName], so nested fields (e.g. address.city) and
date/time columns work.
typescript
// Before (Grid Lite) - function comparer on column
column.sortConfiguration = { comparer: (a, b) => a.length - b.length };
// After (Premium Grid) - object implementing sort()
import { SortingDirection } from 'igniteui-webcomponents-grids';
class LengthSort {
sort(data: any[], fieldName: string, dir: SortingDirection, _ignoreCase: boolean,
valueResolver: (record: any, fieldName: string, isDate?: boolean, isTime?: boolean) => any) {
const factor = dir === SortingDirection.Desc ? -1 : 1;
const len = (record: any) => String(valueResolver(record, fieldName) ?? '').length;
return [...data].sort((a, b) => factor * (len(a) - len(b)));
}
}
column.sortStrategy = new LengthSort();
const grid = document.getElementById('grid') as IgcGridComponent;
// Disable built-in sort/filter so the grid does not process data locally
grid.sortStrategy = IgcNoopSortingStrategy.instance();
grid.filterStrategy = IgcNoopFilteringStrategy.instance();
// React to done events and reload data from the server
grid.addEventListener('sortingDone', async () => {
grid.data = await dataService.sortRemote(grid.sortingExpressions);
});
grid.addEventListener('filteringDone', async () => {
grid.data = await dataService.filterRemote(grid.filteringExpressionsTree);
});
Step 8 - Migrate Sort / Filter Events
Grid Lite Event
Premium Grid Event
Notes
sorting
sorting
Same name - both cancellable (e.detail.cancel = true)
sorted
sortingDone
Name changed - CustomEvent<IgcSortingExpression[]>
filtering
filtering
Same name - both cancellable
filtered
filteringDone
Name changed - CustomEvent<IgcFilteringExpressionsTree>
typescript
// Cancel a sort before it applies
grid.addEventListener('sorting', (e: CustomEvent<IgcSortingEventArgs>) => {
e.detail.cancel = true;
});
// React after sort completes
grid.addEventListener('sortingDone', (e: CustomEvent<IgcSortingExpression[]>) => {
console.log('Sorted by', e.detail);
});
// Cancel a filter before it applies
grid.addEventListener('filtering', (e: CustomEvent<IgcFilteringEventArgs>) => {
e.detail.cancel = true;
});
// React after filter completes
grid.addEventListener('filteringDone', (e: CustomEvent<IgcFilteringExpressionsTree>) => {
console.log('Filter tree', e.detail);
});
Note:primary-key is strongly recommended whenever editing, selection, or row-targeted APIs (getRowByKey, row pinning, transactions) are used. Without it the grid falls back to object identity, which breaks across virtualization and remote data.
Igniteui Wc Migrate Grid Lite To Premium 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.
Igniteui Wc Migrate Grid Lite To Premium compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Igniteui Wc Migrate Grid Lite To Premium this skillIgniteUI/igniteui-webcomponents
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…
Writes, fixes, and reviews SvGrid data-grid code in Svelte 5 projects - columns, features, inline editing, filtering, theming with --sg- tokens, server-side data, the built-in AI helpers, and the…
Implement application views from design images (screenshots, mockups, wireframes) using Ignite UI Web Components, with the igniteui-cli and igniteui-theming MCP servers for component discovery…
Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…
Identify the right Ignite UI Web Components (igniteui-webcomponents, grids, charts, dock manager, React wrappers) for a UI requirement and point to official docs, examples, and API references.
Questions about Igniteui Wc Migrate Grid Lite To Premium
What does Igniteui Wc Migrate Grid Lite To Premium do?
Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid), covering imports, class names, HTML…. Igniteui Wc Migrate Grid Lite To Premium is an agent skill from IgniteUI/igniteui-webcomponents. Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid), covering imports, class names, HTML tags, properties, events, templates, sorting, filtering, remote data, and theming API changes.
When should I use Igniteui Wc Migrate Grid Lite To Premium?
Igniteui Wc Migrate Grid Lite To Premium fits situations like: tasks that involve Agent memory; tasks that involve Excel spreadsheets; tasks that involve Theming and dark mode.
How do I install Igniteui Wc Migrate Grid Lite To Premium in Claude Code?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a claude-code`. Or copy the skill folder (skills/igniteui-wc-migrate-grid-lite-to-premium in IgniteUI/igniteui-webcomponents) into .claude/skills/igniteui-wc-migrate-grid-lite-to-premium in your project. Claude Code loads it when a task matches its description.
How do I install Igniteui Wc Migrate Grid Lite To Premium in Codex?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a codex`. Or copy the skill folder (skills/igniteui-wc-migrate-grid-lite-to-premium in IgniteUI/igniteui-webcomponents) into .agents/skills/igniteui-wc-migrate-grid-lite-to-premium in your project. Codex loads it when a task matches its description.
Can I use Igniteui Wc Migrate Grid Lite To Premium 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-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -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-wc-migrate-grid-lite-to-premium, .gemini/skills/igniteui-wc-migrate-grid-lite-to-premium, .github/skills/igniteui-wc-migrate-grid-lite-to-premium and .opencode/skills/igniteui-wc-migrate-grid-lite-to-premium in your project.
What does Igniteui Wc Migrate Grid Lite To Premium need to run?
Going by SKILL.md and its folder, Igniteui Wc Migrate Grid Lite To Premium needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Igniteui Wc Migrate Grid Lite To Premium access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Igniteui Wc Migrate Grid Lite To Premium 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 Wc Migrate Grid Lite To Premium use?
Igniteui Wc Migrate Grid Lite To Premium 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 Wc Migrate Grid Lite To Premium use?
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Igniteui Wc Migrate Grid Lite To Premium?
Skills that share tags, products or a category with Igniteui Wc Migrate Grid Lite To Premium: Igniteui Angular Grids (IgniteUI/igniteui-angular, 599 stars), Pullmd (AeternaLabsHQ/pullmd, 486 stars), Mineru (Nebutra/MinerU-Skill, 123 stars) and Svgrid (sv-grid/sv-grid, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Igniteui Wc Migrate Grid Lite To Premium?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-webcomponents, which has 170 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 9, 2026.