# Solid Single Responsibility

> Each class should encapsulate a single concept or responsibility Use when designing system architecture. Architecture category skill.

- Skill: `majiayu000/solid-single-responsibility` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/solid-single-responsibility`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/solid-single-responsibility/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/majiayu000/solid-single-responsibility

---


# SOLID - Single Responsibility

Each class should encapsulate a single concept or responsibility. If a class has methods that change for different reasons (UI changes vs. business logic vs. persistence), split it. Signs of SRP violation: large classes, many dependencies, god objects, difficulty naming the class. Apply this at module level too—each module should have a cohesive purpose.