AgentSkillsCN

architecture-ddd

在复杂领域中，运用领域驱动设计流程来建模有界上下文、聚合以及上下文地图。当需界定系统边界、模块间关系，以及架构层面的约束时，可选用此流程；但若仅对单个模块进行重构且不涉及架构层面的影响，则不宜使用。

SKILL.md
--- frontmatter
name: architecture-ddd
description: "Domain-driven design workflow for modeling bounded contexts, aggregates, and context maps in complex domains. Use when system boundaries, module relationships, and architecture-level constraints are being defined; do not use for single-module implementation refactors without architecture impact."

Architecture Ddd

Trigger Boundary

  • •Use when domain complexity or terminology conflicts drive design risk.
  • •Do not use for implementation-layer dependency rules; use architecture-clean-architecture.
  • •Do not use for diagram-only communication; use architecture-c4-modeling.

Goal

Create domain-aligned architecture boundaries with explicit ubiquitous language and ownership.

Shared Architecture Contract (Canonical)

  • •Use skills/architecture-principles/references/architecture-governance-contract.md as the only schema source.
  • •Validate all IDs, lifecycle states, and gate rules against the canonical contract.
  • •Do not define local ID formats or alternate state machines.

Compliance & Governance Baseline (US, Japan, EU)

  • •Model privacy-sensitive concepts explicitly in ubiquitous language.
  • •Isolate regulated data concerns within bounded contexts.
  • •Prepare an ARC-CMP-* evidence package for governance review.

Inputs

  • •Domain events, processes, and terminology sources
  • •Stakeholder language conflicts and ownership boundaries
  • •Business invariants and critical consistency rules

Outputs

  • •Bounded context map with integration relationships
  • •Aggregate and entity boundary definitions
  • •Ubiquitous language glossary and ownership model

Workflow

  1. •Discover domain language and conflicting meanings.
  2. •Define bounded contexts and ownership boundaries.
  3. •Model aggregates around consistency invariants.
  4. •Create context map with integration and anti-corruption patterns.
  5. •Align team boundaries with context ownership.

Quality Gates

  • •Bounded contexts have clear ownership and purpose.
  • •Aggregates enforce explicit invariants.
  • •ARC-CMP-* evidence package is complete and approved.
  • •Greenfield designs exclude fallback paths; brownfield rollback requires trigger and runbook.

Failure Handling

  • •Stop when context boundaries are purely technical.
  • •Stop when canonical contract validation fails.
  • •Escalate when invariant ownership is ambiguous across teams.