Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/u9401066/rootcause-mcp/master/.claude/skills/ddd-architect/SKILL.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/u9401066/rootcause-mcp/ddd-architect)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/ddd-architect"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/ddd-architect.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01780 |
| Opus 5 | $0.00000 | $0.00890 |
| Sonnet 5 | $0.00000 | $0.00356 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
ddd-architect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to ddd-architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DDD 架構輔助技能
描述
確保前後端程式碼遵循 DDD 架構與 DAL 分離原則。
觸發條件
- 「建立新功能」「新增模組」
- 「架構檢查」
- 建立新檔案時自動檢查
- 「前端架構」「後端架構」
法規依據
- 憲法:CONSTITUTION.md 第 1、2 條
- 子法:.github/bylaws/ddd-architecture.md
🔧 後端 DDD 結構 (Python/Go/Rust)
新功能腳手架
當建立新功能時,自動生成 DDD 結構:
「新增 Order 領域」
生成:
src/
├── Domain/
│ ├── Entities/Order.py
│ ├── ValueObjects/OrderId.py
│ ├── Aggregates/OrderAggregate.py
│ └── Repositories/IOrderRepository.py
├── Application/
│ ├── UseCases/CreateOrder.py
│ └── DTOs/OrderDTO.py
└── Infrastructure/
└── Persistence/Repositories/OrderRepository.py
層級職責
| 層級 | 職責 | 可依賴 |
|---|---|---|
| Domain | 業務規則、Entity、Value Object | 無外部依賴 |
| Application | Use Case、DTO、編排 | Domain |
| Infrastructure | Repository 實作、外部 API | Domain |
| Presentation | API、CLI、UI | Application |
⚛️ 前端 DDD 結構 (React/Vue)
React 專案結構
「新增 User 管理功能 (React)」
生成:
src/
├── domain/
│ ├── models/
│ │ └── User.ts # Entity 類型定義
│ ├── types/
│ │ └── UserTypes.ts # Value Object 類型
│ └── rules/
│ └── userValidation.ts # 純業務規則(無框架依賴)
│
├── application/
│ ├── hooks/
│ │ └── useUser.ts # 業務邏輯 Hook
│ ├── stores/
│ │ └── userStore.ts # 狀態管理 (Zustand/Redux)
│ └── services/
│ └── UserService.ts # 應用服務(編排)
│
├── infrastructure/
│ ├── api/
│ │ └── userApi.ts # API Client (fetch/axios)
│ ├── storage/
│ │ └── userStorage.ts # LocalStorage/SessionStorage
│ └── adapters/
│ └── userAdapter.ts # API Response → Domain Model
│
└── presentation/
├── components/
│ └── UserCard.tsx # UI 元件
├── pages/
│ └── UserListPage.tsx # 頁面
└── layouts/
└── UserLayout.tsx # 佈局
Vue 3 專案結構
「新增 Product 管理功能 (Vue)」
生成:
src/
├── domain/
│ ├── models/
│ │ └── Product.ts
│ ├── types/
│ │ └── ProductTypes.ts
│ └── rules/
│ └── productValidation.ts
│
├── application/
│ ├── composables/
│ │ └── useProduct.ts # Composition API
│ ├── stores/
│ │ └── productStore.ts # Pinia Store
│ └── services/
│ └── ProductService.ts
│
├── infrastructure/
│ ├── api/
│ │ └── productApi.ts
│ └── adapters/
│ └── productAdapter.ts
│
└── presentation/
├── components/
│ └── ProductCard.vue
├── views/
│ └── ProductListView.vue
└── layouts/
└── ProductLayout.vue
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 235 lines · 0 tokens per session scan A f56a7fe55192
ddd-architect is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,780 tokens. A static security scan graded it A with 0 findings. It is 100% identical to ddd-architect, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
architecture-patterns
Software architecture patterns and best practices.
tsq-ddd
A guide to Domain-Driven Design, a way to shape software around real business concepts and language. It covers defining clear business boundaries, shared terms, and relationships between parts of a system.
ddd-aggregate-modeling
Guides aggregate modeling decisions for DDD services: aggregate root boundaries, child entity vs value object decisions, invariants, snapshot/primitives mapping, specification/criteria usage, and repository contract design. Invoked when the user asks to model or refactor domain entities and aggregate behavior.
domain-driven-design
Design and review software using patterns from Eric Evans' "Domain-Driven Design." Use for DDD tactical patterns (Entities, Value Objects, Aggregates, Repositories, Factories, Domain Services), strategic patterns (Bounded Context, Context Map, Anticorruption Layer, Shared Kernel, Open Host Service), supple design…
domain-modeling
DDD practical guide: Event Storming, Bounded Contexts, Aggregates and domain-driven design patterns.
ddd-architect
A code-organization guide based on Domain-Driven Design, an approach that keeps business rules separate from application actions, outside systems, and user interfaces. It also separates data-access code from the rest of the application.