superpowers
claudecodexCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Full SDD loop (grill → spec → research → review → build) over one SPEC.md, caveman encoding, bug-to-spec backprop
Plugin ck from marketplace cavekit-marketplace in JuliusBrussee/cavekit. Commands read from the repo's manifest — 1 month ago.
backpropBug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
buildPlan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, im
cavemanCaveman encoding for SPEC.md and spec-adjacent writes. Loaded by /spec, /build, /check. Cuts tokens ~75% vs prose while staying precise. Triggers on any write to SPEC.md or when user says "caveman", "compress this", "be brief".
checkRead-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still ma
deepenOptional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T e
grillCalibrated interrogation of a fuzzy idea before it becomes a spec. Asks one question at a time, recommends an answer, and lands each answer in §G (goal) or §C (constraints) — unknowns parked as `?` items, never guessed. The cheapest place to kill a bad idea is before §T exists. Triggers when the use
researchGather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior. Each finding cites a source; unsourced claims are flagged, never written as fact. Triggers when a spec decision hinges on a library/API/be
reviewAdversarial senior review of the spec before any code is written. Constructs a skeptical reviewer whose authority comes from the codebase, §R research, and live best-practice — then tries to REFUTE the spec, not rubber-stamp it. Every finding cites evidence (file:line or source); unverifiable ones a
specCreate, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "wri
/ck:buildPlan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
/ck:checkDrift detector. Diff SPEC.md against code. Read-only, zero writes.
/ck:deepenSpare-budget design pass. Make one shallow module deep — smaller interface, behavior held, tests green before & after.
/ck:grillSharpen a fuzzy idea into §G/§C before spec. Calibrated interrogation, one question at a time.
/ck:researchGather external knowledge into §R so build grounds in facts, not hallucinations. Every finding cites a source.
/ck:reviewAdversarial senior review of the spec before build. Refute, don't rubber-stamp. Ends in a go/no-go gate.
/ck:specCreate, amend, or backprop bug into SPEC.md. Sole mutator of spec.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.