garage

garage: engineering copilot for Claude Code and Codex

A 12-skill plugin encoding one engineer's actual workflow and house engineering law, rebuilt 2026-07-07 from usage evidence (2,597 real prompts) after the previous 48-skill generation recorded zero invocations. The old pack lives at tag pre-redesign.

Install

Claude Code

claude plugin marketplace add OmexIT/claude-skills-pack   # or the local repo path
# in Claude Code: /plugin, enable "garage", restart session

Codex

codex plugin marketplace add OmexIT/claude-skills-pack   # or the local repo path
codex plugin add garage@garage
# start a new Codex thread so the installed skills are loaded

Both clients install the same 12 skills, references, and skill scripts. The three lifecycle hooks use Claude Code's hook protocol and are loaded only by Claude Code; Codex's plugin manifest intentionally does not declare them.

The skills

Workflow spine (mirrors the real loop; each step optional):

Skill	Use when
spec	Defining or changing WHAT to build; PRD create/update; challenging scope
plan	Turning an approved spec, ticket, or explicit request into a sliced, verifiable plan doc in docs/
build	Executing a plan ("implement docs/...plan.md", "start slice SP-2b")
audit	Reviewing code, diffs, or docs against house standards; expert panels
e2e	Live verification: boot the stack, newman, Playwright, DB checks. Evidence, not claims
ship	Commit / PR / MR / branch promotion per each repo's delivery policy
debug	Any bug or unexpected behavior, before proposing fixes

Domain law (auto-triggers on subject matter):

Skill	Carries
ledger	Double-entry invariants, idempotency key grammar, Blnk + pgledger contracts
migrations	TSID PKs, audit columns, RLS recipe, zero-downtime rules, throttled backfills
temporal	SAGA compensation, retry profiles, versioning, failure-mode table
spring-api	Response envelope, RFC 9457, package-by-feature layout, cursor pagination
igaming-ui	Odds/betslip/live-state patterns, accessible selector contract

Claude Code hooks (plugins/garage/hooks/hooks.json): destructive-command blocker, sensitive-file warning, Prettier autoformat (web files only; Java/Spotless runs once in the ship gate).

The golden path

spec ──► plan ──► build ──► audit ──► e2e ──► ship
                    ▲                           │
                    └────────── debug ◄─────────┘

Plans live in each repo's docs/.../plans/ with checkboxes as durable session state.

Usage samples

Skills fire on natural phrasing. Force one explicitly with /garage:<skill> in Claude Code or $garage:<skill> in Codex.

Single skills

"should we build bulk payouts, or does the batch API already cover it?"   -> spec (challenge: keep/shrink/kill)
"write the PRD for payment links"                                         -> spec (create)
"sync the PRD with what we actually built"                                -> spec (update, drift check)
"plan the wallet top-up feature from docs/prd/topups.md"                  -> plan (sliced plan doc)
"implement docs/plans/2026-07-08-topups-plan.md"                          -> build
"start slice 2b"                                                          -> build (resumes at that slice)
"review this diff against our standards"                                  -> audit
"audit the payments module, include a DDD expert"                         -> audit (expert panel)
"simplification sweep: what can we remove from this product?"             -> audit (removal-first, whole app)
"run and test orders end to end, api and ui"                              -> e2e (newman + Playwright + DB proof)
"why is the balance negative after a refund?"                             -> debug (diagnosis only, no fix yet)
"commit and merge to release-candidate"                                   -> ship (repo's branch policy)
"promote develop to main"                                                 -> ship (promotion PR)

Domain skills load themselves when the work touches their subject: a hold/void flow pulls ledger, a new column pulls migrations, a saga with compensation pulls temporal, a new endpoint pulls spring-api, a betslip component pulls igaming-ui.

A feature, end to end