Skip to content
Back to skills

Builder

ASecurity

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.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 25, 2026
ai-agentsrustgodebuggingrefactoringapi

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned September 25, 2026

npx -y skills add grimoire-rs/grimoire --skill builder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Builder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/grimoire-rs-builder/badge)](https://www.skillsdirectory.com/skills/grimoire-rs-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

$ARGUMENTS

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.