domain-driven-design
适合架构师与大型系统建模，降低业务与代码错配。
用领域驱动设计（DDD）把软件模型围绕业务构建。
把软件模型围绕真实业务建起来，靠 bounded contexts、aggregates 和 ubiquitous language 把代码和业务语义对齐。用在拆单体、划分服务边界或发现代码跟业务不一致时。特点是把业务概念写进代码，用领域事件和上下文映射来控制复杂度，减少沟通误差。
▸ 展开 SKILL.md 英文原文
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", "strategic design", "the code doesnt match the business", or "how do we split this big system". Also trigger when breaking a monolith into services, defining service boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.
帮我安装这个 skill：https://raw.githubusercontent.com/wondelai/skills/main/domain-driven-design/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/wondelai/skills/main/domain-driven-design/SKILL.md"# Domain-Driven Design Framework Framework for tackling software complexity by modeling code around the business domain. The greatest risk in software is not technical failure -- it is building a model that does not reflect how the business actually works. ## Core Principle **The model is the code; the code is the model.** Software should embody a deep, shared understanding of the business domain. When domain experts and developers speak the same language and that language is directly expressed in the codebase, complexity becomes manageable and the system evolves gracefully as the business changes. ## Scoring **Goal: 10/10.** Score a domain model by awarding **1 point per satisfied row