bundle-optimization
Bundle analysis, code splitting, tree shaking, and size optimization.
npx skills add a5c-ai/babysitter --skill bundle-optimization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bundle Optimization Skill Expert assistance for JavaScript bundle optimization. ## Capabilities - Analyze bundle size - Implement code splitting - Configure tree shaking - Optimize dependencies - Set up lazy loading ## Analysis ```bash # webpack-bundle-analyzer npx webpack-bundle-analyzer stats.json # source-map-explorer npx source-map-explorer dist/*.js ``` ## Code Splitting ```typescript // Route-based splitting const Dashboard = lazy(() => import('./pages/Dashboard')); // Library splitting const { Chart } = await import('chart.js'); ``` ## Target Processes - bundle-optimization - performance-improvement - build-optimization
- Capabilities
- Analysis
- Code Splitting
- Target Processes
webpack-bundle-analyzer npx webpack-bundle-analyzer stats.json source-map-explorer npx source-map-explorer dist/*.js
What does the bundle-optimization skill do?
Bundle analysis, code splitting, tree shaking, and size optimization.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill bundle-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
