performance-budget
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.
npx skills add mohitagw15856/pm-claude-skills --skill performance-budget --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 --- # Performance Budget: [Service Name] **Service:** [Name] | **Team:** [Team name] **Last updat
- Required Inputs
- Output Format
- Overview
- Key User Journeys
- Frontend Performance Budget
- Core Web Vitals Targets
- Page Weight Budget
- Per-Journey Frontend Targets
- Backend Performance Budget
- API Latency SLOs
- Database Query Budget
- Measurement Methodology
- Real User Monitoring (RUM)
- Synthetic Monitoring
Run Lighthouse CI against local build Run load test locally Compare performance across recent deploys
What does the performance-budget skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill performance-budget --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.