Source

obra/clank

37 skills · 677 combined installs

Skills from this source

#

Skill

Source

8W Activity

Installs

Getting Started with Skills Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

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

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

Naming Variables Choose names that fully and accurately describe what the variable represents

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

Designing Before Coding Design in pseudocode first, iterate approaches, then translate to code

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

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

Maintaining Consistent Abstractions Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrela…

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

Brainstorming Ideas Into Designs Interactive idea refinement using Socratic method to develop fully-formed designs

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

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

Dispatching Parallel Agents Use multiple Claude agents to investigate and fix independent problems concurrently

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

Executing Plans Execute detailed plans in batches with review checkpoints

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

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

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

Root Cause Tracing Systematically trace bugs backward through call stack to find original trigger

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

Test-Driven Development (TDD) Write the test first, watch it fail, write minimal code to pass

Testing Skills With Subagents RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loo…

Using Git Worktrees Create isolated git worktrees with smart directory selection and safety verification

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

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

Condition-Based Waiting Replace arbitrary timeouts with condition polling for reliable async tests

Defense-in-Depth Validation Validate at every layer data passes through to make bugs impossible

Finishing a Development Branch Complete feature development with structured options for merge, PR, or cleanup

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

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

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

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

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

Verification Before Completion Run verification commands and confirm output before claiming success