Design software systems using Clean Architecture principles and dependency rules.
npx skills add https://github.com/onesyntax/skills --skill architecture-onesyntax
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/onesyntax/skills/tree/main/skills/architecture Command: npx skills add https://github.com/onesyntax/skills --skill architecture-onesyntax
This Skill provides a practical framework for designing software systems using Clean Architecture principles, helping teams separate concerns and manage dependencies.
Follow the Architecture Workflow when designing a new feature or reviewing architecture decisions. Identify layers, apply the dependency rule, define use cases and boundary data structures, and ensure boundaries are expressed via interfaces.
High-intent search queries and answers about installing and using this skill.
Clean architecture separates concerns by structuring software into layers: entities, use cases, interface adapters, and frameworks. You define boundaries, apply the dependency rule, and ensure data crossing boundaries are simple DTOs to maintain system maintainability.
The dependency rule in clean architecture dictates that dependencies must point inward toward higher-level policies. Source code dependencies must only point inward toward entities, ensuring inner layers remain isolated from frameworks and delivery mechanisms.
To define boundaries and use cases, identify architectural layers, map feature requirements to use cases, and express boundaries via interfaces. Data crossing boundaries must be simple DTOs, never entities or database rows, keeping interactors and presenters decoupled.
Yes, clean architecture supports planning feature design, module boundaries, and architectural reviews across teams. It guides teams through applying SOLID principles and the dependency rule to verify that entities remain isolated from frameworks during reviews.
Data crossing boundaries in clean architecture must be simple data structures or DTOs. They must never be entities or database rows, ensuring that interactors and presenters remain decoupled from framework and delivery mechanisms.
Avoid clean architecture when the overhead of defining interactors, presenters, and boundary DTOs outweighs the need for maintainability. If a feature does not require strict separation of concerns or long-term dependency management, simpler designs may be better.
DevXojeValidate dependency rules and layer boundaries for Clean Architecture compliance.
DGouronApplies Clean Architecture to organize modules, entities, use cases, and adapters.
bRRRITSCOLDApply pragmatic SOLID principles to design interfaces and implement dependency injection.
as4584Implement Clean Architecture, Hexagonal Architecture, and Domain-Driven Design for backend systems.
