agentleFS
Asno-devAsno-dev/apex/skills/perf-audit/SKILL.md

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

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-designSkill

    a11y-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

  • CloudflareSkill

    security-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 CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • GoogleSkill

    code-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

The file

Files
SKILL.md

Performance Audit (Rex's Protocol)

  1. BASELINE — Get current number. Never optimize blind
  2. CATEGORIZE — Algorithmic / Database / Network / Bundle / Render
  3. ALGORITHMIC (first) — O(n²)→O(n log n) is first question
  4. DATABASE (second) — N+1? Missing index? Unnecessary joins?
  5. BUNDLE (third) — Dead code? Heavy deps? Route splitting?
  6. RENDER (last) — Profiler evidence required for memo decisions
  7. MEASURE AGAIN — Output improvement ratio

Output: Baseline → Category → Fix → Expected improvement ratio

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.