What problem does it solve? Frontend build pipelines and bundle output often drift from best practices silently: oversized bundles, missing code splitting, unpinned build tools, and absent CI size budgets. This Skill statically audits a TypeScript frontend's build configuration, bundle composition, asset hygiene, and build performance against an opinionated baseline, then offers an implementation plan for the gaps. ## Core Features & Use Cases - Four-layer audit: Checks build configuration soundness, bundle composition and size, asset and dependency hygiene, and build performance, each graded as present, partial, missing, or violation. - Static-first with optional stats enrichment: Runs fully read-only by default; pass --with-stats to consume an existing bundle-stats artefact (webpack-bundle-analyzer, rollup-plugin-visualizer, @next/bundle-analyzer) for real size numbers. - Two-phase workflow: Writes findings.md, findings.json, snapshot.md, and metadata.json to .architect-audits/bundle-build-audit/, then asks before generating a descriptive implementation plan. - Use Case: Run /bundle-build-audit --with-stats on a Vite React app to discover that lodash is imported as a default import in four files, the initial bundle exceeds 250kb gzipped, and no bundle-size budget is enforced in CI, then generate a remediation plan. ## Quick Start Ask the AI to run /bundle-build-audit on this repository to audit the build pipeline and bundle output, optionally adding --with-stats if a bundle-stats artefact exists.
