Ssr Boost Migrate
Lomray-Software/vite-ssr-boost
Migrate an existing Vite and React Router SPA to vite-ssr-boost SSR in Data mode, preserving route objects and checking streaming, hydration, bundle size, and deployment readiness.
Reduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents…
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-size --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .claude/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.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/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .claude/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
$skill-installer install https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-sizeType 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.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-size --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .agents/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .agents/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-size --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .cursor/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .cursor/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
$ gemini skills install https://github.com/IgniteUI/igniteui-webcomponents.git --path skills/igniteui-wc-optimize-bundle-size--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-size --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .gemini/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .gemini/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-sizeInstalls 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).
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .github/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .github/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-optimize-bundle-size --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/igniteui-wc-optimize-bundle-size .opencode/skills/igniteui-wc-optimize-bundle-size && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-wc-optimize-bundle-size" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-optimize-bundle-size into .opencode/skills/igniteui-wc-optimize-bundle-size/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-optimize-bundle-size", 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.
igniteui-wc-optimize-bundle-sizeReduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents…
Igniteui Wc Optimize Bundle Size is an agent skill from IgniteUI/igniteui-webcomponents. Reduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents, lazy-loading heavy components, and verifying tree-shaking with bundle analysis. WHEN TO USE: the user reports a large bundle or slow load, asks how to import components individually, wants to lazy-load grids, charts, or dock manager, or needs to audit Ignite UI imports in Vite/webpack/Rollup builds. WHEN NOT TO USE: initial…
Its SKILL.md is about 3.6k 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 Frontend & Design, covering Web performance. It works with Vite, webpack and React. 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.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a6f3e2c. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
npmjs.comgithub.comwebpack.js.orgvitejs.devweb.devbundlephobia.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Igniteui Wc Optimize Bundle Size loads about 3.6k tokens when it runs. Until then it costs about 204 tokens; SKILL.md has 848 words of instructions outside code blocks.
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.
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.
The full file from IgniteUI/igniteui-webcomponents at commit a6f3e2c, republished under its MIT licence (© IgniteUI). 848 words, ~3,554 tokens.
.claude/skills/igniteui-wc-optimize-bundle-size/SKILL.md (or your agent's skills folder).This skill helps users minimize their application's bundle size when using Ignite UI Web Components by importing only the components they need and following best practices for tree-shaking.
defineAllComponents()// DON'T DO THIS - imports ALL components (~500KB+)
import { defineAllComponents } from 'igniteui-webcomponents';
defineAllComponents();Impact: Includes all 60+ components whether you use them or not.
// DO THIS - import only what you need
import {
defineComponents,
IgcButtonComponent,
IgcInputComponent,
IgcCardComponent
} from 'igniteui-webcomponents';
defineComponents(IgcButtonComponent, IgcInputComponent, IgcCardComponent);Impact: Bundle includes only 3 components and their dependencies.
If you're using React, consider using the igniteui-react package instead of igniteui-webcomponents. It provides the same components with React-friendly wrappers and typically results in better tree-shaking:
npm install igniteui-reactimport { IgrButton, IgrInput, IgrCard } from 'igniteui-react';
// No need to call defineComponents - components register automatically
function MyComponent() {
return (
<div>
<IgrButton variant="contained">Click me</IgrButton>
<IgrInput label="Name" />
<IgrCard>Content</IgrCard>
</div>
);
}Benefits for bundle size:
For more details, see the igniteui-wc-integrate-with-framework skill.
Use a bundle analyzer to identify what's being included before and after optimization.
Vite projects — rollup-plugin-visualizer:
npm install --save-dev rollup-plugin-visualizerAdd visualizer() to the Vite plugins array and run npm run build. The plugin opens a treemap in the browser.
Webpack projects — webpack-bundle-analyzer:
npm install --save-dev webpack-bundle-analyzerAdd BundleAnalyzerPlugin to webpack.config.js plugins and run npm run build.
Framework-agnostic — source-map-explorer:
npm install --save-dev source-map-explorer
# Then: source-map-explorer 'dist/**/*.js'Search your codebase for component usage:
# Search for component tags in templates
grep -r "igc-" src/ --include="*.html" --include="*.tsx" --include="*.vue"
# List unique components
grep -roh "igc-[a-z-]*" src/ | sort | uniqCheck what you're importing vs what you're using:
// Find in your code
import {
defineComponents,
IgcButtonComponent,
IgcInputComponent,
IgcCardComponent,
IgcSelectComponent, // ← Are you using this?
IgcComboComponent, // ← Are you using this?
} from 'igniteui-webcomponents';Remove components you're not using:
// Before: 5 components imported
import {
defineComponents,
IgcButtonComponent,
IgcInputComponent,
IgcCardComponent,
IgcSelectComponent,
IgcComboComponent,
} from 'igniteui-webcomponents';
defineComponents(
IgcButtonComponent,
IgcInputComponent,
IgcCardComponent,
IgcSelectComponent,
IgcComboComponent
);
// After: Only 3 components needed
import {
defineComponents,
IgcButtonComponent,
IgcInputComponent,
IgcCardComponent,
} from 'igniteui-webcomponents';
defineComponents(IgcButtonComponent, IgcInputComponent, IgcCardComponent);Load components only when needed to reduce initial bundle size.
// Load immediately (increases initial bundle)
import { defineComponents, IgcDialogComponent } from 'igniteui-webcomponents';
defineComponents(IgcDialogComponent);
// Lazy load (smaller initial bundle)
async function showDialog() {
const { defineComponents, IgcDialogComponent } = await import('igniteui-webcomponents');
defineComponents(IgcDialogComponent);
const dialog = document.createElement('igc-dialog');
// ... use dialog
}import React, { lazy, Suspense, useState } from 'react';
// Lazy load the dialog component
const IgrDialog = lazy(() =>
import('igniteui-react').then(module => ({ default: module.IgrDialog }))
);
function MyComponent() {
const [showDialog, setShowDialog] = useState(false);
return (
<>
<button onClick={() => setShowDialog(true)}>Open Dialog</button>
{showDialog && (
<Suspense fallback={<div>Loading...</div>}>
<IgrDialog open>
<h2>Dialog Content</h2>
</IgrDialog>
</Suspense>
)}
</>
);
}import React, { useState } from 'react';
// Lazy load component registration
const lazyLoadDialog = async () => {
const { defineComponents, IgcDialogComponent } = await import('igniteui-webcomponents');
defineComponents(IgcDialogComponent);
};
function MyComponent() {
const [dialogReady, setDialogReady] = useState(false);
const openDialog = async () => {
if (!dialogReady) {
await lazyLoadDialog();
setDialogReady(true);
}
// Show dialog
};
return (
<button onClick={openDialog}>Open Dialog</button>
);
}<script setup lang="ts">
import { ref } from 'vue';
const dialogReady = ref(false);
async function openDialog() {
if (!dialogReady.value) {
const { defineComponents, IgcDialogComponent } = await import('igniteui-webcomponents');
defineComponents(IgcDialogComponent);
dialogReady.value = true;
}
// Show dialog
}
</script>
<template>
<button @click="openDialog">Open Dialog</button>
<igc-dialog v-if="dialogReady" open>
<h2>Dialog Content</h2>
</igc-dialog>
</template>import { Component } from '@angular/core';
@Component({
selector: 'app-my-component',
template: `
<button (click)="openDialog()">Open Dialog</button>
<igc-dialog *ngIf="dialogReady" [open]="true">
<h2>Dialog Content</h2>
</igc-dialog>
`
})
export class MyComponent {
dialogReady = false;
async openDialog() {
if (!this.dialogReady) {
const { defineComponents, IgcDialogComponent } = await import('igniteui-webcomponents');
defineComponents(IgcDialogComponent);
this.dialogReady = true;
}
}
}Load Ignite UI components only for the routes that need them by placing defineComponents(...) calls inside the lazy-loaded route module for each framework.
Put component imports and defineComponents at the top of each page module. React's lazy() + Suspense handles the async split:
// pages/Dashboard.tsx
import { IgrCard, IgrButton } from 'igniteui-react';
function Dashboard() {
return (
<div>
<IgrCard>
<h2>Dashboard</h2>
<p>Dashboard content here</p>
</IgrCard>
</div>
);
}Refer to your router's lazy-loading docs (React Router, TanStack Router, etc.) for how to split pages/Dashboard into its own chunk.
Use onMounted to register components only when the route mounts:
<script setup lang="ts">
import { onMounted } from 'vue';
onMounted(async () => {
// Load components only for this route
const { defineComponents, IgcCardComponent } = await import('igniteui-webcomponents');
defineComponents(IgcCardComponent);
});
</script>Refer to Vue Router docs for the () => import('./views/Dashboard.vue') lazy-route syntax.
Place defineComponents(...) inside the route's module or component so it's included only in that lazy chunk. Refer to Angular Router docs for loadChildren / loadComponent lazy loading.
Ensure your build tool is running in production mode with minification enabled. For Vite, this is the default for vite build. For Webpack, set mode: 'production'.
To reduce chunk-size warnings from Ignite UI components, increase the chunkSizeWarningLimit in Vite or configure splitChunks in Webpack to place igniteui-* packages in a named vendor chunk. Consult your build tool's documentation for the exact configuration options.
Actual sizes depend heavily on which components you import (grid and chart components are significantly larger than UI components). Use your bundle analyzer to measure the real impact in your project rather than relying on generic estimates.
The key rule: importing a subset of components with defineComponents() instead of defineAllComponents() will reduce the bundle by the weight of every component you don't include, plus all of their exclusive dependencies.
defineAllComponents() unless you truly need every componentdefineComponents() with specific components you needInvestigate:
igniteui-react instead of igniteui-webcomponentsSolutions:
// Review your imports - are you using all of these?
import {
defineComponents,
IgcButtonComponent,
IgcInputComponent,
IgcSelectComponent,
IgcComboComponent,
IgcDatePickerComponent
} from 'igniteui-webcomponents';
// Consider lazy loading components you don't need immediately
async function loadDialog() {
const { defineComponents, IgcDialogComponent } = await import('igniteui-webcomponents');
defineComponents(IgcDialogComponent);
}Cause: Forgot to import a component you're using
Solution:
// Error: <igc-button> not working
// You're using igc-button but didn't import it
import { defineComponents, IgcButtonComponent } from 'igniteui-webcomponents';
defineComponents(IgcButtonComponent); // Add thisSolution: Update type imports:
// Import types separately if needed
import type { IgcButtonComponent } from 'igniteui-webcomponents';For ongoing bundle size monitoring in CI, tools like bundlesize, size-limit, or the Bundlewatch GitHub Action can fail a pull request when the bundle exceeds a defined threshold. Configure a size limit appropriate for your project's component set after you've completed the import optimization.
© IgniteUI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/igniteui-wc-optimize-bundle-size of IgniteUI/igniteui-webcomponents.
Open the folder on GitHubat commit a6f3e2c
Igniteui Wc Optimize Bundle Size 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Igniteui Wc Optimize Bundle Size this skillIgniteUI/igniteui-webcomponents | 170 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Ssr Boost MigrateLomray-Software/vite-ssr-boost | 118 | — | ~2.3k | Automated safety check: Pass | MIT | |
| React Best Practicesryokun6/ryos | 1.3k | — | ~2k | Automated safety check: Pass | MIT | |
| Sentry React SDKgetsentry/sentry-for-ai | 268 | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Frontend Engineer Workflownanocoai/nanoclaw | 31k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Phy Bundle Size AuditLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Lomray-Software/vite-ssr-boost
Migrate an existing Vite and React Router SPA to vite-ssr-boost SSR in Data mode, preserving route objects and checking streaming, hydration, bundle size, and deployment readiness.
ryokun6/ryos
React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).
getsentry/sentry-for-ai
Full Sentry SDK setup for React. An agent skill from getsentry/sentry-for-ai.
nanocoai/nanoclaw
Sets a build, test and verify routine for web projects: write typed, accessible code and never call work done until it is checked in a real browser with screenshots.
LeoYeAI/openclaw-master-skills
JavaScript bundle size auditor and budget enforcer. An agent skill from LeoYeAI/openclaw-master-skills.
ericrisco/rsc-harness
A skill your agent uses when building, reviewing, testing, securing, or optimizing a Next.js App Router app: Server vs Client boundaries, use server actions, route handlers, the v15 vs v16 use cache…
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.
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…
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…
IgniteUI/igniteui-webcomponents
Add a reactive property to an existing Lit web component with proper decorators, types, tests, specification updates, and documentation
IgniteUI/igniteui-webcomponents
Create a new Lit web component following project conventions, including specification, component class, styles, tests, Storybook story, and exports
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.
Categories
Reduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents…. Igniteui Wc Optimize Bundle Size is an agent skill from IgniteUI/igniteui-webcomponents. Reduce application bundle size with Ignite UI Web Components by registering only needed components via named imports from the package root with defineComponents instead of defineAllComponents, lazy-loading heavy components, and verifying tree-shaking with bundle analysis.
Igniteui Wc Optimize Bundle Size fits situations like: tasks that involve Web performance.
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a claude-code`. Or copy the skill folder (skills/igniteui-wc-optimize-bundle-size in IgniteUI/igniteui-webcomponents) into .claude/skills/igniteui-wc-optimize-bundle-size in your project. Claude Code loads it when a task matches its description.
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-optimize-bundle-size -a codex`. Or copy the skill folder (skills/igniteui-wc-optimize-bundle-size in IgniteUI/igniteui-webcomponents) into .agents/skills/igniteui-wc-optimize-bundle-size in your project. Codex loads it when a task matches its description.
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-optimize-bundle-size -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-optimize-bundle-size, .gemini/skills/igniteui-wc-optimize-bundle-size, .github/skills/igniteui-wc-optimize-bundle-size and .opencode/skills/igniteui-wc-optimize-bundle-size in your project.
Going by SKILL.md and its folder, Igniteui Wc Optimize Bundle Size needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
SKILL.md names 6 domains. As links in the text: npmjs.com, github.com, webpack.js.org, vitejs.dev, web.dev and bundlephobia.com. This is read from the text; nothing was executed.
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.
Igniteui Wc Optimize Bundle Size is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Igniteui Wc Optimize Bundle Size: Ssr Boost Migrate (Lomray-Software/vite-ssr-boost, 118 stars), React Best Practices (ryokun6/ryos, 1.3k stars), Sentry React SDK (getsentry/sentry-for-ai, 268 stars) and Frontend Engineer Workflow (nanocoai/nanoclaw, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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 7, 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.