From performance-budget-validator
Validates web app performance metrics—page loads, bundle sizes, API responses—against budgets to detect regressions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/performance-budget-validator:validating-performance-budgetsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate page load times, bundle sizes, and API response times against predefined performance budgets to catch regressions before they reach production.
Validate page load times, bundle sizes, and API response times against predefined performance budgets to catch regressions before they reach production.
This skill allows Claude to automatically validate your application's performance against predefined budgets. It helps identify performance regressions and ensures your application maintains optimal performance characteristics.
This skill activates when you need to:
User request: "Validate performance budget for the homepage."
The skill will:
User request: "Run performance budget validation as part of the build process."
The skill will:
This skill can be integrated with other plugins that provide performance metrics, such as website speed test tools or API monitoring services. It can also be used in conjunction with alerting plugins to notify developers of performance budget violations.
If budget validation fails:
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin performance-budget-validatorCreates a structured performance budget document with Core Web Vitals targets, backend latency SLOs, CI enforcement rules, and breach response procedures for web services or applications.
Profiles application performance against budgets and optimizes hot paths. Use when investigating performance issues or auditing budgets.
Measures performance baselines, detects regressions before/after PRs, and compares stack alternatives. Supports page, API, build, and before/after modes.