architecture patterns

Design Community

Skill notes

When to Use This Skill

Designing new backend services or microservices from scratch Refactoring monolithic applications where business logic is entangled with ORM models or HTTP concerns Establishing bounded contexts before splitting a system into services Debugging dependency cycles where infrastructure code bleeds into the domain layer Creating testable codebases where use-case tests do not require a running database

1. Clean Architecture (Uncle Bob)

Layers (dependency flows inward): Entities: Core business models, no framework imports Use Cases: Application business rules, orchestrate entities Interface Adapters: Controllers, presenters, gateways — translate between use cases and external formats Frameworks & Drivers: UI, database, external services — all at the outermost ring

2. Hexagonal Architecture (Ports and Adapters)

Components: Domain Core: Business logic lives here, framework-free Ports: Abstract interfaces that define how the core interacts with the outside world (driving and driven) Adapters: Concrete implementations of ports (PostgreSQL adapter, Stripe adapter, REST adapter) Benefits:

3. Domain-Driven Design (DDD)

Strategic Patterns: Bounded Contexts: Isolate a coherent model for one subdomain; avoid sharing a single model across the whole system Context Mapping: Define how contexts relate (Anti-Corruption Layer, Shared Kernel, Open Host Service) Ubiquitous Language: Every term in code matches the term used by domain experts Tactical Patterns:

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wshobson · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview architecture-patterns.preview
# Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.