obra verified

Run verification commands and confirm output before claiming success

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

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

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

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

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

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

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

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

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

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

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