Apply Software Patterns

Overview

Use this skill to make design decisions practical, not dogmatic. Start from the real problem and codebase constraints, then recommend the smallest design move that improves readability, maintainability, testability, and room to grow.

Prefer incremental refactors over big rewrites. When a pattern is not justified, say so clearly and keep the design simpler.

Treat pattern names as tools, not goals. The target is code that another engineer can read, trace, modify, and test without needing a pattern catalog open beside them.

When To Use This Skill

Use this skill when the task involves any of the following: