One-click install
npx skills add https://github.com/machenjie/rd-skills --skill performance-budgeting-machenjie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-budgeting
Source: https://github.com/machenjie/rd-skills/tree/main/src/foundation/capabilities/performance-budgeting
Command: npx skills add https://github.com/machenjie/rd-skills --skill performance-budgeting-machenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents performance regressions and surprise cloud spend by requiring explicit, measurable budgets for latency, payload, frontend health, queries, memory, and unit economics before a change ships.

Core Features & Use Cases

  • Define budgets you can enforce: Establish percentile-based targets (e.g., P95/P99) for user-facing latency and ensure they are checked automatically in CI/CD rather than documented.
  • Cover end-to-end bottlenecks: Use frontend budgets (LCP, INP, CLS, TTI), bundle-per-chunk budgets, database execution and resource-cost budgets, and cloud cost unit economics.
  • Make tradeoffs quantifiable: Drive architectural decisions (caching, indexing, pagination, code splitting, autoscaling) using justified baseline measurements and escalation rules.

Quick Start

Use performance-budgeting to define and enforce P95/P99 latency, frontend Core Web Vitals, bundle size per route/chunk, query cost via EXPLAIN validation, and CI/CD release gates for the change you are about to ship.

Frequently Asked Questions about performance-budgeting

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

FAQPage Schema
How do I enforce CI/CD release gates for frontend Core Web Vitals and bundle size?

You can enforce CI/CD release gates by setting explicit per-chunk bundle limits and Core Web Vitals targets (LCP, INP, CLS, TTI) that block or warn on regressions before a change ships, ensuring frontend performance budgets are automatically validated rather than just documented.

What is performance budgeting for API latency percentiles and cloud cost unit economics?

Performance budgeting defines measurable P95/P99 latency targets and cloud cost unit economics limits for API endpoints and background jobs, preventing user-impacting latency regressions and surprise cloud spend by bounding resource usage before release.

How do I set up database query cost control using EXPLAIN validation in CI?

To set up query cost control, you define database execution and resource-cost budgets that enforce index requirements via EXPLAIN validation in CI/CD, blocking releases if queries exceed the specified execution cost or fail to use required indexes.

Can I apply performance budgets to background jobs and long-running workers?

Yes, performance budgets apply to background jobs and long-running workers by bounding their latency, payload, and resource usage, ensuring these asynchronous tasks do not exceed measurable P95/P99 latency targets or cloud cost unit economics limits before release.

When should I use warning versus blocking outcomes for CI/CD performance release gates?

Use warning versus blocking outcomes based on your performance budget escalation rules and justified baseline measurements, making architectural tradeoffs quantifiable so critical latency, Core Web Vitals, or query cost regressions block release while minor deviations warn.