Performance Budget Skill

Produce a complete, actionable performance budget document for a web service or application. A performance budget is not a wishlist — it is a set of measurable, enforced constraints that define what "acceptable performance" means and who is responsible when those constraints are violated.

A good performance budget answers: what are the targets, how are they measured, what triggers an investigation, and what happens when a budget is breached.

Required Inputs

Ask for these if not already provided:

• Service name and type — web app, API service, mobile app, or combination
• Key user journeys — the 3–5 most important flows users take (e.g. "search → product page → checkout")
• Current baseline metrics — P50/P95/P99 latency, LCP, CLS, INP if available (state "no baseline" if not collected yet)
• Tech stack — frontend framework, backend language/framework, CDN, database
• Deployment environment — cloud provider, region(s), edge/CDN configuration
• Cost constraints — any budget or infrastructure limits that affect headroom

Output Format