Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Architecture Patterns
These generic examples explain Clean Architecture, Hexagonal Architecture, and
Domain-Driven Design. They are not GEODE's package blueprint. For GEODE changes,
start with [naming conventions](../../../docs/architecture/naming-conventions.md)
and [dependency review](../dependency-review/SKILL.md); introduce a boundary only
for a demonstrated consumer, substitution need, or ownership constraint.
## When to Use This Skill
- Designing new backend systems from scratch
- Refactoring monolithic applications for better maintainability
- Establishing architecture standards for your team
- Migrating from tightly coupled to loosely coupled architectures
- Implementing domain-driven design principles
- Creating testable and mockable codebases
- Planning microservices decomposition
## Core Concepts
### 1. Clean Architecture (Uncle Bob)
**Layers (dependency flows inward):**
- **Entities**: Core business models
- **Use Cases**: Application business rules
- **Interface Adapters**: Controllers, presenters, gateways
- **Frameworks & Drivers**: UI, database, external services
**Key Principles:**
- Dependencies point inward
…
The line at the top of this page pins the label git:20260907.97cb78b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ytikkns6jcnvdo6u
GET https://markdownregistry.com/api/v1/resolve?ref=mangowhoiscloud/geode/architecture-patterns
GET https://markdownregistry.com/api/v1/blob/215f4fa1b20ae582eee02193534b39aec8bb36210d7fe405d17e5531a865eafa
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
mangowhoiscloud/geode · .agents/skills/codex-mcp-verify/SKILL.md · Use an available Codex MCP integration as a read-only second-opinion verifier for GEODE code reviews, GAP audits, and…
mangowhoiscloud/geode · .agents/skills/docs-link-audit/SKILL.md · Docs 사이트 (`site/` Next.js) 의 본문/JSX/markdown 링크 audit. broken 내부 링크 탐지, build-time copy 인지, 옵트인 HTTP probe. 신규 페이지 추가 /…
mangowhoiscloud/geode · .agents/skills/frontier-harness-research/SKILL.md · Research process for comparing frontier harnesses (Claude Code, Codex, OpenClaw, autoresearch, Prime Agent) with the…
a5c-ai/babysitter · library/methodologies/cc10x/skills/architecture-patterns/SKILL.md · System and API design guidance covering component boundaries, data flow, integration patterns, and scalability…
