On-demand performance and optimization analysis. Use when identifying bottlenecks, improving build times, reducing bundle size, or optimizing code performance. Trigger keywords - "optimize", "performance", "bottleneck", "bundle size", "build time", "speed up".
View on GitHubFebruary 5, 2026
Select agents to install to:
npx add-skill https://github.com/MadAppGang/claude-code/blob/main/plugins/dev/skills/optimize/SKILL.md -a claude-code --skill optimizeInstallation paths:
.claude/skills/optimize/# Optimize Skill ## Overview The optimize skill provides comprehensive on-demand performance and optimization analysis for your codebase. It identifies bottlenecks, slow builds, large bundles, inefficient code patterns, and opportunities for performance improvements across all supported technology stacks. **When to Use**: - Performance issues and slow response times - Large bundle sizes and slow page loads - Long build and compile times - High memory usage - Database query optimization - API endpoint performance tuning - CI/CD pipeline optimization **Technology Coverage**: - React/TypeScript/JavaScript (Vite, Webpack, Rollup) - Go applications (build time, runtime performance) - Rust projects (compile time, binary size) - Python codebases (runtime optimization) - Full-stack applications - Database queries (SQL, ORM) ## Optimization Categories ### 1. Build Performance **What Gets Analyzed**: - Build duration and bottlenecks - Dependency resolution time - TypeScript compilation speed - Asset processing (images, fonts) - Code splitting effectiveness - Cache utilization **Common Issues**: - Unnecessary re-builds of unchanged code - Large dependency trees - Inefficient TypeScript configuration - Missing build caching - Redundant asset processing **Optimization Targets**: - Reduce build time by 30-50% - Enable incremental builds - Optimize dependency resolution - Improve cache hit rates ### 2. Bundle Size **What Gets Measured**: - Total bundle size (uncompressed/gzipped) - Individual chunk sizes - Duplicate dependencies - Tree-shaking effectiveness - Unused code in bundles - Third-party library sizes **Bundle Analysis**: ``` Bundle Size Breakdown: ├── vendor.js: 847 KB (312 KB gzipped) │ ├── react-dom: 142 KB │ ├── lodash: 71 KB (should use lodash-es) │ ├── moment: 67 KB (consider date-fns) │ └── ... ├── main.js: 234 KB (89 KB gzipped) └── [lazy chunks]: 156 KB total ``` **Optimization Goals**: - Keep initial bundle under 200 KB (gzipped) - Lazy load