Agent skill

Igniteui Wc Migrate Grid Lite To Premium

by IgniteUI in 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…

MITAuto-check passedDocuments & Office

Install Igniteui Wc Migrate Grid Lite To Premium

skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-migrate-grid-lite-to-premium -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-migrate-grid-lite-to-premium --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/igniteui-wc-migrate-grid-lite-to-premium .claude/skills/igniteui-wc-migrate-grid-lite-to-premium && rm -rf skills-src

Use ~/.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/

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.

  1. Install / Verify the Premium Package
  2. Update Imports and Registration
  3. Update HTML Tags
  4. Update TypeScript References
  5. Migrate Column Properties
  6. Migrate Cell and Header Templates
  7. Migrate Remote Data Operations
  8. Migrate Sort / Filter Events
  9. Migrate Programmatic Sort / Filter API

What it can do on your machine

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.

SKILL.md

The full file from IgniteUI/igniteui-webcomponents at commit 834666d, republished under its MIT licence (© IgniteUI). 853 words, ~4,310 tokens.

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:

  1. 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.
  2. 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.
  3. 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 FeatureGrid LitePremium Grid
Cell / Row / Batch editingNoYes
Row adding / deletingNoYes
Row / Cell / Column selectionNoYes
Paging (client or remote)NoYes
GroupByNoYes
Summaries (built-in & custom)NoYes
Column pinningNoYes
Column movingNoYes
Master-Detail rowsNoYes
Export (Excel / CSV)NoYes
ToolbarNoYes
State persistenceNoYes
Advanced filteringNoYes
Action stripNoYes
Row dragNoYes
Clipboard supportNoYes
Cell mergingNoYes

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.

bash
# Remove Grid Lite
npm uninstall igniteui-grid-lite

# Open-source / trial (shows watermark)
npm install igniteui-webcomponents-grids

# OR licensed package (requires private registry)
npm install @infragistics/igniteui-webcomponents-grids

Step 2 - Update Imports and Registration

Before (Grid Lite):

typescript
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():

typescript
render() {
  return html`
    <style>${gridTheme}</style>
    <igc-grid ...></igc-grid>
  `;
}

Step 3 - Update HTML Tags

Grid LitePremium Grid
<igc-grid-lite><igc-grid>
<igc-grid-lite-column><igc-column>
Bare boolean attrs (sortable, filterable, hidden)Quoted values (sortable="true", filterable="true", hidden="true")
No grid-level filter toggleallow-filtering="true" required on <igc-grid>
No height requirementheight attribute required for row virtualization

Before:

html
<igc-grid-lite id="grid" auto-generate>
  <igc-grid-lite-column field="name" sortable filterable resizable></igc-grid-lite-column>
  <igc-grid-lite-column field="price" data-type="number" sortable></igc-grid-lite-column>
</igc-grid-lite>

After:

html
<!-- 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 PropertyPremium Grid PropertyNotes
fieldfieldUnchanged
headerheaderUnchanged
widthwidthUnchanged
hiddenhiddenUnchanged
resizableresizableUnchanged
sortablesortableUnchanged
filterablefilterableUnchanged
dataTypedataTypePremium adds dateTime, time, currency, percent
filteringCaseSensitivefilteringIgnoreCaseLogic inverted - true becomes false
sortingCaseSensitivesortingIgnoreCaseLogic inverted - true becomes false
sortConfiguration: { comparer }sortStrategyObject with a sort(...) method (see below) - no base class to extend
(none)editable, pinned, groupable, hasSummary, disableHiding, disablePinning, selectable, searchable, formatter, minWidth, maxWidthPremium-only

Custom sort strategy migration:

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:

typescript
sort(data: any[], fieldName: string, dir: SortingDirection, ignoreCase: boolean,
     valueResolver: (record: any, fieldName: string, isDate?: boolean, isTime?: boolean) => any): any[]

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

Step 6 - Migrate Cell and Header Templates

AspectGrid LitePremium Grid
Cell template propertycolumn.cellTemplatecolumn.bodyTemplate
Cell context typeBaseIgcCellContextIgcCellTemplateContext
Cell valuectx.valuectx.implicit
Row datactx.rowctx.cell.row.data
Header templateno paramsIgcColumnTemplateContext param

Cell template migration:

typescript
// Before (Grid Lite)
column.cellTemplate = (ctx) => html`<span class=${ctx.value}>${ctx.value}</span>`;

// After (Premium Grid)
column.bodyTemplate = (ctx: IgcCellTemplateContext) =>
  html`<span class=${ctx.implicit}>${ctx.implicit}</span>`;

Header template migration:

typescript
// Before (Grid Lite) - no parameters
column.headerTemplate = () => html`<strong>Name</strong>`;

// After (Premium Grid) - receives IgcColumnTemplateContext
column.headerTemplate = (ctx: IgcColumnTemplateContext) =>
  html`<strong>${ctx.column.header ?? ctx.column.field}</strong>`;

Step 7 - Migrate Remote Data Operations

Grid Lite uses dataPipelineConfiguration (async callbacks). The Premium Grid uses noop strategies + events.

Before (Grid Lite):

typescript
grid.dataPipelineConfiguration = {
  sort:   async ({ grid }) => dataService.sortRemote(grid.sortingExpressions),
  filter: async ({ grid }) => dataService.filterRemote(grid.filterExpressions),
};

After (Premium Grid):

typescript
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 EventPremium Grid EventNotes
sortingsortingSame name - both cancellable (e.detail.cancel = true)
sortedsortingDoneName changed - CustomEvent<IgcSortingExpression[]>
filteringfilteringSame name - both cancellable
filteredfilteringDoneName 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);
});

Step 9 - Migrate Programmatic Sort / Filter API

Grid Lite API:

typescript
grid.sort({ key: 'name', direction: 'ascending' });
grid.filter({ key: 'age', condition: 'greaterThan', searchTerm: 21 });
grid.clearSort();
grid.clearFilter();

Premium Grid API:

typescript
import { SortingDirection, IgcNumberFilteringOperand } from 'igniteui-webcomponents-grids';

// Sorting - fieldName + SortingDirection enum (Asc = 1, Desc = 2, None = 0)
grid.sort([{ fieldName: 'name', dir: SortingDirection.Asc, ignoreCase: true }]);
grid.clearSort('name');   // clear one column
grid.clearSort();           // clear all

// Filtering - positional arguments with typed operand instances
grid.filter('age', 21, IgcNumberFilteringOperand.instance().condition('greaterThan'), true);
grid.clearFilter('age');   // clear one column
grid.clearFilter();          // clear all

// Multi-column filtering via expression tree
const tree = new IgcFilteringExpressionsTree(FilteringLogic.And);
tree.filteringOperands.push({
  fieldName: 'age',
  condition: IgcNumberFilteringOperand.instance().condition('greaterThan'),
  searchVal: 21,
  ignoreCase: true,
});
grid.filteringExpressionsTree = tree;

Key expression shape changes:

AspectGrid LitePremium Grid
Sort target fieldkeyfieldName
Sort directiondirection: 'ascending' (string)dir: SortingDirection.Asc (enum)
Filter target fieldkeyfieldName
Filter search valuesearchTermsearchVal (expression tree)
Case sensitivity (sort)caseSensitive: trueignoreCase: false (inverted)
Case sensitivity (filter)caseSensitive: trueignoreCase: false (inverted)
Filter criteriacriteria stringFilteringLogic enum on the tree

Adding Enterprise Features Post-Migration

Once on the Premium Grid, enable the features that motivated the migration:

Row Editing
html
<igc-grid id="grid" row-editable="true" primary-key="id" height="600px">
  <igc-column field="name" editable="true"></igc-column>
  <igc-column field="price" data-type="number" editable="true"></igc-column>
</igc-grid>

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.

Row Selection
html
<igc-grid id="grid" row-selection="multiple" primary-key="id" height="600px">
  <!-- columns -->
</igc-grid>
typescript
grid.addEventListener('rowSelectionChanging', (e: CustomEvent<IgcRowSelectionEventArgs>) => {
  console.log('Selected rows:', e.detail.added);
});
Paging
html
<igc-grid id="grid" primary-key="id" height="600px">
  <!-- columns -->
  <igc-paginator per-page="15"></igc-paginator>
</igc-grid>
GroupBy
html
<igc-grid id="grid" primary-key="id" height="600px">
  <igc-column field="category" groupable="true"></igc-column>
</igc-grid>
typescript
grid.groupBy([{ fieldName: 'category', dir: SortingDirection.Asc }]);
Column Pinning
typescript
const column = grid.getColumnByName('name');
column.pin();    // pin to start (default)
column.unpin();
Summaries
html
<igc-column field="price" data-type="number" has-summary="true"></igc-column>
Toolbar (Column Hiding, Pinning, Export)
html
<igc-grid id="grid" auto-generate="true" height="600px">
  <igc-grid-toolbar>
    <igc-grid-toolbar-title>My Grid</igc-grid-toolbar-title>
    <igc-grid-toolbar-actions>
      <igc-grid-toolbar-advanced-filtering></igc-grid-toolbar-advanced-filtering>
      <igc-grid-toolbar-hiding></igc-grid-toolbar-hiding>
      <igc-grid-toolbar-pinning></igc-grid-toolbar-pinning>
      <igc-grid-toolbar-exporter></igc-grid-toolbar-exporter>
    </igc-grid-toolbar-actions>
  </igc-grid-toolbar>
  <!-- columns -->
</igc-grid>
Advanced Filtering Dialog
typescript
grid.allowAdvancedFiltering = true;
grid.openAdvancedFilteringDialog();
Excel-Style Filter UI
typescript
grid.filterMode = 'excelStyleFilter';  // default is 'quickFilter'
Batch Editing
html
<igc-grid id="grid" batch-editing="true" row-editable="true" primary-key="id" height="600px">
  <igc-column field="name" editable="true"></igc-column>
</igc-grid>

© 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

Just SKILL.md in skills/igniteui-wc-migrate-grid-lite-to-premium of IgniteUI/igniteui-webcomponents.

Open the folder on GitHubat commit 834666d

Compare with similar skills

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Igniteui Wc Migrate Grid Lite To Premium this skillIgniteUI/igniteui-webcomponents170—~4.3kAutomated safety check: PassMIT
Igniteui Angular GridsIgniteUI/igniteui-angular599—~2.6kAutomated safety check: PassMIT
PullmdAeternaLabsHQ/pullmd486—~2.6kAutomated safety check: PassAGPL-3.0
MineruNebutra/MinerU-Skill123—~1.4kAutomated safety check: PassMIT
Svgridsv-grid/sv-grid179—~2.6kAutomated safety check: PassCustom licence
Et ExcelFlameskyDexive/Legends-Of-Heroes928—~554Automated safety check: PassMIT

Similar skills

  • Igniteui Angular Grids

    IgniteUI/igniteui-angular

    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…

    599 GitHub stars~2.6k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Pullmd

    AeternaLabsHQ/pullmd

    Read any web page, document, or YouTube video as clean Markdown using PullMD.

    486 GitHub stars~2.6k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into clean Markdown with MinerU — a fast, zero-config document parser for AI agents.

    123 GitHub stars~1.4k tokensUpdated 17 days ago
    Documents & OfficeAuto-check passed
  • Svgrid

    sv-grid/sv-grid

    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…

    179 GitHub stars~2.6k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Et Excel

    FlameskyDexive/Legends-Of-Heroes

    ET Excel MCP workflow for reading, writing, styling, transforming, and inspecting xlsx data.

    928 GitHub stars~554 tokensUpdated 19 days ago
    Documents & OfficeAuto-check passed
  • Library

    crane-in-clear-sky/WorkWit-AI-Agent

    当要写/整理在线文档、建数据表增删改查、导入 CSV·Excel、做看板/dashboard/运营页/汇报页、md 转网页或演示 HTML 发布、建目录、上传下载网盘文件、审阅修订、分享协作,以及提到资料库/知识库/网盘/空间/workbuddy.cn/space 链接时使用。资料库是 WorkBuddy…

    115 GitHub stars~1.5k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

More from IgniteUI/igniteui-webcomponents

All 13 skills in this repo
  • Igniteui Wc Customize Component Theme

    IgniteUI/igniteui-webcomponents

    Theme and style Ignite UI Web Components (and igniteui-react) apps using CSS custom properties, optional Sass, and the igniteui-theming MCP server.

    170 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check passed
  • Igniteui Wc Generate From Image Design

    IgniteUI/igniteui-webcomponents

    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…

    170 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Igniteui Wc Integrate With Framework

    IgniteUI/igniteui-webcomponents

    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…

    170 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Add Component Property

    IgniteUI/igniteui-webcomponents

    Add a reactive property to an existing Lit web component with proper decorators, types, tests, specification updates, and documentation

    170 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Create New Component

    IgniteUI/igniteui-webcomponents

    Create a new Lit web component following project conventions, including specification, component class, styles, tests, Storybook story, and exports

    170 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Igniteui Wc Choose Components

    IgniteUI/igniteui-webcomponents

    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.

    170 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed

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.

Source: IgniteUI/igniteui-webcomponents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.