Piloting Ddd
Use when adding new features to an existing non-DDD codebase (legacy, monolith, "屎山") and wanting to introduce DDD discipline. Use when the project has no DDD structure (no ports, adapters, bounded contexts) but needs a clean new feature. Use when asked to "add DDD to legacy code", "build a clean feature in a messy codebase", "introduce DDD without rewriting everything", or "create a DDD island i…
Test Driven Development
>
Ddd Protocol
Shared DDD workflow protocols referenced by all skills. Contains the Ambiguity Handling Protocol (STOP/ASSUME), Persistence Defense Reference (3-layer model + hooks enforcement), Domain Architecture Reference (red lines), Spec Change Detection Reference, Per-Phase Subagent Dispatch Protocol, Platform Detection Reference (unified platform detection + constraint/hook paths), and Cross-Skill Traceab…
Language Conventions
>
Defining Schemas
Use when Phase 4 technical solution is approved and concrete schema files need to be generated before behavior contracts (SDD) and coding. Use when tempted to write code without formal interface definitions, database schemas, or error catalogs. Schema定义, proto生成, DDL, 错误码, openapi, asyncapi, event schema.
Snapshotting Code Context
Use when iterating on an existing codebase (DDD-structured or partially-structured) where docs/ddd/ is empty (archived or never generated). Use when code exists but phase artifacts are missing — the code IS the source of truth, not old documents. Use when asked to "understand the current state", "rebuild context from code", or "prepare for iteration". Also used by restructuring-ddd as Step 1 on n…
Designing Contracts First
Use when two bounded contexts need to communicate, when defining cross-context APIs, or when tempted to directly import types from another context's package — even in a monorepo. Use when encountering cross-context coupling, missing anti-corruption layers, or shared domain models across boundaries. 契约优先, 防腐层, ACL, anti-corruption layer, port interface.
Restructuring Ddd
Use when fully restructuring an existing non-DDD project into DDD hexagonal architecture. Big-bang approach — reverse-engineer, design, refactor entirely. Use when asked to "convert to DDD", "restructure to hexagonal", "rewrite properly", "migrate from MVC/monolith to DDD". 全面重构, 非DDD转DDD, MVC转六边形, 大重构, restructure to DDD, monolith to hexagonal.
Architecting Technical Solution
Use when making technology choices — database selection, framework decisions, sync vs async, REST vs gRPC — especially when choices are made implicitly or "obvious" without documenting trade-offs. Use when transitioning from approved contracts to domain coding, or when an agent starts coding with implicit architectural assumptions. Symptoms include picking PostgreSQL/Redis/Kafka "by default" with…
Extracting Domain Events
Use when receiving a PRD, feature request, or business requirements — especially when requirements seem obvious or a design doc already exists. Use when tempted to jump straight to database schemas, API endpoints, or code. Symptoms include skipping failure path analysis and missing compensating events. 需求分析, 事件风暴, event storming, domain events.
Importing Technical Solution
Use when user has an existing technical solution, architecture document, or design spec and wants to onboard it into the DDD pipeline. Use when a tech solution exists but lacks structured DDD artifacts, or when reverse-engineering existing decisions into phase artifacts. 导入技术方案, 已有方案, 接入DDD, import to DDD, existing tech solution, import technical solution, reverse-engineer.
Mapping Bounded Contexts
Use when determining system boundaries, setting up a new module, or encountering a shared God-object model (e.g. a User struct used across multiple domains). Use when facing vocabulary drift, terms used inconsistently, or code organized by technical layers instead of business capabilities. 划分上下文, bounded context, context map, ubiquitous language.
Ddd Review
>
Full Ddd
Use when starting a new project or module from a PRD, feature spec, or business requirements — even when requirements seem simple. Use when asked to "architect a system from scratch", "turn these requirements into code", "build this feature end-to-end", or when onboarding AI into a codebase lacking DDD structure. Also use when translating whiteboard EventStorming into code. 从零开始, 新项目, 全流程, PRD to…
Coding Isolated Domains
Use when implementing core business logic, domain entities, or aggregates. Use when encountering anemic models (entities with only getters/setters), ORM tags or HTTP logic leaking into domain structs, public SetStatus() methods, or business logic living in services instead of entities. 充血模型, 六边形架构, 领域层隔离, rich domain model, hexagonal architecture.
Spec Driven Development
>
Mapping Legacy Landscape
Use when analyzing a non-DDD legacy codebase to understand its structure before introducing DDD. Use when the codebase is MVC, layered, monolithic, or unstructured ("屎山"). Use when asked to "understand the legacy code", "map the existing system", "find where to introduce DDD", or "analyze the codebase before adding a feature". 遗留地形图, 屎山分析, legacy analysis, brownfield mapping, 映射遗留代码, map legacy c…
Iterating Ddd
Use when adding new features or requirements to an existing DDD-structured project where a previous iteration has been completed and archived. Use when docs/ddd/ is empty after archival and new requirements arrive. Use when asked to "iterate on the existing design", "add a feature to the DDD project", "extend the bounded contexts", or "evolve the domain model". 迭代DDD, 增量需求, 新功能迭代, extend domain,…