skills.rest
KentoShimizu
KentoShimizuCOMMUNITY
Explore all skills by this author →
𝕏@KStartup_GitHub

architecture-clean-architecture

Enforce clean architectural boundaries between domain, application, and infrastructure layers.

7|Updated Feb 14, 2026
Search Tags:#architecture#clean-architecture#architecture-review#dependency-inversion#domain-boundaries#application-services
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill architecture-clean-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-clean-architecture
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/architecture-clean-architecture
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill architecture-clean-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces clear architectural boundaries between domain, application, and infrastructure to reduce coupling and maintain stable business rules.

Core Features & Use Cases

  • Guides dependency direction and identifies boundary leaks between layers.
  • Defines ports and adapters to isolate infrastructure concerns from domain logic.
  • Supports guided refactoring and team governance for architecture compliance.

Quick Start

Align your project by mapping modules to domain, application, and infrastructure boundaries.

Frequently Asked Questions about architecture-clean-architecture

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

FAQPage Schema
How do I enforce clean architecture boundaries between domain and infrastructure layers?▼

Clean architecture separates business rules from frameworks and delivery mechanisms by strictly dividing modules into domain, application, and infrastructure layers, ensuring dependency direction flows inward toward the domain.

How do I identify dependency inversion points and map ports and adapters during a refactoring?▼

Identifying dependency inversion points requires mapping ports and adapters to isolate infrastructure concerns from domain logic, aligning transaction boundaries with use-case semantics to ensure proper boundary separation during refactoring.

When do I need to separate business rules from frameworks using clean architecture?▼

You need to separate business rules from frameworks when teams must perform system-wide reviews and refactoring to reduce coupling, enforce clear architectural boundaries, and maintain stable domain logic independent of delivery mechanisms.

Does clean architecture work for fixing boundary leaks between application services and domain layers?▼

Clean architecture works for fixing boundary leaks by guiding dependency direction and defining ports and adapters to isolate infrastructure concerns, which supports guided refactoring and team governance for architecture compliance.

What is the best way to align transaction boundaries with use-case semantics in clean architecture?▼

The best way to align transaction boundaries with use-case semantics is to map ports and adapters across domain, application, and infrastructure boundaries, ensuring that architectural boundaries strictly encapsulate business rules.

Related Skills

Explore More Software Engineering Skills→
SatoryKonoSatoryKono
1

architecture-guardian

Identify architectural boundary violations in BioETL code and generate a compliance report.

Community
Advanced
leaderiopleaderiop
7

Advanced Clean Hexagonal Architecture

Guide software engineers in implementing Clean Architecture and Hexagonal patterns for domain isolation.

Community
Advanced
s977043s977043
2

architecture-review

Identify boundary and responsibility misalignments in software architecture.

Community
Basic
hung-phanhung-phan

hexagonal

Implement Hexagonal Architecture to isolate domain logic from infrastructure layers.

Community
Advanced