W Perf

by blockmatic7e05e2abd052dc6b526e8a28e36d102d42bfd635No license1 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 6 days ago

Measure bottlenecks with repository tools, then recommend or apply evidenced optimizations.

AI-generated overview

Measures performance bottlenecks with a real baseline, then recommends or applies evidenced optimizations.

What it does: Guides an agent through a measured performance investigation: read existing testing docs for budgets, capture a baseline using the repository's profiler, traces, tests, or job timing, and locate the owning hot path such as a query, render, or allocation. It then recommends the smallest change, implements it only when authorized, and re-measures afterwards. New budgets are documented in existing testing docs rather than invented, and documentation is updated if behavior or commands changed.
When to use it: Use when investigating performance issues in a repository and a measured baseline is needed before proposing changes. It suits report-only analysis unless the user explicitly asks for implementation.
Requirements: Instructions only, no bundled scripts. Requires access to the repository's testing docs, profiler, traces, or tests, and optionally the gh CLI for job timing.

Find performance issues with a measured baseline. Do not invent SLOs or impact percentages. Report-only unless the user asked to implement.

Read testing docs for budgets if present. Capture a baseline with the repo profiler, traces, tests, or gh job timing — not estimates.
Locate the owning hot path (query, render, allocation) with that evidence.
Recommend the smallest change. Implement only when authorized. Re-measure after a change.
If a new budget is required, document it in existing testing docs instead of inventing an SLO here.
Docs: /w-docs if behavior or commands changed.

Source and attribution

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.