perf-audit

Analyze frontend bundle outputs and enforce size budgets for Vite, Webpack, Next.js, or Rollup.

12|1|Updated Feb 13, 2026

Search Tags:#performance #frontend #audit #lighthouse #webpack #vite #bundle

Ready to run

npx skills add https://github.com/helderberto/skills --skill perf-audit-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: perf-audit
Source: https://github.com/helderberto/skills/tree/main/perf-audit
Command: npx skills add https://github.com/helderberto/skills --skill perf-audit-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes frontend bundles to reduce size and improve load times by surfacing performance bottlenecks and optimization opportunities.

Core Features & Use Cases

Automated bundle analysis detects size distribution, heavy chunks, and potential optimizations across common toolchains (Vite, Webpack, Next.js, Rollup).
Budget enforcement compares initial JS/CSS and total page weight against defined thresholds to prevent regressions.
Guided optimizations suggests practical changes like code-splitting, dependency pruning, and build-configuration tweaks, with real-world examples.

Quick Start

Run a production build and generate a bundle report to identify bottlenecks and optimization opportunities.

Frequently Asked Questions about perf-audit

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

FAQPage Schema

How do I audit frontend bundle size and identify performance bottlenecks?▼

Yes, bundle analysis supports Vite, Webpack, Next.js, and Rollup. The audit automatically detects your toolchain from the production build workflow and analyzes the generated bundle outputs to identify size distribution and heavy chunks.

How do I enforce bundle size budgets to prevent performance regressions?▼

Enforce bundle size budgets by comparing initial JS/CSS and total page weight against defined thresholds. The audit checks package.json for heavy packages and reports size budgets to prevent performance regressions across your frontend build.

What causes large frontend bundles and how can I reduce their impact on load times?▼

You need a production build workflow to use this bundle audit. The tool requires generated production build outputs and checks your package.json for heavy packages to accurately analyze initial JS/CSS size and report optimization opportunities.

What are the limitations of frontend bundle analysis without a production build?▼

Without a production build, bundle analysis cannot accurately assess size distribution or enforce size budgets. The audit enforces production builds because development builds do not reflect the minified initial JS/CSS or heavy dependencies impacting load times.