obra/clank

installing-skills-system

Fork, clone to ~/.clank, run installer, edit CLAUDE.md

testing-skills-with-subagents

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

getting-started-with-skills

Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

brainstorming-ideas-into-designs

Interactive idea refinement using Socratic method to develop fully-formed designs

executing-plans

Execute detailed plans in batches with review checkpoints

subagent-driven-development

Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks

finishing-a-development-branch

Complete feature development with structured options for merge, PR, or cleanup

using-git-worktrees

Create isolated git worktrees with smart directory selection and safety verification

code-review-reception

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

remembering-conversations

Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search

writing-plans

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

systematic-debugging

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

verification-before-completion

Run verification commands and confirm output before claiming success

creating-skills

TDD for process documentation - test with subagents before writing, iterate until bulletproof

test-driven-development-tdd

Write the test first, watch it fail, write minimal code to pass

testing-anti-patterns

Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.

requesting-code-review

Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding

encapsulating-complexity

Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)

maintaining-consistent-abstractions

Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns

commenting-intent

Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)

exploring-alternatives

Try 2-3 different approaches before implementing - don't settle for first design you think of

keeping-routines-focused

Each routine does one thing and does it well - extract when routines have multiple responsibilities

localizing-variables

Declare variables in smallest possible scope, initialize close to first use, minimize span and live time

domain-focused-naming

Name code by what it does in the domain, not how it's implemented or its history

naming-variables

Choose names that fully and accurately describe what the variable represents

refactoring-safely

Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features

simplifying-control-flow

Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels

single-purpose-variables

Use each variable for exactly one purpose - no hybrid coupling or hidden meanings

validating-inputs

Check all external inputs for validity - garbage in, nothing out, never garbage out

writing-evergreen-comments

Write comments explaining WHAT and WHY, never temporal context or history

gardening-skills-wiki

Maintain skills wiki health - check links, naming, cross-references, and coverage

reducing-complexity

Managing complexity is software's primary technical imperative - all other goals are secondary

designing-before-coding

Design in pseudocode first, iterate approaches, then translate to code

dispatching-parallel-agents

Use multiple Claude agents to investigate and fix independent problems concurrently

defense-in-depth-validation

Validate at every layer data passes through to make bugs impossible

root-cause-tracing

Systematically trace bugs backward through call stack to find original trigger

condition-based-waiting

Replace arbitrary timeouts with condition polling for reliable async tests