PB
Performance Budget
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Define and document performance budgets for a web service or application. Use when asked to set performance targets, define SLOs for latency or throughput, establish Core Web Vitals targets, create a performance baseline, or document performance regression policy. Produces a structured performance budget covering key user journeys, Core Web Vitals, backend latency SLOs, measurement tooling, CI enforcement, and breach response process.
What to give it
▸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
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every budget threshold is a specific number — not a range or "TBD"
✓Both frontend (if applicable) and backend targets are defined — not just one or the other
✓Measurement tooling is named with a link to the dashboard or config file
✓CI enforcement is configured for at least one gate (build-time or deploy-time)
✓Budget breach response process names specific Slack channels and owners
✓Budget thresholds are anchored to baseline measurements or a justified target — not pulled from thin air
✓Per-journey targets are defined for critical user journeys, not just global averages
⚠️ What it refuses to do
Do not set budget thresholds without measuring a current baseline first — targets must be anchored to reality
Do not define global averages only — critical user journeys need individual budgets as they may diverge significantly
Do not omit CI enforcement — a performance budget that is not enforced in the build pipeline will not be respected
Do not leave the breach response process without named owners and escalation channels
Do not set budgets that apply only to one environment — production and staging targets should be documented separately if they differ
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
Start with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="performance-budget"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>
💬 Discussion
Performance Budget is one of 1174 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog