perf-audit
Skill1 starsChanged 5 months agoMITView on GitHub
Invoke when user reports slowness, high memory, timeout. "optimize this", "it's slow", "reduce bundle size", "memory leak", "N+1 query", "unnecessary re-renders". SDLC categories: Non-Functional, Software Maintenance.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- arcasilesgroup/ai-engineeringtheir own version, first seen Nov 8, 2026
- rcelebrone/DotAgentstheir own version, first seen Oct 14, 2026
- muon-m2/magento2-toolstheir own version, first seen Oct 13, 2026
- helderberto/agent-skillstheir own version, first seen Oct 11, 2026
- gonimar/claude-web-studiotheir own version, first seen Sep 27, 2026
- kelgirechandrakant-cpu/vibe-coding-playbooktheir own version, first seen Aug 17, 2026
Used with
Projects with it also use a11y-audit, security-audit and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
renfei-designSkilla11y-audit
Audit Figma designs for WCAG accessibility issues — color contrast, minimum font size, touch target sizing, and missing text alternatives. Use when asked to check accessibility, audit contrast ratios, find a11y issues, verify WCAG compliance, or review designs for accessibility problems. Scans nodes, analyzes offline, and annotates issues in Figma.
Also in 4 projects that use this
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- arcasilesgroup/ai-engineering★ 65same name
- eric-cielo/moflo★ 19same name
- helderberto/agent-skills★ 19same name
- rcelebrone/DotAgents★ 15same name
- muon-m2/magento2-tools★ 6same name
- gonimar/claude-web-studio★ 4same name
- kelgirechandrakant-cpu/vibe-coding-playbook★ 4same name
- CodeWithBehnam/cc-docs★ 2same name
- cystema/skills★ 1same name
- PeterStanchev/ps-claude-skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- apex-archSkill
- apex-debugSkill
- apex-flexSkill
- apex-infraSkill
- apex-novaSkill
- apex-perfSkill
- apex-reedSkill
- apex-reviewSkill
- apex-secSkill
- apexSkill
- apex-uiSkill
- bug-patchSkill
- debug-protocolSkill
- deploy-pipelineSkill
- full-stack-scaffoldSkill
- mvp-cutSkill
- pr-reviewSkill
- refactorSkill
- requirements-to-specSkill
- researchSkill
- sec-reviewSkill
- system-designSkill
- test-harnessSkill
- ui-generateSkill
The file
Files
Performance Audit (Rex's Protocol)
- BASELINE — Get current number. Never optimize blind
- CATEGORIZE — Algorithmic / Database / Network / Bundle / Render
- ALGORITHMIC (first) — O(n²)→O(n log n) is first question
- DATABASE (second) — N+1? Missing index? Unnecessary joins?
- BUNDLE (third) — Dead code? Heavy deps? Route splitting?
- RENDER (last) — Profiler evidence required for memo decisions
- MEASURE AGAIN — Output improvement ratio
Output: Baseline → Category → Fix → Expected improvement ratio
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.

