Build Optimization
Expert guidance for optimizing build systems, reducing compilation times, maximizing cache hit rates, and building developer tools that enhance productivity across the development lifecycle.
When to Use This Skill
- Diagnosing slow build times and identifying bottlenecks
- Configuring caching strategies (local, remote, distributed)
- Setting up incremental builds and parallel execution
- Optimizing CI/CD pipeline performance and cost
- Designing or improving bundle splitting and tree shaking
- Building CLIs, plugins, code generators, or IDE extensions
- Configuring monorepo tooling (Nx, Turborepo, Bazel)
- Reducing developer feedback loop times (hot reload, watch mode)
- Managing build artifacts and reproducibility
Quick Reference
| Task |
Load reference |
| Compilation, caching, incremental builds, CI/CD optimization |
skills/build-optimization/references/build-systems.md |
| Plugin systems, code generation, linting, IDE integration, monorepo tooling |
skills/build-optimization/references/developer-tooling.md |
Core Targets
- Build time under 30 seconds for development builds
- Rebuild time under 5 seconds with watch mode
- Cache hit rate above 90% in CI
- Zero flaky builds in production pipelines
- Reproducible builds across environments
Workflow
1. Performance Analysis
Profile the current build before making changes.
- Measure cold build, incremental rebuild, and hot reload times
- Profile CPU, memory, and I/O during builds
- Map the dependency graph and identify bottlenecks
- Evaluate cache hit rates and invalidation patterns
- Review current tool configuration for missed optimizations
2. Optimization
Apply targeted improvements based on profiling data.
- Enable incremental compilation and caching
- Configure parallel execution across available cores
- Set up code splitting and tree shaking
- Optimize module resolution and source transformation
- Implement remote or distributed caching for CI
3. Tooling
Build or configure developer tools for fast feedback loops.
- Configure watch mode and hot module replacement
- Set up clear error messages and progress indicators
- Integrate build analytics and performance dashboards
- Add pre-commit hooks for format, lint, and validation
4. Monitoring
Track build health over time.
- Set up automated build time tracking and alerting
- Monitor cache hit rates and bundle size trends
- Detect performance regressions in CI
- Review and optimize periodically based on data
Common Mistakes
- Optimizing without profiling first
- Disabling caching due to intermittent issues instead of fixing invalidation
- Running full builds when incremental builds would suffice
- Not parallelizing independent build tasks
- Ignoring I/O as a bottleneck (disk speed, network latency)
- Letting bundle sizes grow unchecked without analysis
- Using a single build configuration for development and production
1---2name: build-optimization3description: Build system optimization covering compilation, caching, incremental builds, and developer tooling. Use when improving build times, configuring CI pipelines, or designing developer tools.4---5
6# Build Optimization
7
8Expert guidance for optimizing build systems, reducing compilation times, maximizing cache hit rates, and building developer tools that enhance productivity across the development lifecycle.
9
10## When to Use This Skill
11
12- Diagnosing slow build times and identifying bottlenecks
13- Configuring caching strategies (local, remote, distributed)
14- Setting up incremental builds and parallel execution
15- Optimizing CI/CD pipeline performance and cost
16- Designing or improving bundle splitting and tree shaking
17- Building CLIs, plugins, code generators, or IDE extensions
18- Configuring monorepo tooling (Nx, Turborepo, Bazel)
19- Reducing developer feedback loop times (hot reload, watch mode)
20- Managing build artifacts and reproducibility
21
22## Quick Reference
23
24| Task | Load reference |
25| --- | --- |
26| Compilation, caching, incremental builds, CI/CD optimization | `skills/build-optimization/references/build-systems.md` |
27| Plugin systems, code generation, linting, IDE integration, monorepo tooling | `skills/build-optimization/references/developer-tooling.md` |
28
29## Core Targets
30
31- Build time under 30 seconds for development builds
32- Rebuild time under 5 seconds with watch mode
33- Cache hit rate above 90% in CI
34- Zero flaky builds in production pipelines
35- Reproducible builds across environments
36
37## Workflow
38
39### 1. Performance Analysis
40
41Profile the current build before making changes.
42
43- Measure cold build, incremental rebuild, and hot reload times
44- Profile CPU, memory, and I/O during builds
45- Map the dependency graph and identify bottlenecks
46- Evaluate cache hit rates and invalidation patterns
47- Review current tool configuration for missed optimizations
48
49### 2. Optimization
50
51Apply targeted improvements based on profiling data.
52
53- Enable incremental compilation and caching
54- Configure parallel execution across available cores
55- Set up code splitting and tree shaking
56- Optimize module resolution and source transformation
57- Implement remote or distributed caching for CI
58
59### 3. Tooling
60
61Build or configure developer tools for fast feedback loops.
62
63- Configure watch mode and hot module replacement
64- Set up clear error messages and progress indicators
65- Integrate build analytics and performance dashboards
66- Add pre-commit hooks for format, lint, and validation
67
68### 4. Monitoring
69
70Track build health over time.
71
72- Set up automated build time tracking and alerting
73- Monitor cache hit rates and bundle size trends
74- Detect performance regressions in CI
75- Review and optimize periodically based on data
76
77## Common Mistakes
78
79- Optimizing without profiling first
80- Disabling caching due to intermittent issues instead of fixing invalidation
81- Running full builds when incremental builds would suffice
82- Not parallelizing independent build tasks
83- Ignoring I/O as a bottleneck (disk speed, network latency)
84- Letting bundle sizes grow unchecked without analysis
85- Using a single build configuration for development and production
nickcrew