How does the skill handle module communication?

It enforces sacred boundaries where modules only communicate through public contracts (APIs or events) and never reach into another module's internals.

Can this skill help document technical decisions?

Yes, it includes guidelines and templates for Architectural Decision Records (ADRs) to capture context, alternatives, and trade-offs.

Does this skill favor feature-based or layer-based folders?

It strongly recommends organizing by feature (e.g., /users, /orders) rather than by layer (e.g., /services, /models) to keep related code together.

What is the 'North Star' of this Architecture skill?

The primary goal is ensuring that small changes stay local. A feature should ideally touch only 1-2 modules rather than requiring edits across the entire system.

What layers does this architecture skill support?

It follows a 3-layer approach: Presentation (UI), Logic (Business Rules), and Data (Persistence), with a strict one-way dependency flow.

Architectural Design Patterns

Name: Architectural Design Patterns
Author: AlexanderStephenThompson

byAlexanderStephenThompson

API Development

Enforces robust architectural principles, module boundaries, and design patterns to ensure code maintainability and scalability.

About

The Architecture skill provides Claude with a comprehensive framework for building scalable and maintainable software systems. It emphasizes a 'North Star' goal where small changes remain local to 1-2 modules, preventing system-wide regressions. By enforcing explicit wiring over magic, sacred module boundaries, and feature-based organization, this skill helps developers avoid common pitfalls like circular dependencies and 'shotgun surgery.' It also provides structured guidance on testing strategies, observability, and documenting architectural decision records (ADRs) to maintain project health as complexity grows.

Key Features

Identifies architectural 'smells' like God Objects and Shotgun Surgery.
Enforces strict module boundaries through public API contracts and index files.
Standardizes documentation for major technical choices using ADR templates.
0 GitHub stars
Implements a validated three-layer dependency flow (Presentation, Logic, Data).
Guides feature-based project organization to keep related code cohesive.

Use Cases

Auditing a project for circular dependencies and layer violations.
Refactoring a monolithic codebase into clean, independent modules.
Setting up a scalable project structure for a new backend service.

About

Key Features

Identifies architectural 'smells' like God Objects and Shotgun Surgery.
Enforces strict module boundaries through public API contracts and index files.
Standardizes documentation for major technical choices using ADR templates.
0 GitHub stars
Implements a validated three-layer dependency flow (Presentation, Logic, Data).
Guides feature-based project organization to keep related code cohesive.

Use Cases

Auditing a project for circular dependencies and layer violations.
Refactoring a monolithic codebase into clean, independent modules.
Setting up a scalable project structure for a new backend service.