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