obra/clank
37 skills · 263 total installs
$npx skills add obra/clankSkillInstalls
reducing-complexityManaging complexity is software's primary technical imperative - all other goals are secondarycommenting-intentComment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)keeping-routines-focusedEach routine does one thing and does it well - extract when routines have multiple responsibilitieslocalizing-variablesDeclare variables in smallest possible scope, initialize close to first use, minimize span and live timenaming-variablesChoose names that fully and accurately describe what the variable representscreating-skillsTDD for process documentation - test with subagents before writing, iterate until bulletproofdesigning-before-codingDesign in pseudocode first, iterate approaches, then translate to codedispatching-parallel-agentsUse multiple Claude agents to investigate and fix independent problems concurrentlyencapsulating-complexityHide implementation details behind interfaces - work at domain level (what), not implementation level (how)executing-plansExecute detailed plans in batches with review checkpointsgardening-skills-wikiMaintain skills wiki health - check links, naming, cross-references, and coveragemaintaining-consistent-abstractionsClass interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concernsroot-cause-tracingSystematically trace bugs backward through call stack to find original triggertesting-skills-with-subagentsRED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholesvalidating-inputsCheck all external inputs for validity - garbage in, nothing out, never garbage outwriting-plansCreate detailed implementation plans with bite-sized tasks for engineers with zero codebase contextcondition-based-waitingReplace arbitrary timeouts with condition polling for reliable async testsexploring-alternativesTry 2-3 different approaches before implementing - don't settle for first design you think offinishing-a-development-branchComplete feature development with structured options for merge, PR, or cleanuprefactoring-safelyRefactor with tests first, one change at a time, never mix refactoring with bug fixes or new featuresremembering-conversationsSearch previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text searchrequesting-code-reviewDispatch code-reviewer subagent to review implementation against plan or requirements before proceedingsimplifying-control-flowFlatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levelssingle-purpose-variablesUse each variable for exactly one purpose - no hybrid coupling or hidden meaningssubagent-driven-developmentExecute implementation plan by dispatching fresh subagent for each task, with code review between taskssystematic-debuggingFour-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.testing-anti-patternsNever test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.using-git-worktreesCreate isolated git worktrees with smart directory selection and safety verificationverification-before-completionRun verification commands and confirm output before claiming successwriting-evergreen-commentsWrite comments explaining WHAT and WHY, never temporal context or historybrainstormingInteractive idea refinement using Socratic method to develop fully-formed designsdefense-in-depthValidate at every layer data passes through to make bugs impossiblegetting-startedSkills wiki intro - mandatory workflows, search tool, brainstorming triggersinstalling-skillsFork, clone to ~/.clank, run installer, edit CLAUDE.mdnaming-by-domainName code by what it does in the domain, not how it's implemented or its historyreceiving-code-reviewReceive and act on code review feedback with technical rigor, not performative agreement or blind implementationtest-driven-developmentWrite the test first, watch it fail, write minimal code to pass