design-review

Review source code for SOLID principles and architectural violations.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/tanjed/claude-workflow --skill design-review-tanjed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/tanjed/claude-workflow/tree/main/skills/design-review
Command: npx skills add https://github.com/tanjed/claude-workflow --skill design-review-tanjed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the review of code for SOLID principles violations, design pattern misuse, tight coupling, and architectural boundary violations, providing feedback on code quality and structure.

Core Features & Use Cases

  • SOLID Principle Compliance: Checks for violations of the Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles.
  • Design Pattern Analysis: Identifies design patterns in use and suggests improvements for misapplied patterns.
  • Coupling and Layer Boundary Check: Ensures that business logic is not leaking into controllers, DB queries are not in services, and there are no direct instantiations or cross-layer imports.
  • Code Smell Detection: Flags common code smells like God classes, long parameter lists, feature envy, dead code, and missing early returns.
  • Use Case: When a developer wants to ensure their codebase adheres to best practices and is well-structured before deployment.

Quick Start

Review the code in 'src/main/java' for design and architecture issues.

Frequently Asked Questions about design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SOLID principles compliance checks in my source code?

Automate SOLID principles compliance checks by analyzing source code files to identify Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion violations. The review provides actionable feedback on structural improvements.

What is the best way to detect architectural boundary violations like leaking business logic into controllers?

Detecting architectural boundary violations involves checking layer boundaries to ensure business logic is not leaking into controllers and database queries are not in services. The automated review flags cross-layer imports and direct instantiations.

Can I identify design pattern misuse and common code smells like God classes automatically?

Identifying design pattern misuse and common code smells like God classes, long parameter lists, and feature envy is automated by analyzing the source code structure. The review identifies patterns in use and suggests improvements for misapplied implementations.

Does architectural review work for any source code directory structure?

Architectural review works for any source code directory structure where the files are accessible for analysis. You can target specific directories like 'src/main/java' to review the code for design and architecture issues before deployment.

How do I check for tight coupling and missing early returns in my codebase?

Checking for tight coupling and missing early returns is performed by analyzing source code files for structural dependencies and control flow. The review flags tight coupling and detects common code smells to improve code quality.