Enforce clean architecture principles for module design and boundary contracts.
npx skills add https://github.com/lekman/cdn --skill clean-architecture-lekman
Please help me install this Agent Skill. Skill: clean-architecture Source: https://github.com/lekman/cdn/tree/main/.claude/skills/clean-architecture Command: npx skills add https://github.com/lekman/cdn --skill clean-architecture-lekman
Enforces clean architecture principles to guide module design and boundary contracts, reducing architectural drift and confusion across teams.
Apply the clean-architecture guidelines when starting a new module to ensure boundaries.
High-intent search queries and answers about installing and using this skill.
To enforce clean architecture boundaries during a module refactor, apply structured principles that separate code into Business Logic, Interface, and System Implementation layers. This ensures inward dependencies and clear separation of concerns for maintainable modules.
Preventing architectural drift requires codifying per-boundary interfaces and modularization requirements. By enforcing clear ownership and separation of concerns during architectural reviews, teams reduce confusion and maintain consistent module design.
Yes, you can apply clean architecture guidelines across languages and platforms during system design. The guidelines codify inward dependencies, per-boundary interfaces, and modularization requirements independent of any specific technology stack.
Organize code folders using module-based structures and barrel exports to improve maintainability and testability. This approach enforces per-boundary interfaces and separates Business Logic from System Implementation layers for clearer ownership.
Define per-boundary interfaces when starting a new module to ensure boundaries and separation of concerns. This practice prevents architectural drift by codifying contracts between Business Logic, Interface, and System Implementation layers.
Separating business logic from system implementation reduces confusion by enforcing inward dependencies. This separation ensures the inner Business Logic layer remains isolated behind boundary interfaces, making module ownership and architectural contracts explicit.
ralvarezdevDefines domain-owned ports and implements adapters to enforce inward dependency flow in hexagonal architecture.
chiubakaValidate TypeScript barrel file structures to enforce public API boundaries.
ArabelaTsoAnalyze Python codebases to identify component boundaries and detect architectural violations.
billybbuffumStructure Go applications into domain, application, and infrastructure layers.
