igniteui-react-optimize-bundle-size

A guide for reducing the size of a React application that uses Ignite UI, a collection of user-interface components.

In plain words
What is it for?
It covers installing only needed packages, importing specific components so unused code can be removed, and loading large parts such as grids or charts only when needed.
Why use it?
Large bundles can make an application take longer to load, especially when they include components the app does not use.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/igniteui/igniteui-react/igniteui-react-optimize-bundle-size
Any agent
npx skills add IgniteUI/igniteui-react --skill igniteui-react-optimize-bundle-size
Clone the repo
git clone --depth 1 https://github.com/IgniteUI/igniteui-react

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,928 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.02928
Opus 5 $0.00025 $0.01464
Sonnet 5 $0.00010 $0.00586
Haiku 4.5 $0.00005 $0.00293

Measured 2d ago against content hash cd0be380fbcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

igniteui-react-optimize-bundle-size scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to igniteui-react-optimize-bundle-size — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/igniteui-react-optimize-bundle-size/SKILL.md · 440 lines

How it starts

The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Optimize Bundle Size

This skill helps users minimize their React application's bundle size when using Ignite UI for React by importing only the components they need, leveraging tree-shaking, and applying lazy loading strategies.

Example Usage

  • "My bundle size is too large"
  • "How do I reduce the size of igniteui-react?"
  • "Import only the components I need"
  • "Tree-shake unused components"
  • "Optimize imports for production"
  • "How do I lazy load the data grid?"

When to Use

  • Application bundle size is too large
  • User wants to optimize for production
  • User is importing more components than needed
  • User asks about tree-shaking or optimization
  • User wants to improve load times
  • User wants to code-split heavy components like grids or charts

Key Principles

  1. Install only the packages you need — don't install igniteui-react-grids if you only use core UI components
  2. Use named imports — enable tree-shaking by importing specific components
  3. Lazy load heavy components — use React.lazy + Suspense for grids, charts, and other large components
  4. Analyze your bundle — use tools to identify what's being included

Granular Package Imports

Only install the packages you actually use:

Package Contains Install only if you need…
igniteui-react Buttons, inputs, dialogs, calendars, lists, etc. Core UI components
igniteui-react + igniteui-grid-lite Lightweight grid (IgrGridLite from igniteui-react/grid-lite) Simple tabular data (MIT, requires both packages)
igniteui-react-grids DataGrid, TreeGrid, PivotGrid, HierarchicalGrid Advanced data grids (commercial)
igniteui-react-charts Category, Pie, Financial, Scatter charts Charts and data visualization (commercial)
igniteui-react-maps Geographic maps Map visualizations (commercial)
igniteui-react-gauges Radial and linear gauges Gauge indicators (commercial)

Read the full file on GitHub · 440 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 440 lines · 50 tokens per session scan A cd0be380fbcf

Subscribe to this mod's changes

igniteui-react-optimize-bundle-size is a skill published in the GitHub repository IgniteUI/igniteui-react (56 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 2,928 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to igniteui-react-optimize-bundle-size, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

material-ui-review

Review the current diff for regressions, correctness bugs, tests, simplifications, and docs issues, scaling depth to a low/medium/high/xhigh/max effort level. Use ONLY when explicitly requested by name: the user runs /material-ui-review, writes $material-ui-review, or asks for "the Material UI review skill". Do NOT…

mui/material-ui · 137 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

chakra-ui-migrate

Migrate Chakra UI projects from v2 to v3, covering package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Use this skill whenever a user is upgrading Chakra UI versions, encountering breaking changes after an upgrade, converting old v2 patterns…

chakra-ui/chakra-ui · 137 tokens

chakra-ui-refactor

Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…

chakra-ui/chakra-ui · 139 tokens

migrate-v8-to-v9

Complete Angular v8-to-v9 migration reference: injectTable and injection context, explicit features and row-model slots, signal/atom state, FlexRender directives, type generics, prototype methods, sorting, sizing, selection, and logical pinning.

TanStack/table · 58 tokens

cell-selection

Select, add, and subtract rectangular cell ranges with cellSelectionFeature: ordered include/exclude operations keyed by row and column id, modifier dragging, final positive bounds, selection edges, render-order resolution under pinning, and autoResetCellSelection. Load for spreadsheet-style selection, “select all…

TanStack/table · 83 tokens