performance

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "performance",
  "version": "0.2.9",
  "description": "Measurement-first optimization workflow for an arbitrary target, built around refusing to report what the data does not support. Five skills: target (identify and rank optimization candidates by evidence quality rather than suspicion, so an unmeasured target makes \"instrument this first\" the recommendation instead of a guess), goal (human-gated goal construction that holds a realistic target and an ideal target separately and computes the irreducible floor BEFORE any work, so a target below the floor is surfaced as unreachable-by-any-code-change up front rather than discovered as a failed goal at the end), snapshot (baseline and post capture with the host qualified first: repeated no-op spawns characterize the machine's own noise, a drift-immune counter is reported alongside and ranked above any duration, before/after arms are interleaved within one run rather than compared across two passes, and a wall-clock claim is REFUSED outright from a host whose spread carries the bimodal contention signature, naming the counter it can still report instead), verify (fresh-context adversarial re-derivation that does not inherit the implementer's numbers, plus a report that states a target as met or not met and never rounds a miss into a win), and protect (locks in a proven counter win with a checked-in counter ceiling, a CI check that fails when the counter rises, and a lower ceiling when the counter falls, in the same PR or by a scheduled draft PR, never merging). A technique catalog and a glossary back every skill step. Gates hard-block, with a named override recorded in the report. Every gate ships with a discrimination check proving it fails when its condition is unmet, because a check that passes whether or not the condition holds is worse than no check: it reports success. Normative claims carry a source tier, and the ones the benchmarking literature does not ground (sample counts, the p95 convention, counts-over-time for anything but instruction counts) are labeled as house rules rather than dressed as consensus.",
  "author": {
    "name": "Melodic Software",
    "email": "[email protected]"
  },
  "license": "MIT",
  "keywords": [
    "performance",
    "benchmarking",
    "baseline",
    "measurement",
    "optimization",
    "noise-characterization",
    "drift-immune-counter",
    "interleaved-ab",
    "skill"
  ]
}