clean-architecture

Apply Clean Architecture rules to enforce dependency direction and boundary isolation.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/moughamir/justwaitit-review --skill clean-architecture-moughamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-architecture
Source: https://github.com/moughamir/justwaitit-review/tree/main/.agents/skills/clean-architecture
Command: npx skills add https://github.com/moughamir/justwaitit-review --skill clean-architecture-moughamir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clean Architecture helps you reduce tangled dependencies and fragile codebases by structuring software into clear layers with enforceable rules for direction of dependencies, boundaries, and responsibilities.

Core Features & Use Cases

  • Dependency direction rules: apply principles that prevent cyclic dependencies and keep inner layers from depending on outer layers.
  • Boundary and isolation guidance: design use cases and entities so they stay independent of frameworks, databases, and delivery mechanisms.
  • Architecture review & refactoring support: use the rule catalog to systematically refactor toward better separation of concerns.

Quick Start

Use the clean-architecture skill to review a module you plan to refactor and identify which Clean Architecture rule(s) are currently being violated.

Frequently Asked Questions about clean-architecture

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

FAQPage Schema
How do I fix cyclic dependencies and tangled module layers in my codebase?

To refactor coupled modules, map existing design decisions to Clean Architecture rules such as inward-only dependencies and boundary isolation, then systematically restructure code so entities and use cases stay independent of frameworks and databases.

What is the best way to isolate domain entities from database and framework dependencies?

Framework and persistence isolation is achieved by designing use cases and entities behind architectural boundaries, using ports and input-output modeling to keep inner layers independent of delivery mechanisms and external systems.

How do I review code structure to identify Clean Architecture violations?

Code structure review involves mapping design decisions against a rule catalog of Clean Architecture principles, checking for single-responsibility workflows, boundary isolation, and correct dependency direction to identify violated rules in coupled modules.

Can I use Clean Architecture principles for designing new systems, or is it only for refactoring?

Clean Architecture principles apply to both designing new systems and refactoring existing coupled modules, providing enforceable rules for dependency direction, boundary isolation, and single-responsibility workflows across entities, use cases, layers, and adapters.

When should I not use layered architecture with strict dependency inversion?

Layered architecture with strict dependency inversion may be unnecessary for small, simple scripts or prototypes where the overhead of defining ports, adapters, and architectural boundaries exceeds the complexity of the business logic itself.