Keeping Routines Focused

$npx mdskill add obra/clank/Keeping Routines Focused

Extract routines to improve manageability and testability.

  • Splits complex functions into focused units with single responsibilities.
  • Detects multiple responsibilities via 'and' in descriptions or line count.
  • Identifies violations of single responsibility principle automatically.
  • Outputs refactored code with clearer structure and better naming.

SKILL.md

.github/skills/Keeping Routines FocusedView on GitHub ↗

No skill content available yet.

More from obra/clank

SkillDescription
Commenting IntentComment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Creating SkillsTDD for process documentation - test with subagents before writing, iterate until bulletproof
Designing Before CodingDesign in pseudocode first, iterate approaches, then translate to code
Domain-Focused NamingName code by what it does in the domain, not how it's implemented or its history
Encapsulating ComplexityHide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Exploring AlternativesTry 2-3 different approaches before implementing - don't settle for first design you think of
Installing Skills SystemFork, clone to ~/.clank, run installer, edit CLAUDE.md
Localizing VariablesDeclare variables in smallest possible scope, initialize close to first use, minimize span and live time
Maintaining Consistent AbstractionsClass interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Naming VariablesChoose names that fully and accurately describe what the variable represents