Imported from OutThisLife/brooklyn-skills (skills/perf/SKILL.md). Install upstream with npx skills add OutThisLife/brooklyn-skills --skill perf. Copyright stays with the author.

Perf

Name: perf
Author: OutThisLife

The general performance loop. Profiling (CPU profile, flamegraph, memory snapshot, trace) is the usual tool, but the loop is the same regardless of which one fits.

Loop

Reproduce the slow path and capture a baseline number — time, memory, FPS, request latency, whatever matters here.
Profile to find the real hot path: CPU profile / flamegraph / memory snapshot / trace as fits. Reuse the repo's existing profiler; don't build a parallel harness.
Read the profile, not your intuition — fix the actual hot path.
Re-measure. Record before/after in the PR title/description.
Ship in topical commits (pr-update), clean, keep CI green.

Don't

Optimize by guess before profiling.
Fiddle with the measurement system instead of improving perf.
Run a full suite or profile that overwhelms the machine — scope the run.
Report gains you didn't measure.

{ "ocm": "1", "id": "outthislife-brooklyn-skills-perf", "kind": "skill", "name": "perf", "description": "The general profile-driven perf loop for any language or runtime: baseline, profile, fix the real hot path, re-measure. Use for /perf, \"this is slow\", or optimization work.", "publisher": "OutThisLife", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "The general profile-driven perf loop for any language or runtime: baseline, profile, fix the real hot path, re-measure. Use for /perf, \"this is slow\", or optimization work." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/OutThisLife/brooklyn-skills", "path": "skills/perf/SKILL.md", "ref": "e91f3a9d1506d4f708086561354dae98361f404d", "url": "https://github.com/OutThisLife/brooklyn-skills/blob/e91f3a9d1506d4f708086561354dae98361f404d/skills/perf/SKILL.md", "key": "OutThisLife/brooklyn-skills/skills/perf/SKILL.md" } }, "instructions": "# Perf\n\nThe general performance loop. Profiling (CPU profile, flamegraph, memory\nsnapshot, trace) is the usual tool, but the loop is the same regardless of which\none fits.\n\n## Loop\n\n1. Reproduce the slow path and capture a baseline number — time, memory, FPS,\n request latency, whatever matters here.\n2. Profile to find the real hot path: CPU profile / flamegraph / memory snapshot\n / trace as fits. Reuse the repo's existing profiler; don't build a parallel\n harness.\n3. Read the profile, not your intuition — fix the actual hot path.\n4. Re-measure. Record before/after in the PR title/descrip", "cost": { "context_tokens": 223 } }

perf

About

Perf

Loop

Don't

Use it

Manifest

Reviews