Coding & architecture skills

A relentless interview to sharpen a plan or design.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the…

Build and refine your project's domain model, glossary, and architectural decisions

Teach the user a new skill or concept, within this workspace.

Deep module design vocabulary for building testable, maintainable code with small interfaces

Systematic diagnosis loop for hard bugs and performance regressions with tight feedback loops

Two-axis code review: Standards compliance and spec adherence, running in parallel

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens".…

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".

Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Trigger: /caveman-compress.

Quick-reference card for the three caveman skills and their commands. Trigger: /caveman-help or "caveman help".

Hypothesis-driven debugging loop: observe, hypothesize, test, verify

Write structured implementation plans before starting complex tasks

Prepare code for review: self-review, test coverage, and pull request description

Create isolated Git worktrees for feature branches without disrupting your current workspace

Verify tests pass, detect your environment, then safely merge or deploy completed work