vibe-perf
Skill7 starsChanged 13 days agoNo licenceView on GitHub
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 after vibe-review flags performance as P1/P2, and before deploy when vibe-deploy Step 0.5 runs it (perf baseline exists, or the user asks). Open P0s go to backlog.md, each result to vibe/perf/baseline.json; deploy STOPs while findings.p0 > 0. 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. Fixes after a passed review gate reopen it, so review: runs again. Tracks scores over time and compares against previous perf: runs.
- Installs packages
In this repository26 other files it gives its agents.
- vibe-add-featureSkill
- vibe-agentSkill
- vibe-architectSkill
- vibe-brainstormSkill
- vibe-changelogSkill
- vibe-change-specSkill
- vibe-costSkill
- vibe-deploySkill
- vibe-design-mdSkill
- vibe-designSkill
- vibe-doctorSkill
- vibe-documentSkill
- vibe-e2eSkill
- vibe-fix-bugSkill
- vibe-goldfishSkill
- vibe-graphSkill
- vibe-handoffSkill
- vibe-initSkill
- vibe-ledgerSkill
- vibe-modeSkill
- vibe-new-appSkill
- vibe-parallelSkill
- vibe-progressSkill
- vibe-reviewSkill
- vibe-spec-reviewSkill
- vibe-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
34 rules. About 0 are common, 27 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈27
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.