Clean Code

Clean Code

Overview

Apply clean code principles to produce readable, maintainable, and testable software. This skill covers SOLID principles, DRY application, code smell identification, refactoring patterns, naming conventions, error handling, and complexity management. Based on the works of Robert C. Martin, Martin Fowler, and Kent Beck.

Announce at start: "I'm using the clean-code skill to improve code quality."

---

Phase 1: Analyze Current Code

Goal: Read and understand the code in full context before changing anything.

Actions

1. Read the code in its full context (not just the snippet) 2. Identify the code's responsibility and purpose 3. Measure cyclomatic complexity 4. Map coupling and dependencies 5. Note any existing tests

STOP — Do NOT proceed to Phase 2 until:

• [ ] Code is read in full context
• [ ] Purpose and responsibility are understood
• [ ] Complexity hotspots are identified
• [ ] Existing test coverage is known

---

Phase 2: Identify Code Smells

Goal: Catalog all code smells using the reference tables below.

Bloaters

Object-Orientation Abusers

Change Preventers

Dispensables

STOP — Do NOT proceed to Phase 3 until:

• [ ] All code smells are cataloged
• [ ] Each smell has a priority (high/medium/low)
• [ ] Refactoring approach is identified for each

---

Phase 3: Apply Refactoring

Goal: Apply refactoring patterns one at a time, verifying tests after each.

Actions

1. Apply ONE refactoring at a time 2. Run tests after each change 3. If any test fails, revert immediately 4. Continue until code is clean 5. Review naming, structure, and documentation

STOP — Refactoring complete when:

• [ ] All high-priority smells are resolved
• [ ] All tests pass after each change
• [ ] No behavior was changed during refactoring
• [ ] Code is readable to a new team member

---

SOLID Principles

S — Single Responsibility Principle

A class/module should have one, and only one, reason to change.

Smell: A class that changes for multiple unrelated reasons. Fix: Extract responsibilities into separate classes.

O — Open/Closed Principle

Open for extension, closed for modification.

Smell: Switch statements that grow with new types. Fix: Polymorphism, strategy pattern, or plugin architecture.

L — Liskov Substitution Principle

Subtypes must be substitutable for their base types.

Smell: Subclass overrides method to throw "not supported." Fix: Restructure hierarchy; prefer composition over inheritance.

I — Interface Segregation Principle

No client should depend on methods it does not use.

Smell: Interfaces with many methods; implementors leave some as no-ops. Fix: Split into smaller, focused interfaces.

D — Dependency Inversion Principle

Depend on abstractions, not concretions.

Smell: High-level modules importing low-level modules directly. Fix: Inject dependencies via interfaces/abstract classes.

---

Naming Conventions

Rules

Name Length Guidelines

---

Function Guidelines

Size and Structure

• Functions should do one thing
• Ideal: 5-15 lines (excluding boilerplate)
• Maximum: 30 lines (beyond this, extract)
• Maximum parameters: 3 (beyond this, use options object)

Guard Clauses (Early Return)

// Bad: nested conditions
function getDiscount(user) {
  if (user) {
    if (user.isPremium) {
      if (user.orderCount > 10) {
        return 0.2;
      }
    }
  }
  return 0;
}

// Good: guard clauses
function getDiscount(user) {
  if (!user) return 0;
  if (!user.isPremium) return 0;
  if (user.orderCount <= 10) return 0;
  return 0.2;
}

---

Error Handling Patterns

Decision Table

Result Type Pattern

type Result<T, E = Error> =
  | { success: true; data: T }
  | { success: false; error: E };

function parseConfig(raw: string): Result<Config, ParseError> {
  try {
    const config = JSON.parse(raw);
    if (!isValidConfig(config)) {
      return { success: false, error: new ParseError('Invalid config structure') };
    }
    return { success: true, data: config };
  } catch {
    return { success: false, error: new ParseError('Invalid JSON') };
  }
}

Error Handling Never List

• Never catch and swallow errors silently
• Never use exceptions for control flow
• Never return null to indicate an error
• Never log and rethrow without adding context

---

Complexity Metrics

Reducing Complexity

1. Extract complex conditions into named booleans 2. Replace nested conditionals with guard clauses 3. Use polymorphism instead of type checking 4. Decompose into smaller functions 5. Use lookup tables instead of switch/if chains

---

DRY Application Decision Table

---

Comment Philosophy

Good Comments

Bad Comments (remove and fix code instead)

---

Anti-Patterns / Common Mistakes

---

Integration Points

---

Immutability Preferences

• Default to const (JavaScript/TypeScript)
• Use readonly properties and ReadonlyArray
• Prefer spread/destructuring over mutation
• Use immutable update patterns for state
• Only mutate when performance profiling demands it

---

Skill Type

FLEXIBLE — Apply principles based on context. Not every function needs to be 5 lines; not every pattern needs to be SOLID. Use judgment and optimize for team readability over theoretical purity.