trove-perf
Diagnose and fix a measured performance problem against a baseline: measure first, fix, re-measure, and cite the delta with an artifact path. Use for slow endpoints, slow queries, or any "make this faster" backed by a measurement. Use when: this is slow; optimize performance; measure and improve.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-perf
- description
- Diagnose and fix a measured performance problem against a baseline: measure first, fix, re-measure, and cite the delta with an artifact path. Use for slow endpoints, slow queries, or any "make this faster" backed by a measurement. Use when: this is slow; optimize performance; measure and improve.
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
trove-perf
Optimize against numbers, not vibes. Every perf claim ties to a before/after measurement.
Workflow
- Baseline. Capture a measurement of the current behavior (timing, query plan, trace, profile) and save the artifact. Don't skip to reading source — measure first.
- Locate the cost. Use the baseline to find where the time actually goes (the slow query, the N+1, the hot frame), not where you assume it is.
- Fix the measured cost. The smallest change that addresses what the measurement showed.
- Re-measure. Same method as the baseline, same inputs.
- Cite the delta. Report baseline, post-fix, and the delta, with the path to the artifact (trace file, query plan, timing run). A fix with no re-measurement is not done.
Anti-patterns
- Reading the code instead of measuring. The bottleneck is rarely where it looks; profile.
- Optimizing an unmeasured path. If the baseline doesn't show it's hot, don't.
- Claiming a win without a re-measure. "Should be faster" is not a result.
Output
Baseline: <metric> (artifact: <path>)
Post-fix: <metric> (artifact: <path>)
Delta: <improvement>
Change: <what was done, tied to the measured cost>
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.