docs(structure): 删除DDD经典分层架构目录结构文档

- 移除了完整的DDD分层架构目录结构说明文档
- 删除了单体工程和微服务工程的目录结构示例
- 移除了DDD核心概念和架构原则相关内容
- 清理了领域驱动设计的最佳实践指南
This commit is contained in:
wandl-6A72h
2026-01-22 16:02:02 +08:00
parent 2d69904d9f
commit c33d3896bf
21 changed files with 84 additions and 254 deletions
+1 -1
View File
@@ -101,7 +101,7 @@
"skills": [
"./skills/code-generator",
"./skills/test-writer",
"./skills/ddd4j-project-builder",
"./skills/ddd4j-project-creator",
"./skills/documentation-builder",
"./skills/full-stack-doc",
"./skills/mcp-builder",
+2 -2
View File
@@ -744,7 +744,7 @@ assistant: "我将使用UI设计师智能体来完成相关方案与文档。"</
### 可用Agent Skills
- ddd-cola, ddd-microservices, ddd-event-driven, ddd-hexagonal-architecture, ddd-clean-architectureDDD架构
- ddd4j-project-builderDDD项目建)
- ddd4j-project-creatorDDD4j项目建)
- plantumlPlantUML
- drawio-architecture架构图绘制
- api-doc-generatorAPI文档生成
@@ -892,7 +892,7 @@ assistant: "我将使用前端开发工程师智能体来完成相关方案与
- mysql, postgresql, oracle, mongodb, redis, elasticsearch数据库
- navicat, dbeaver数据库工具
- ddd-cola, ddd-microservices, ddd-event-driven, ddd-hexagonal-architecture, ddd-clean-architectureDDD架构
- ddd4j-project-builderDDD项目建)
- ddd4j-project-creatorDDD4j项目建)
- code-generator代码生成
- api-doc-generatorAPI文档生成
- documentation-builder文档构建
+1 -1
View File
@@ -331,7 +331,7 @@ python convert_all.py ../skills ../adapters-output
**技能列表:**
- `code-generator` - 代码生成器
- `test-writer` - 测试编写工具
- `ddd4j-project-builder` - DDD 项目建器(支持单体单模块、单体多模块、微服务架构)
- `ddd4j-project-creator` - DDD4j 项目建器(基于 ddd4j-boot支持单体单模块、单体多模块、微服务架构)
- `documentation-builder` - 文档构建工具
- `full-stack-doc` - 全栈文档生成14种文档模板覆盖产品到运维全生命周期
- `mcp-builder` - MCP 构建器
+2 -2
View File
@@ -622,7 +622,7 @@
**Agent Skills**
- ddd-cola, ddd-microservices, ddd-event-driven, ddd-hexagonal-architecture, ddd-clean-architectureDDD架构
- ddd4j-project-builderDDD项目建)
- ddd4j-project-creatorDDD4j项目建)
- plantumlPlantUML
- drawio-architecture架构图绘制
- api-doc-generatorAPI文档生成
@@ -758,7 +758,7 @@
- mysql, postgresql, oracle, mongodb, redis, elasticsearch数据库
- navicat, dbeaver数据库工具
- ddd-cola, ddd-microservices, ddd-event-driven, ddd-hexagonal-architecture, ddd-clean-architectureDDD架构
- ddd4j-project-builderDDD项目建)
- ddd4j-project-creatorDDD4j项目建)
- code-generator代码生成
- api-doc-generatorAPI文档生成
- documentation-builder文档构建
-202
View File
@@ -1,202 +0,0 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-22
View File
@@ -1,22 +0,0 @@
---
name: c4-model
description: Provides comprehensive guidance for C4 model including context diagrams, container diagrams, component diagrams, and code diagrams. Use when the user asks about C4 model, needs to create architecture diagrams, document system architecture, or visualize software architecture.
license: Complete terms in LICENSE.txt
---
## When to use this skill
Use this skill whenever the user wants to:
- [待完善:根据具体工具添加使用场景]
## How to use this skill
[待完善:根据具体工具添加使用指南]
## Best Practices
[待完善:根据具体工具添加最佳实践]
## Keywords
[待完善:根据具体工具添加关键词]
@@ -1,21 +1,66 @@
---
name: ddd4j-project-builder
description: A comprehensive skill for initializing new DDD (Domain-Driven Design) projects and checking existing project structure compliance. Supports three project types: single-module monolith, multi-module monolith, and microservices. Can identify project structure type and validate directory conventions against DDD, Hexagonal Architecture, Clean Architecture, and COLA V5 standards. Use this skill when creating new DDD projects, checking project structure compliance, or migrating existing projects to DDD architecture.
name: ddd4j-project-creator
description: |
A comprehensive skill for creating new ddd4j (Domain-Driven Design for Java) projects based on ddd4j-boot framework.
Use ONLY when the user explicitly mentions creating a ddd4j project, initializing ddd4j project, or setting up
ddd4j-boot project. Supports three project types: single-module monolith, multi-module monolith, and microservices.
Generates project scaffolding based on ddd4j-boot architecture with DDD, Hexagonal Architecture, Clean Architecture,
and COLA V5 patterns. Do NOT trigger for generic DDD projects, JPA/Hibernate projects, or other ORM frameworks
without explicit ddd4j mention.
license: Complete terms in LICENSE.txt
---
# DDD4j Project Initialization and Structure Validation
# DDD4j Project Creator
## When to use this skill
Use this skill whenever you need to:
**CRITICAL: This skill should ONLY be triggered when the user explicitly mentions creating a ddd4j project, initializing ddd4j project, or setting up ddd4j-boot project.**
- **Initialize a new DDD project** with proper directory structure
- **Check existing project structure** compliance with DDD standards
- **Identify project architecture type** (single-module, multi-module, microservices)
- **Validate directory conventions** against DDD patterns
- **Migrate existing projects** to DDD architecture
- **Generate project scaffolding** based on DDD principles
**ALWAYS use this skill when the user mentions:**
- Creating a ddd4j project (explicitly mentions "ddd4j")
- Initializing ddd4j-boot project
- Setting up ddd4j project structure
- Creating ddd4j project scaffolding
- 创建 ddd4j 项目 (explicitly mentions "ddd4j")
- 初始化 ddd4j 项目 (initialize ddd4j project)
- ddd4j-boot 项目创建 (create ddd4j-boot project)
**Trigger phrases include:**
- "创建 ddd4j 项目" (create ddd4j project) - **must include "ddd4j"**
- "初始化 ddd4j 项目" (initialize ddd4j project) - **must include "ddd4j"**
- "创建 ddd4j-boot 项目" (create ddd4j-boot project) - **must include "ddd4j"**
- "使用 ddd4j 创建项目" (create project using ddd4j)
- "ddd4j 项目脚手架" (ddd4j project scaffolding)
**DO NOT trigger this skill for:**
- Generic DDD projects without mentioning ddd4j
- JPA/Hibernate projects
- Other ORM frameworks
- Generic project initialization without ddd4j context
- "创建 DDD 项目" without "ddd4j" (too generic)
- "初始化项目" without "ddd4j" (too generic)
## About DDD4j Boot
**DDD4j Boot** is a Java microservice development scaffold based on **Domain-Driven Design (DDD)** principles. It is built with Spring Boot 3.5.x and uses lightweight [ddd-4-java](https://github.com/fuinorg/ddd-4-java) and [cqrs-4-java](https://github.com/fuinorg/cqrs-4-java) libraries to implement Domain-Driven Design, Command Query Responsibility Segregation (CQRS), and Event Sourcing.
### Core Design Principles
- **Domain-Driven Design (DDD)**: Strategic design through bounded contexts, tactical design with entities, value objects, aggregates, domain services, repositories, and domain events
- **Command Query Responsibility Segregation (CQRS)**: Separation of read and write models, independent optimization
- **Event Sourcing**: State changes recorded as event sequences, supporting complete history and state reconstruction
- **Diamond Architecture (COLA)**: Adapter → Application → Domain ← Infrastructure four-layer architecture
### Key Features
- Complete DDD layered architecture supporting COLA V5 pattern
- Lightweight DDD implementation based on ddd-4-java and cqrs-4-java
- Technology stack integration: Spring Boot 3.5.x, MyBatis Plus, Jackson, Guava, Swagger, SaToken
- Dual stack support: WebMVC (traditional Servlet) and WebFlux (reactive)
- Domain model base capabilities: BaseEntity, BaseRepository, BaseService
- Domain event support with built-in event publishing mechanism
- Anti-Corruption Layer (ACL) for external service integration
- Unified exception handling mechanism
## Project Types Supported
@@ -47,7 +92,9 @@ Use this skill whenever you need to:
## How to use this skill
### For New Project Initialization
**CRITICAL: This skill should ONLY be triggered when the user explicitly mentions creating a ddd4j project. Do NOT trigger for generic DDD project creation requests without ddd4j context.**
### For New DDD4j Project Creation
1. **Identify the project type** from user requirements:
- Single-module monolith → `single-module`
@@ -61,13 +108,14 @@ Use this skill whenever you need to:
- `examples/architecture-patterns.md` - DDD, Hexagonal, Clean, COLA V5 patterns
3. **Collect project information**:
- `groupId`: Maven group ID (e.g., `io.ddd4j.base`)
- `artifactId`: Maven artifact ID (e.g., `ddd4j-douyin`)
- `groupId`: Maven group ID (e.g., `com.github.hiwepy` or `io.ddd4j.base`)
- `artifactId`: Maven artifact ID (e.g., `ddd4j-douyin` or `my-ddd4j-service`)
- `version`: Project version (e.g., `1.0.0-SNAPSHOT`)
- `parentVersion`: Parent POM version (e.g., `2023.0.x.20251205-SNAPSHOT`)
- `packageBase`: Base package name (e.g., `io.ddd4j.douyin`)
- `parentVersion`: Parent POM version (e.g., `2023.0.x.20251205-SNAPSHOT` or reference to `ddd4j-boot-parent`)
- `packageBase`: Base package name (e.g., `io.ddd4j.douyin` or `com.example.service`)
- `modules`: List of business modules (for multi-module/microservices)
- `architecture`: Architecture pattern (DDD Classic, Hexagonal, Clean, COLA V5)
- `ddd4jBootVersion`: DDD4j Boot version (if using ddd4j-boot-bom)
4. **Generate project structure**:
- Create directory structure based on selected type
@@ -225,4 +273,10 @@ See the `examples/` directory for:
## Keywords
ddd, domain-driven design, ddd project, project initialization, project structure, architecture validation, single-module, multi-module, microservices, hexagonal architecture, clean architecture, cola v5, maven project, java project, 领域驱动设计, DDD项目, 项目初始化, 项目结构, 架构验证, 单体单模块, 单体多模块, 微服务, 六边形架构, 整洁架构, COLA架构
**English keywords:**
ddd4j, ddd4j-boot, ddd4j project, create ddd4j project, initialize ddd4j project, ddd4j project creator, ddd4j project scaffolding, ddd4j-boot project, ddd4j project structure, ddd4j-boot initialization, ddd4j microservice, ddd4j monolith
**Chinese keywords (中文关键词):**
ddd4j, ddd4j-boot, ddd4j 项目, 创建 ddd4j 项目, 初始化 ddd4j 项目, ddd4j 项目创建, ddd4j 项目脚手架, ddd4j-boot 项目, ddd4j 项目结构, ddd4j-boot 初始化, ddd4j 微服务, ddd4j 单体应用
**IMPORTANT**: All keywords must include "ddd4j" to avoid false triggers. Generic terms like "DDD 项目" (DDD project) or "创建项目" (create project) without "ddd4j" should NOT trigger this skill.
@@ -265,7 +265,7 @@ src/main/java/{package}/
- 快速参考表:`architecture-directory-quick-reference.md`
- 详细示例:`../examples/architecture-directory-mapping.md`
- DDD 架构参考:`../../ddd4j-project-builder/docs/1、DDD 经典分层架构目录结构.md`
- 六边形架构参考:`../../ddd4j-project-builder/docs/2、六边形架构详细目录结构参考.md`
- 整洁架构参考:`../../ddd4j-project-builder/docs/3、整洁架构详细目录结构参考.md`
- COLA V5 架构参考:`../../ddd4j-project-builder/docs/4、COLA V5 架构详细目录结构参考.md`
- DDD 架构参考:`../../ddd4j-project-creator/docs/1、DDD 经典分层架构目录结构.md`
- 六边形架构参考:`../../ddd4j-project-creator/docs/2、六边形架构详细目录结构参考.md`
- 整洁架构参考:`../../ddd4j-project-creator/docs/3、整洁架构详细目录结构参考.md`
- COLA V5 架构参考:`../../ddd4j-project-creator/docs/4、COLA V5 架构详细目录结构参考.md`
@@ -229,7 +229,7 @@ src/main/java/com/example/order/
## 参考文档
- 详细示例:`examples/architecture-directory-mapping.md`
- DDD 架构参考:`../ddd4j-project-builder/docs/1、DDD 经典分层架构目录结构.md`
- 六边形架构参考:`../ddd4j-project-builder/docs/2、六边形架构详细目录结构参考.md`
- 整洁架构参考:`../ddd4j-project-builder/docs/3、整洁架构详细目录结构参考.md`
- COLA V5 架构参考:`../ddd4j-project-builder/docs/4、COLA V5 架构详细目录结构参考.md`
- DDD 架构参考:`../ddd4j-project-creator/docs/1、DDD 经典分层架构目录结构.md`
- 六边形架构参考:`../ddd4j-project-creator/docs/2、六边形架构详细目录结构参考.md`
- 整洁架构参考:`../ddd4j-project-creator/docs/3、整洁架构详细目录结构参考.md`
- COLA V5 架构参考:`../ddd4j-project-creator/docs/4、COLA V5 架构详细目录结构参考.md`