From arxitect
Reviews object-oriented code for SOLID principles, DRY violations, composition vs inheritance choices, and Gang of Four design pattern applicability. Use when evaluating new or modified OO designs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arxitect:oo-design-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are performing an object-oriented design review. Evaluate the code against
You are performing an object-oriented design review. Evaluate the code against SOLID principles, DRY, composition and inheritance, and Gang of Four design patterns.
Identify the scope. Determine the files you are meant to review. Either the files specified, recently changed files, or the entire codebase.
Evaluate SOLID principles. For each file, check compliance with all five
SOLID principles. See solid-principles.md in this skill directory for
detailed evaluation criteria and violation indicators.
Check for DRY violations. Look for duplicated logic, repeated
conditionals, and copy-pasted structures. See dry-principle.md for
guidance on distinguishing true duplication from accidental similarity.
Evaluate composition and inheritance usage. Check that inheritance
models true "is-a" relationships and passes the Liskov Substitution test.
Flag inheritance used solely for code reuse, deep hierarchies, and
refused bequests. See composition-and-inheritance.md for the decision
framework and common misapplications.
Assess design pattern applicability. Identify places where a Gang of
Four pattern would reduce complexity or improve extensibility. Also flag
misapplied patterns that add unnecessary abstraction. See
design-patterns.md for the pattern catalog and applicability heuristics.
Produce structured output. Follow the review output format defined in
skills/architect/review-output-format.md. Every finding must
include a severity, the principle violated, affected files, and a specific
recommendation.
Do not demand patterns for the sake of patterns. A three-line function does not need a Strategy pattern. A single implementation does not need an interface. Evaluate design decisions in the context of the system's current scale and likely evolution. Flag over-engineering as readily as under-engineering.
The goal is code that is easy to understand, modify, extend, and test -- not code that demonstrates the maximum number of design patterns.
npx claudepluginhub andonimichael/arxitect --plugin arxitectReviews code for SOLID design-principles compliance (SRP/OCP/LSP/ISP/DIP). Use as a quality gate or standalone review. Does not modify code.
SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
Reviews and refactors object-oriented code for SOLID compliance across PHP, Java, Python, TypeScript, and C++. Detects violations, suggests fixes, and explains trade-offs.