trove-architect
Design the shape before the code: sketch types, signatures, and module structure with not-implemented bodies, agree, then fill in. Scrap the sketch when implementation proves it wrong. Use for non-trivial work where jumping straight to code would lock in the wrong shape. Use when: architect this; design this before coding; sketch the types first.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-architect
- description
- Design the shape before the code: sketch types, signatures, and module structure with not-implemented bodies, agree, then fill in. Scrap the sketch when implementation proves it wrong. Use for non-trivial work where jumping straight to code would lock in the wrong shape. Use when: architect this; design this before coding; sketch the types first.
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.
If a sibling skill in this plugin matches the request more directly, defer to it. See AGENTS.md (or docs/routing.md in the marketplace) for the per-plugin routing index.
trove-architect
Design the shape before writing the code. The shape is the types, the signatures, and the module boundaries — with not implemented bodies. Get the data shape right first (trove-principle-data-shape) and make it honest (trove-principle-type-discipline).
Phases
- Ground. Understand the existing code via
trove-explain(read the real code, don't guess). Skip for greenfield. - Sketch. Write the types, function signatures, and module map with stubbed (
throw new Error('not implemented')) bodies. This is the artifact to review — it's cheap to change now. - Agree (optional gate). For contested or high-blast-radius shapes, confirm the sketch before filling in. For routine work, proceed.
- Implement. Fill in the bodies. Ship the synthesis (the sketch) as its own commit so later commits read as filling in bodies.
- Scrap when wrong. Watch for the tells that the shape is wrong and rewrite the sketch rather than forcing it.
Scrap tells
Rewrite the shape — don't paper over it — when you see a pattern (not a single case) of:
- The same workaround repeated to fit the types.
- Escape hatches creeping in (
any, casts, optional fields that "shouldn't" be optional). - The "we need a lock / a flag / a side channel" reflex to make the shape work.
One awkward spot is normal. A pattern of them means the foundation is wrong; redesign as if you'd known on day one.
Anti-patterns
- Don't sketch a trivial one-liner — that's over-process. This is for work where the wrong shape is expensive.
- Don't keep filling in a sketch that keeps fighting you. Scrapping early is cheaper than a built-out wrong shape.
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.