vibe-perflisted

Full-stack performance audit for vibe-* projects — frontend, backend, agentic pipelines, and infrastructure. Measures, scores, compares against previous runs, and writes approved fixes automatically. Triggers on "perf:" prefix, "performance audit", "this is slow", "optimize performance", "Lighthouse score", "bundle size", "slow queries", "LLM latency", "token usage", "memory leak", "CPU usage", "cold start", "perf regression". Runs automatically after vibe-review flags performance as P1/P2, and as a recommended pre-deploy check — any perf **P0** it writes to vibe/reviews/backlog.md is then enforced by vibe-deploy's Step 0.5 gate (which blocks on open P0s), so a perf-critical finding does block deploy. Always use when performance is in question — even without the exact prefix. Shows fix plan by category, waits for human approval, then writes all fixes. Tracks scores over time and compares against previous perf: runs.
aakashdhar/vibe-skill · ★ 7 · AI & Automation · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Perf Skill Full-stack performance audit grounded in actual measurements. Measures every layer. Scores it. Compares to last run. Flags regressions. Shows fix plan by category. Writes all approved fixes automatically. **Runs in agent mode (Claude Code / Cursor). Requires filesystem access.** --- ## The principle this enforces Performance problems that aren't measured are invisible. Performance problems that aren't tracked regress silently. Performance problems caught before deploy cost minutes to fix. Performance problems caught in production cost users and reputation. Measure first. Fix second. Never the other way around. --- ## Entry points ### Entry point A — On demand Triggered by: `perf:`, "performance audit", "this is slow", "optimize X" Default scope: full project audit across all applicable layers. If user specifies scope ("perf: frontend only" / "perf: audit the Scout agent") — scope to that layer/module only. Go to **Step 0**. ### Entry point B — After vibe-review flags perf Triggered when `vibe-review` produces P1/P2 findings tagged as performance. Read the review report. Scope to flagged files and layers only. Go to **Step 0**. ### Entry point C — Pre-deploy gate Triggered automatically before `vibe-deploy` runs. Full audit — all layers. If any P0 perf finding exists, deploy is blocked. Go to **Step 0**. --- ## Step 0 — Read project context Read in this order: 1. `vibe/ARCHITECTURE.md` — stack, patterns, any perf thresholds defined 2. `vibe/