agentleFS
Cor-IncorporatedCor-Incorporated/claude-code-skills/skills/modern-architecture/SKILL.md

modern-architecture

Skill5 starsChanged 2 months agoMITView on GitHub

Design features using DDD + TDD + Clean Architecture + Event-Driven + API-First patterns for TypeScript, Python, and Go. Use when: designing features with domain complexity (Entities, Value Objects, Aggregates), structuring projects with layer separation, defining Bounded Contexts, applying Outside-In TDD, designing CQRS or Event Sourcing, creating API contracts before implementation, starting a new project architecture. Trigger phrases: DDD, TDD, clean architecture, hexagonal, ports and adapters, CQRS, event sourcing, API-first, domain model, bounded context. Do NOT use for: simple scripts, one-off utilities, UI-only components without domain logic, or CRUD-only endpoints with no business rules.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All domain objects return new instances.

    line 114

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Modern Architecture

DDD + TDD + Clean Architecture + Event-Driven + API-First for TS/Python/Go.

Decision Tree

New feature or module?
|
+- Complex business rules?
|  YES -> DDD Tactical Patterns (references/ddd-tactical.md)
|  |
|  +- Different stakeholders use different terms for same concept?
|  |  YES -> Bounded Contexts (references/ddd-strategic.md)
|  |
|  +- External system integration?
|  |  YES -> Anti-Corruption Layer (references/ddd-strategic.md)
|  |
|  +- Read/write patterns differ significantly?
|     YES -> CQRS (references/event-driven.md)
|
+- Has API surface?
|  YES -> Contract-First: schema before code (references/api-first.md)
|
+- Needs async/real-time communication?
|  YES -> Event-Driven (references/event-driven.md)
|
+- Any of the above?
   YES -> Clean Architecture layers (references/clean-architecture.md)
   NO  -> Simple module, skip this skill
<important if="applying Outside-In TDD with DDD or starting a new feature with domain discovery"> ## Core Workflow: Outside-In Development

1. Domain Discovery

Define ubiquitous language. List domain events in past tense.

Domain: Order Management
Events: OrderPlaced, OrderCancelled, PaymentReceived
Aggregates: Order, Payment, Shipment

2. Contract First (if API exists)

Define API schema before writing code. See references/api-first.md.

3. Outside-In TDD

Acceptance Test (RED) -> Domain Test (RED->GREEN) -> Use Case Test (RED->GREEN) -> Adapter (GREEN) -> Acceptance (GREEN) -> Refactor

Full workflow in references/tdd-ddd-workflow.md. </important>

<important if="structuring a project with Clean Architecture layers or creating module directory layout"> ### 4. Layer Implementation
domain/           -> Entities, VOs, Events, Ports (zero dependencies)
application/      -> Use Cases, Commands, Queries (depends on domain only)
infrastructure/   -> DB adapters, API controllers (depends on all)

Dependency Rule: Inner layers NEVER import outer layers.

Directory Structure

src/modules/{context-name}/
  domain/
    model/           # Aggregate Root, Entities, Value Objects
    events/          # Domain Events (past tense)
    ports/           # Repository & Service interfaces
    services/        # Domain Services (stateless)
  application/
    use-cases/       # One class per use case
    dto/             # Commands & Queries
  infrastructure/
    persistence/     # Repository implementations + Mappers
    api/             # HTTP Controllers / GraphQL Resolvers
    messaging/       # Event publishers / subscribers
</important><important if="naming DDD entities, value objects, events, repositories, or commands"> ## Naming Conventions
ConceptPatternExample
EntityDomain nounOrder, Customer
Value ObjectImmutable conceptMoney, Address, Email
Domain EventPast tenseOrderPlaced, PaymentReceived
Use CaseVerb phrasePlaceOrder, CancelOrder
Repository{Aggregate}RepositoryOrderRepository
PortInterface in domainPaymentGateway
Adapter{Tech}{Port}StripePaymentGateway
Command{Action}{Noun}CommandPlaceOrderCommand
QueryGet{Noun}QueryGetOrderQuery
</important><important if="implementing domain objects or reviewing domain model mutations"> ## Immutability Rule

All domain objects return new instances. Never mutate.

// CORRECT: return new instance
addItem(item: OrderItem): Order {
  return new Order(this.id, [...this._items, item], this._status)
}

// WRONG: mutation
addItem(item: OrderItem): void {
  this._items.push(item)  // VIOLATION
}
</important><important if="planning test strategy for a Clean Architecture project"> ## Test Pyramid
LayerTypeDependenciesTarget
DomainUnitNone (pure)less than 1ms
ApplicationUnitMocked portsless than 10ms
InfrastructureIntegrationReal DBless than 500ms
E2EAcceptanceFull stackless than 3s
</important><important if="deciding whether to apply DDD or assessing over-engineering risk"> ## Error Handling
SituationAction
Domain complexity unclearStart with simple module; extract domain layer when rules emerge
Bounded Context boundaries uncertainMap team/stakeholder language first; split where language diverges
Existing codebase has no layersIntroduce layers incrementally; start with domain extraction
Over-engineering riskIf entity has no business rules, use plain DTO -- skip DDD
</important>

References

  • references/ddd-tactical.md -- Entity, VO, Aggregate, Repository, Domain Event, Factory (TS/Python/Go)
  • references/ddd-strategic.md -- Bounded Context, Context Map, Anti-Corruption Layer
  • references/clean-architecture.md -- Layers, Ports and Adapters, DI, testing per layer
  • references/event-driven.md -- Event Bus, CQRS, Event Sourcing, Pub/Sub
  • references/api-first.md -- OpenAPI, tRPC, GraphQL, versioning, error contracts
  • references/tdd-ddd-workflow.md -- Outside-In TDD phases, property-based testing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.