Software Patterns

A decision framework that tells you which architectural patterns to apply and when, covering the foundational ones (Dependency Injection, SOA) and situational ones (Repository, Domain Events, Circuit Breaker, Anti-Corruption Layer). The philosophy is problem-first: it gives you decision trees based on specific pain points like "code is hard to test" or "one slow service breaks everything" rather than pattern catalogs to memorize. Useful when designing new systems, adding integrations, or refactoring existing architecture. The best part is the explicit anti-YAGNI warnings, like stopping you from adding patterns preemptively or cargo-culting "best practices" without understanding what problem they solve.

skills.sh installs: 382
GitHub stars: 79
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bobmatnyc/claude-mpm-skills --skill software-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

Software Patterns Primer

Overview

Architectural patterns solve specific structural problems. This skill provides a decision framework for when to apply each pattern, not a catalog to memorize.

Core philosophy: Patterns solve problems. No problem? No pattern needed.

When to Use This Skill

Activate when:

Designing a new system or major feature
Adding external service integrations
Code becomes difficult to test or modify
Services start calling each other in circles
Failures in one component cascade to others
Business logic scatters across multiple locations

Pattern Hierarchy

Foundational (Apply by Default)

These patterns provide the structural foundation for maintainable systems. Apply unless you have specific reasons not to.

Pattern	Problem Solved	Signal to Apply
Dependency Injection	Tight coupling, untestable code	Classes instantiate their own dependencies
Service-Oriented Architecture	Monolithic tangles, unclear boundaries	Business logic scattered, no clear ownership

DI quick example — before and after:

SKILL.md on GitHub