agentsclimarketplace
Sign in

Builder

Skill grimoire-rs/grimoire/.claude/skills/builder

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.From its SKILL.md

Install
npx -y skills add grimoire-rs/grimoire --skill builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 4 commands, including `cargo check` and 3 more.

SKILL.md

2.5 KB, 509 tokens by cl100k_base, as published. Nobody here has run it

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 Swarm Review — code review

$ARGUMENTS

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.