performance-budget-setter

Defines and enforces performance budgets for bundle size, API latency, and web vitals.

2|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sathishssj3/NexVR-Engine --skill performance-budget-setter-sathishssj3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-budget-setter
Source: https://github.com/sathishssj3/NexVR-Engine/tree/main/.agents/skills/performance-budget-setter
Command: npx skills add https://github.com/sathishssj3/NexVR-Engine --skill performance-budget-setter-sathishssj3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications gradually become slower as features accumulate, and teams lack measurable thresholds to catch regressions before users notice. This Skill provides structured templates and enforcement strategies to set, monitor, and defend performance budgets across bundles, APIs, and databases. ## Core Features & Use Cases - Budget Templates: Ready-to-use tables for bundle size, API latency percentiles, database query limits, and Core Web Vitals targets. - CI/CD Enforcement: Configurations for bundlesize, Lighthouse CI, and webpack performance hints that block regressions at pull request time. - Monitoring & Response: Real User Monitoring with web-vitals, synthetic checks, alert thresholds, and a budget violation response process. - Use Case: A team notices their checkout page slowing down release over release. Use this Skill to define per-page budgets, wire Lighthouse CI into the pipeline, and set alerts when LCP exceeds 2.5 seconds. ## Quick Start Create a performance budget for my web app covering bundle size, API latency, and Core Web Vitals with CI enforcement.

Frequently Asked Questions about performance-budget-setter

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

FAQPage Schema
How do I set a performance budget for my website?▼

Define measurable limits per asset type, such as 200 KB initial JavaScript, 50 KB CSS, and LCP under 2.5 seconds. Document current values alongside targets in a budget table, then enforce them automatically in CI with bundlesize or Lighthouse CI.

How to enforce bundle size limits in CI/CD?▼

Add a bundlesize configuration in package.json with maxSize per output file, then run npx bundlesize in your pull request workflow. Webpack performance hints set to error mode also fail builds exceeding maxAssetSize and maxEntrypointSize.

What are good Core Web Vitals targets?▼

Google defines LCP under 2.5s, FID under 100ms, and CLS under 0.1 as good thresholds. Stricter internal targets like LCP under 2.0s and CLS under 0.05 give headroom before user experience degrades.

How do I monitor web performance in production?▼

Use the web-vitals library to capture CLS, FID, and LCP from real users and send metrics via sendBeacon to an analytics endpoint. Combine this with synthetic Lighthouse CI runs and a dashboard tracking daily percentile trends.

What should I do when a performance budget is exceeded?▼

Block the pull request, notify the team, and investigate the cause within 24 hours. Prefer optimizing the code, but if a budget increase is justified, document it with an impact analysis and alternatives considered.