perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
Install
npx skills add https://github.com/composio-community/awesome-claude-plugins --skill perf-theory-gathererSKILL.md
perf-theory-gatherer
Generate performance hypotheses for a specific scenario.
Follow docs/perf-requirements.md as the canonical contract.
Required Steps
- Review recent git history (scope to relevant paths when possible).
- Identify code paths involved in the scenario (repo-map or grep).
- Produce up to 5 hypotheses with evidence + confidence.
Output Format
hypotheses:
- id: H1
hypothesis: <short description>
evidence: <file/path or git change>
confidence: low|medium|high
- id: H2
...
Constraints
- MUST check git history before hypothesizing.
- No optimization suggestions; only hypotheses.
- Keep to 5 hypotheses maximum.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".