Reducing Complexity
Managing complexity is software's primary technical imperative - all other goals are secondary
Install
npx skills add obra/clank --skill Reducing Complexitygit clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/architecture/reducing-complexity ~/.claude/skills/Reducing-ComplexityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Reducing Complexity ## Overview **Managing complexity is the most important technical topic in software development.** All other technical goals—performance, features, elegance—are secondary to managing complexity. **Core principle:** "There are two ways of constructing a software design: one way is to make it so simple that there are *obviously* no deficiencies, and the other is to make it so complicated that there are no *obvious* deficiencies." - C.A.R. Hoare **Always choose the first way.** ## When to Use **Use as guiding principle for EVERY technical decision:** - Design decisions (class structure, subsystems, interfaces) - Implementation decisions (algorithms, data structures) - Refactoring decisions (what to simplify) - Architecture decisions (how to partition system) - Code review (primary evaluation criterion) **Warning signs of complexity overload:** - Can't keep design in mind all at once - Need to understand entire system to change one part - Applying methods mechanically without knowing why - Code works but you're not sure how - Difficult to explain how code works - Many edge cases and special conditions - Deep nesting (if inside if inside if...) - Long parameter lists (> 7 parameters) - Large routines that do many things - Classes with unclear purpose ## Two Types of Complexity ### Essential Complexity Inherent in the real-world problem itself. Can't be eliminated, only managed. **Examples:** - Interfacing with complex, disorderly real world
Details
- Skill name
Reducing Complexity- Repository
- obra/clank
- Path
skills/architecture/reducing-complexity/SKILL.md- Repo updated
- 9 October 2025
FAQ
What does the Reducing Complexity skill do?
Managing complexity is software's primary technical imperative - all other goals are secondary
How do I install the Reducing Complexity skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Reducing Complexity. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Reducing Complexity popular?
It lives in obra/clank, which has 43 GitHub stars and 26 forks.
Related skills
Gardening Skills Wiki
43obra/clank
Maintain skills wiki health - check links, naming, cross-references, and coverage
Remembering Conversations
43obra/clank
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Brainstorming Ideas Into Designs
43obra/clank
Interactive idea refinement using Socratic method to develop fully-formed designs
Refactoring Safely
43obra/clank
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
Pre Mortem
62ElliotJLT/Claude-Skill-Potions
Before starting ANY significant task (feature build, refactor, integration, migration, or architectural change), first imagine the project has failed. Generate 3-5 specific failure scenarios, assess risk levels, identify mitigations, then adjust the implementation plan to address high-risk items FIRST. Do not start coding until the pre-mortem is acknowledged.
Requesting Code Review
43obra/clank
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.