clean-code-ch12-emergence

Enforce Kent Beck's four rules of simple design in code reviews.

4|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/hatlesswizard/clean-code-skills --skill clean-code-ch12-emergence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code-ch12-emergence
Source: https://github.com/hatlesswizard/clean-code-skills/tree/main/ch12-emergence
Command: npx skills add https://github.com/hatlesswizard/clean-code-skills --skill clean-code-ch12-emergence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and enforces Kent Beck's four rules of simple design to help codebases achieve emergent design.

Core Features & Use Cases

  • Enforces Rule 1: all tests pass to ensure verifiable behavior
  • Detects duplication and guides refactoring to reduce waste
  • Encourages expressiveness and minimal class/method counts through actionable checks

Quick Start

Run an incremental design review against the target codebase to surface violations and guide remediation.

Frequently Asked Questions about clean-code-ch12-emergence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are Kent Beck's four rules of simple design for emergent design?

Emergent design is achieved by iteratively applying Kent Beck's four rules of simple design: ensuring all tests pass, removing duplication, maximizing expressiveness, and minimizing classes and methods.

How do I enforce simple design rules during code reviews and refactoring?

Run an incremental design review against your codebase to surface violations of simple design rules, checking for duplication, poor expressiveness, and excessive classes to guide refactoring remediation.

Do I need a test suite to apply emergent design principles?

Yes, a test suite is required. Ensuring all tests pass is the first rule of simple design, providing verifiable behavior and a safety net for refactoring and reducing duplication.

How does the Single Responsibility Principle relate to simple design?

The Single Responsibility Principle (SRP) serves as an evaluation criterion for expressiveness. Adhering to SRP alongside Dependency Inversion ensures classes do one thing, minimizing methods and improving emergent design.

What is the best way to reduce code duplication in an existing codebase?

The best way to reduce duplication is performing incremental design reviews that target code smells, enforce simple design rules, and guide refactoring activities to eliminate waste and improve maintainability.