Encapsulating Complexity

$npx mdskill add obra/clank/Encapsulating Complexity

Shield domain logic from implementation leaks.

  • Prevents client code from depending on storage formats.
  • Allows internal changes without breaking external users.
  • Enforces abstraction boundaries in class and interface design.
  • Delivers maintainable systems by hiding raw data structures.

SKILL.md

.github/skills/Encapsulating ComplexityView 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
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
Keeping Routines FocusedEach routine does one thing and does it well - extract when routines have multiple responsibilities
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