菜单
Verify a performance change with before/after evidence — baseline runs, labeled diffs, then the asserting layer. Use when optimizing API or web performance, investigating a perf regression, comparing latency, DOM nodes, or script time across a change, or asked "did this make it faster".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/adam-s/saasparilla --skill perf-verify命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Operating manual for the local GitOps twin (kind + registry + Gitea + Flux) — how to drive it, how to read it, and the failure catalogue that cost real time to learn. Use when working on deploy/, clusters/, scripts/cluster.mjs, scripts/gitops.mjs, scripts/images.mjs, or when a Kustomization, Gateway, ImagePolicy or rollout is not doing what it says.
Adversarial review of TIME — instants, calendar dates, zones, DST, precision and ordering — across this repo's store, wire and run planes; hunts the defect that never throws (a plausible-looking wrong moment) and reports it only with the input that produces it. Report-only, diagnoses without fixing. Use after any change that stores, converts, formats, compares, groups by or measures time, or when asked to "red team the time handling", "check the timezone", "is this DST-safe", "why is this on the wrong day", "audit the timestamps", "check the date bucketing".
Load-test the API with stress.mjs scenarios (read-heavy, cold-heavy, ingest-heavy, mixed, rate-limit-storm), snapshot /metrics before and after, and write a findings report naming any failing budget. Use for stress testing, load testing, soak checks, or verifying perf budgets under concurrency.
基于 SOC 职业分类
正在显示 SKILL.md
| name | perf-verify |
| description | Verify a performance change with before/after evidence — baseline runs, labeled diffs, then the asserting layer. Use when optimizing API or web performance, investigating a perf regression, comparing latency, DOM nodes, or script time across a change, or asked "did this make it faster". |
Report tools produce labeled artifacts (.perf/<label>/); the asserting
layer gates. Never conclude from a single run — variance rule: 3 runs
per side, compare medians.
docker info first if anything hangs, then docker compose up -d.pnpm --filter core build && pnpm --filter api build && pnpm --filter web buildRATE_LIMIT_PER_MIN=10000000 node dist/main.js from apps/api/
(a full stress run is ~600k requests — 100k/min silently measured
the limiter once; stress now fails such a run)pnpm --filter web preview --port 4173 (never the dev server)curl -s localhost:3001/metrics
answers (stale-dist runs have burned two milestones).node scripts/api-bench.mjs --label baseline-<n> (n = 1..3)node scripts/perf-profile.mjs --label baseline-<n> and one
node scripts/snapshot.mjs --label baseline for screenshots.--label after-<slug>-<n>..perf/<label>/api.json / profile.json. If the
delta of medians is within the baseline's own run-to-run spread, the
honest verdict is "no measurable change" — report exactly that.pnpm ui-spec — frontend budgets (DOM scaling, script time)node scripts/stress.mjs --label after-<slug> — backend budgets,
exits 1 on breach.Report a table: metric | baseline median | after median | delta | budget.
Budgets live in perf/budgets.json — ratcheted, never loosened silently.
A real improvement may tighten one: one-line DECISIONS.md entry + ratchet
in the same commit.
bench/stress print their own psql cleanup line — run it. After any load run, restart the API before probing error paths (a hot process skews them).