Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When designing a new Python service/component, refactoring a God class or monolithic function, deciding between abstraction and duplication, evaluating PRs for coupling issues, or choosing inheritance vs composition.
references/details.md for deeper patternsCleaner, testable Python code with clear responsibility separation, reduced coupling, and justified abstractions; easier maintenance and review.
Use Cases
A developer is building a new microservice and must decide how to layer responsibilities between API, service, and repository. Using this skill, they apply SRP and dependency direction rules, avoid a God class, and inject dependencies for testability. Result: a modular service that is easy to unit test and extend without entangled I/O and business logic.
A team lead reviews a PR where a class imports from the API layer and has 7 constructor params. They invoke this skill to identify the layering violation and oversized class, suggest splitting by reason-to-change and introducing a shared models layer. Result: cleaner architecture, smaller constructors, and prevented future coupling bugs.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File