build-optimization-specialist

Optimize JavaScript and TypeScript frontend builds with Vite, Rollup, Webpack, or esbuild.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill build-optimization-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-optimization-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/build-optimization-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill build-optimization-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams who face slow builds, oversized bundles, or CI timeouts by providing a structured approach to measure, analyze, and reduce build time and bundle size for web applications.

Core Features & Use Cases

  • Measure build performance and identify bottlenecks, largest dependencies, and slow build steps.
  • Optimize dependency usage and replace or lazily load heavy libraries to reduce initial bundle weight.
  • Implement code splitting, tree shaking, and manual chunking strategies for route and vendor separation.
  • Tune build configuration and enable caching strategies in CI to speed up developer feedback loops and deployments.
  • Use faster toolchains and package managers, optimize assets and images, and set bundle size budgets to enforce limits.

Quick Start

Run an analysis of the repository build to identify top time sinks, largest modules, and a prioritized list of changes to reduce build time and bundle size.

Frequently Asked Questions about build-optimization-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce bundle size and speed up build times for a Vite project?

To reduce bundle size and speed up Vite builds, analyze your largest dependencies, enforce tree shaking, and configure code splitting for routes and vendor chunks. This structured approach measures bottlenecks and applies manual chunking to shrink delivery size.

Why does my JavaScript frontend build keep timing out in CI?

JavaScript frontend builds time out in CI due to slow dependency installation and missing cache configurations. Implementing CI dependency caching and tuning your build configuration speeds up developer feedback loops and prevents pipeline timeouts.

What's the best way to identify the largest dependencies in a Webpack bundle?

The best way to identify the largest dependencies in a Webpack bundle is to run a repository build analysis. This measures build performance, identifies top time sinks, and highlights the largest modules to prioritize replacement or lazy loading.

Does this build optimization approach work with Rollup and esbuild?

Yes, this build optimization approach works with Rollup and esbuild. It applies dependency analysis, tree shaking enforcement, and configuration tuning to any JavaScript or TypeScript frontend project using Vite, Webpack, Rollup, or esbuild.

How do I set up bundle size budgets to enforce size limits?

To set up bundle size budgets, configure your build tool to enforce strict size limits on your production bundles. This prevents oversized deliveries by failing the build when initial bundle weight exceeds the defined target thresholds.

When should I use manual chunking instead of automatic code splitting?

Use manual chunking instead of automatic code splitting when you need strict route and vendor separation to optimize initial bundle weight. It allows precise control over dependency grouping, complementing tree shaking and lazy loading strategies.