performance-budgeting

Define performance budgets via axis-by-axis interviews during PRD compilation.

6|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill performance-budgeting-repairyourtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-budgeting
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skills/performance-budgeting
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill performance-budgeting-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes clear, measurable, and enforceable performance thresholds for software applications, ensuring a consistent and high-quality user experience across various surfaces and conditions.

Core Features & Use Cases

  • Axis-based Budgeting: Defines performance targets across key metrics like Web Vitals, bundle size, API/DB response times, and desktop/mobile surface metrics.
  • Surface Conditioning: Tailors performance axes to the specific tech stack of a project, skipping irrelevant metrics.
  • Write-As-You-Go: Integrates directly into the PRD compilation process, writing budgets immediately to ENGINEERING-STANDARDS.md.
  • CI Enforcement Mapping: Specifies how performance budgets will be monitored and enforced within the CI/CD pipeline.
  • Use Case: When creating a new web application's Product Requirements Document (PRD), use this Skill during the architecture phase to define acceptable LCP, INP, CLS, and JavaScript bundle sizes for different page types, ensuring the application remains performant from the outset.

Quick Start

Use the performance-budgeting skill to define engineering performance standards for a new web application.

Frequently Asked Questions about performance-budgeting

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

FAQPage Schema
How do I define performance budgets for Web Vitals during a PRD architecture phase?

You define performance budgets through an axis-by-axis interview methodology during PRD compilation, setting specific thresholds for Web Vitals like LCP, INP, and CLS. This process ensures measurable performance targets are established before development begins.

What metrics should I include when establishing engineering performance budgets?

Engineering performance budgets should include thresholds for Web Vitals, JavaScript bundle size, API response times, and database response times. These metrics are further conditioned across desktop and mobile surfaces to match your application's requirements.

Can I tailor performance budgets to skip irrelevant metrics for my specific tech stack?

Yes, performance budgets are tailored to your specific tech stack through surface conditioning. This process skips irrelevant metrics, ensuring only applicable performance axes like API or DB response times are defined for your project.

How do I enforce performance budgets in a CI/CD pipeline?

Performance budgets are enforced in CI/CD pipelines through explicit enforcement mapping. The Skill specifies how thresholds like JS bundle size and Web Vitals will be monitored and blocked within your continuous integration workflow.

Where are performance budget thresholds documented when compiling a PRD?

Performance budget thresholds are written directly to an ENGINEERING-STANDARDS.md file during PRD compilation. This write-as-you-go integration ensures engineering standards are captured immediately as architecture decisions are made.