performance-budget

Enforce performance budgets across CI gates and PR checks.

Updated May 11, 2026

Search Tags:#performance #regression #ci #web-vitals #budgets #rum

Ready to run

npx skills add https://github.com/resultakak/argos --skill performance-budget-resultakak

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performance-budget
Source: https://github.com/resultakak/argos/tree/main/skills/performance-budget
Command: npx skills add https://github.com/resultakak/argos --skill performance-budget-resultakak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Performance budgets and gating across deployment pipelines to prevent regressions in UX and cost.

Core Features & Use Cases

Declarative budgets for web vitals (LCP/INP/CLS), bundle size, API latency, memory/CPU, and cost.
CI gates and PR checks to enforce budgets before release.
RUM authoritative monitoring and regression detection to surface issues early.

Quick Start

Define budgets for your main pages and enable CI gates to block excessive changes.

Frequently Asked Questions about performance-budget

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

FAQPage Schema

How do I enforce performance budgets in CI to prevent regressions?▼

You can enforce performance budgets in CI by defining declarative limits for web vitals, bundle size, and API latency, then configuring CI gates and PR checks to block excessive changes before release.

What web vitals and metrics can I set performance budgets for?▼

Performance budgets can be set for core web vitals like LCP, INP, and CLS, alongside bundle size, API latency, memory/CPU usage, and operational cost to comprehensively guard production quality.

How do I detect performance regressions using RUM data?▼

You can detect performance regressions using RUM by applying authoritative monitoring procedures that surface real user experience issues early, triggering remediation before releases are deployed.

Can I apply per-page web vitals budgets across frontend and backend pipelines?▼

Yes, you can apply per-page web vitals, bundle size, and API latency budgets across frontend and backend pipelines to identify bottlenecks and systematically guard production quality.

What's the best way to block PRs that exceed bundle size or API latency budgets?▼

The best way to block PRs exceeding bundle size or API latency budgets is to define declarative limits and enable CI gates that automatically block excessive changes during PR checks.

Do I need separate tools for CI performance gating and RUM monitoring?▼

No, you can unify CI performance gating and RUM monitoring by defining declarative budgets, configuring CI gates to block regressions, and applying RUM dashboards to detect post-deployment issues.