| name | dev-build-optimization |
| description | Use to diagnose or improve build speed, cache behavior, bundle size, packaging output, and monorepo task execution. |
| metadata | {"version":"0.3","updated":"2026-06-12"} |
Build optimization workflow
Use this workflow when a build, bundle, compile, package, or monorepo task is slow, unstable, or too large.
Steps
-
Identify the build surface.
- Package manager, workspace layout, build tool, bundler, compiler, CI job, cache configuration, and output artifact.
-
Establish a baseline.
- Cold build time
- Incremental build time
- Bundle or artifact size
- Cache hit/miss evidence
- Relevant CI logs
-
Find bottlenecks.
- Dependency graph
- Type checking
- Transpilation
- Minification
- Asset handling
- Test execution
- Remote/cache setup
-
Apply targeted improvements.
- Incremental compilation
- Parallel tasks
- Cache configuration
- Tree shaking
- Code splitting
- Dependency dedupe
- Build script simplification
-
Validate before and after.
- Run comparable commands.
- Confirm output still works.
- Check source maps, assets, and package contents when relevant.
Output
Return:
- Baseline
- Bottleneck evidence
- Change summary
- Before/after validation
- Remaining build risk
Do not
- Do not claim improvement without comparable measurements.
- Do not remove checks from builds just to make them faster.
- Do not change package output semantics without calling out compatibility impact.