igniteui-webcomponents

Implement application views from design images using Ignite UI Web Components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working view with Ignite UI Web Components. Also triggers when the user asks to "implement this design", "build this UI", "convert this mockup", or "create a page from this image" in an Ignite UI Web Components project.

Step-by-step migration guide from igniteui-grid-lite (IgcGridLite) to the premium igniteui-webcomponents-grids (IgcGridComponent), covering every import, class name, HTML tag, property, event, template, sorting, filtering, and theming API change.

Identify and select the right Ignite UI Web Components for your app UI, then navigate to official docs, usage examples, and API references

Customize Ignite UI Web Components styling using CSS custom properties, optional Sass, and the igniteui-theming MCP server for AI-assisted theming

Optimize application bundle size by importing only necessary components and using tree-shaking effectively

Integrate Ignite UI Web Components packages into React, Angular, Vue, or vanilla JS applications with framework-specific configurations

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

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

Comprehensive code review checklist for component pull requests ensuring quality, accessibility, and adherence to project conventions

Update component styling following the SCSS to Lit CSS workflow with proper theme support