Verified:GitHub

code-architecture

Define module boundaries and file layouts using Clean Architecture or Hexagonal patterns.

Updated Mar 27, 2026

Search Tags:#architecture #solid #clean-architecture #hexagonal-architecture #ports-and-adapters #feature-based #module-boundaries

Ready to run

npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill code-architecture-cenredjun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-architecture
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/code-architecture
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill code-architecture-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps developers understand how to structure software using established architecture patterns to improve maintainability, testability, and long-term evolution. It clarifies when to use Clean Architecture, Hexagonal, feature-based organization, and other patterns, and contrasts them with anti-patterns.

Core Features & Use Cases

Clear definitions of major patterns (Clean Architecture, Hexagonal, feature-based organization, vertical slice).
Guidance on module boundaries, ports and adapters, testing strategies, and ADR-style decision records.
Practical examples and anti-pattern warnings to guide teams in choosing the right pattern for their context.

Quick Start

Review the guide and apply Clean Architecture or Hexagonal patterns to structure a sample module.

Frequently Asked Questions about code-architecture

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

FAQPage Schema

What is the difference between Clean Architecture and Hexagonal Architecture?▼

Clean Architecture layers dependencies strictly inward toward domain entities, while Hexagonal Architecture emphasizes ports and adapters to symmetrize infrastructure interactions. Both patterns isolate business logic to improve testability and maintainability for single-application projects.

How do I structure a project using feature-based organization?▼

Feature-based organization structures code by vertical business capabilities rather than technical layers. You define strict module boundaries around each feature, grouping its domain logic, UI, and infrastructure together to improve maintainability and scalability.

When should I use vertical slice architecture over traditional layered architecture?▼

Use vertical slice architecture when you want to reduce artificial coupling between technical layers and simplify cross-cutting changes. It organizes code by feature slices rather than horizontal layers, avoiding the anti-pattern of unnecessary dependencies in maintainable code.

How do ports and adapters work to improve software testability?▼

Ports and adapters define strict boundaries between application core logic and external infrastructure. By programming against port interfaces and injecting infrastructure adapters, you isolate side effects and enable independent unit testing of the domain.

Does this architecture guidance apply to single-application projects seeking scalable organization?▼

Yes, this architecture guidance specifically targets single-application projects seeking scalable organization. It provides decision records and module boundary specifications to structure software patterns effectively for maintainable, long-term code evolution.