design-patterns

SKILL.md

Design patterns are proven solutions to recurring software design problems. They provide a shared vocabulary for discussing design and capture collective wisdom refined through decades of real-world use.

Core Philosophy: Patterns are templates you adapt to your context, not blueprints to copy. Use the right pattern when it genuinely simplifies your design—not to impress or over-engineer.

| Encapsulate What Varies | Isolate changing parts from stable parts | Changes ripple through codebase | | Program to Interfaces | Depend on abstractions, not concretions | Can't swap implementations | | Composition Over Inheritance | Build behavior by composing objects | Deep rigid class hierarchies |

Use when designing software architecture, refactoring code structure, solving recurring design problems, or when code exhibits symptoms like tight coupling, rigid hierarchies, scattered responsibilities, or difficult-to-test components. Also use when choosing between architectural approaches or reviewing code for structural improvements. Source: ratacat/claude-skills.

View raw