Skip to content
Skills Library
Programming · Building & coding

builder

/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.

Repository
grimoire ↗
Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Arguments

/builder task-description
Original author 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.

How it works

  1. Workflow
  2. Focus Modes
  3. Relevant Rules (load explicit for planning)
  4. Tool Preferences
  5. Constraints
  6. Handoff
Original SKILL.md headings · 50 lines, 281 words
SKILL.md preview
---
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

Versions

RepositoryScoreLicence
This page · grimoire-rs/grimoire90Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT
Tristan578/project-forge100Apache-2.0
tomaspozo/agentlink90MIT

Database snapshot: 13.11.2026 · package version 496b3b7386e3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100test-data-builder
    Test Data Builder - Auto-activating skill for Test Automation. Triggers on: test data builder, test data builder Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test data builder", "test builder", "test".
  • 100project-structure
    This skill should be used when the user is setting up a Python project structure, choosing between src/ and flat layout, organizing __init__.py files, creating a new package directory, or structuring a monorepo. Covers src/ layout, flat layout, __init__.py design, __all__…
  • 91test-driven-development
    Use when implementing any feature or bugfix, before writing implementation code
  • 100test-driven-development
    Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
  • 100apd-tdd
    MANDATORY for every APD builder dispatch. Use when implementing any feature, fixing any bug, or writing new code as a builder agent — write a FAILING test first, watch it fail, write minimal code to pass, refactor while green. Triggers on "implement", "add feature", "fix bug",…
  • 100test-driven-development
    Use when implementing a large task (above the small-task threshold in rules/dispatch.md 测试分级) — feature, bugfix or refactor — before writing implementation code

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.