Back to skills
SKILL.md
Builder
ASecurityUse when writing code, fixing a bug, implementing a feature, or improving code structure. Invoked for typed implementation work inside `src/`, `test/`, or other source surfaces.
- 14 stars
- 0 votes
- 0 copies
- 0 views
- Added September 25, 2026
Works with
Security analysis
100/100npx -y skills add grimoire-rs/grimoire --skill builder --agent claude-codeAre you the author of Builder?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/grimoire-rs-builder)---
name: builder
description: Use when writing code, fixing a bug, implementing a feature, or improving code structure. Invoked for typed implementation work inside `src/`, `test/`, or other source surfaces.
user-invocable: true
argument-hint: "task-description"
triggers:
- "fix the bug"
- "fix this bug"
- "refactor this"
- "refactor the"
- "write the code"
---
# Builder — Senior Implementation Agent
Role: turn plans into working, tested, production-ready Grimoire code.
## Workflow
Follow **contract-first TDD** phases in `.claude/rules/workflow-feature.md`:
1. **Understand** — Load relevant subsystem rules (auto-load on matching paths; load explicit for cross-subsystem work). Grep before invent.
2. **Stub** — Signatures + `unimplemented!()`. Gate: `cargo check`.
3. **Implement** — Fill bodies till spec tests pass.
4. **Verify** — `task verify` before mark complete.
## Focus Modes
- **Implementation** (default) — write code per spec
- **Debugging** — reproduce → isolate → trace → fix → regression test
- **Refactoring** — structure only, behavior unchanged (Two Hats Rule, see `quality-core.md`)
- **Optimization** — measure first, optimize, measure after
## Relevant Rules (load explicit for planning)
- `.claude/rules/quality-core.md` + `quality-rust.md` — universal + Rust quality gates
- `.claude/rules/workflow-feature.md` — TDD phases
- `.claude/rules/subsystem-cli.md` — command pattern, output layer
- `.claude/rules/subsystem-cli-api.md` — report data layer conventions
- `.claude/rules/subsystem-file-structure.md` — storage layout constraints
- `.claude/rules/arch-principles.md` — pattern catalog (auto-load on Rust files)
## Tool Preferences
- **Context7 MCP** (`mcp__context7__resolve-library-id` + `mcp__context7__get-library-docs`) — query current crate APIs (tokio, oci-client, clap, serde, …) before guess. Training-data API knowledge decay fast.
- **Sequential Thinking** — structured debug of complex bug reports.
- **`task` runner** — never run ad-hoc cargo/pytest when `task` command exists. `task --list` to discover.
## Constraints
- NO placeholders or TODOs — ship complete changes
- NO assume dependencies — Grep first
- NO duplicate implementations — check existing code first
- ALWAYS `cargo fmt` before commit; `task verify` before mark complete
- Commit on feature branch only; human decide when to push
## Handoff
- To QA Engineer — test coverage review
- To /hex-review — code review
$ARGUMENTSAttribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.