feat: Add DDD skills, bundles, workflows
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"generatedAt": "2026-02-08T00:00:00.000Z",
|
||||
"total": 864,
|
||||
"total": 868,
|
||||
"skills": [
|
||||
{
|
||||
"id": "3d-web-experience",
|
||||
@@ -8167,6 +8167,88 @@
|
||||
],
|
||||
"path": "skills/dbt-transformation-patterns/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "ddd-context-mapping",
|
||||
"name": "ddd-context-mapping",
|
||||
"description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
|
||||
"category": "architecture",
|
||||
"tags": [
|
||||
"ddd",
|
||||
"context-map",
|
||||
"anti-corruption-layer",
|
||||
"integration"
|
||||
],
|
||||
"triggers": [
|
||||
"ddd",
|
||||
"context-map",
|
||||
"anti-corruption-layer",
|
||||
"integration",
|
||||
"context",
|
||||
"mapping",
|
||||
"map",
|
||||
"relationships",
|
||||
"between",
|
||||
"bounded",
|
||||
"contexts",
|
||||
"define"
|
||||
],
|
||||
"path": "skills/ddd-context-mapping/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "ddd-strategic-design",
|
||||
"name": "ddd-strategic-design",
|
||||
"description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
|
||||
"category": "architecture",
|
||||
"tags": [
|
||||
"ddd",
|
||||
"strategic-design",
|
||||
"bounded-context",
|
||||
"ubiquitous-language"
|
||||
],
|
||||
"triggers": [
|
||||
"ddd",
|
||||
"strategic-design",
|
||||
"bounded-context",
|
||||
"ubiquitous-language",
|
||||
"strategic",
|
||||
"artifacts",
|
||||
"including",
|
||||
"subdomains",
|
||||
"bounded",
|
||||
"contexts",
|
||||
"ubiquitous",
|
||||
"language"
|
||||
],
|
||||
"path": "skills/ddd-strategic-design/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "ddd-tactical-patterns",
|
||||
"name": "ddd-tactical-patterns",
|
||||
"description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
|
||||
"category": "architecture",
|
||||
"tags": [
|
||||
"ddd",
|
||||
"tactical",
|
||||
"aggregates",
|
||||
"value-objects",
|
||||
"domain-events"
|
||||
],
|
||||
"triggers": [
|
||||
"ddd",
|
||||
"tactical",
|
||||
"aggregates",
|
||||
"value-objects",
|
||||
"domain-events",
|
||||
"apply",
|
||||
"code",
|
||||
"entities",
|
||||
"value",
|
||||
"objects",
|
||||
"repositories",
|
||||
"domain"
|
||||
],
|
||||
"path": "skills/ddd-tactical-patterns/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "debugger",
|
||||
"name": "debugger",
|
||||
@@ -8821,6 +8903,33 @@
|
||||
],
|
||||
"path": "skills/docx-official/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "domain-driven-design",
|
||||
"name": "domain-driven-design",
|
||||
"description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
|
||||
"category": "architecture",
|
||||
"tags": [
|
||||
"ddd",
|
||||
"domain",
|
||||
"bounded-context",
|
||||
"architecture"
|
||||
],
|
||||
"triggers": [
|
||||
"ddd",
|
||||
"domain",
|
||||
"bounded-context",
|
||||
"architecture",
|
||||
"driven",
|
||||
"plan",
|
||||
"route",
|
||||
"work",
|
||||
"strategic",
|
||||
"modeling",
|
||||
"tactical",
|
||||
"evented"
|
||||
],
|
||||
"path": "skills/domain-driven-design/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "dotnet-architect",
|
||||
"name": "dotnet-architect",
|
||||
|
||||
@@ -211,6 +211,63 @@
|
||||
"notes": "Classify failures by root cause: selector drift, timing, environment, data."
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "design-ddd-core-domain",
|
||||
"name": "Design a DDD Core Domain",
|
||||
"description": "Workflow to model complex domains and implement tactical and evented patterns with explicit boundaries.",
|
||||
"category": "architecture",
|
||||
"relatedBundles": [
|
||||
"core-dev",
|
||||
"ops-core"
|
||||
],
|
||||
"steps": [
|
||||
{
|
||||
"title": "Assess DDD fit and scope",
|
||||
"goal": "Decide if full DDD is justified and define the modeling scope.",
|
||||
"recommendedSkills": [
|
||||
"domain-driven-design",
|
||||
"architecture-decision-records"
|
||||
],
|
||||
"notes": "Document why DDD is needed, where to keep it lightweight, and what success looks like."
|
||||
},
|
||||
{
|
||||
"title": "Create strategic model",
|
||||
"goal": "Define subdomains, bounded contexts, and ubiquitous language.",
|
||||
"recommendedSkills": [
|
||||
"ddd-strategic-design"
|
||||
],
|
||||
"notes": "Classify subdomains and assign ownership before making implementation decisions."
|
||||
},
|
||||
{
|
||||
"title": "Map context relationships",
|
||||
"goal": "Define context integration patterns, ownership, and translation boundaries.",
|
||||
"recommendedSkills": [
|
||||
"ddd-context-mapping"
|
||||
],
|
||||
"notes": "Prefer explicit contracts and anti-corruption layers where domain models diverge."
|
||||
},
|
||||
{
|
||||
"title": "Implement tactical model",
|
||||
"goal": "Encode invariants with aggregates, value objects, repositories, and domain events.",
|
||||
"recommendedSkills": [
|
||||
"ddd-tactical-patterns",
|
||||
"test-driven-development"
|
||||
],
|
||||
"notes": "Start from invariants and transaction boundaries, not from tables or endpoints."
|
||||
},
|
||||
{
|
||||
"title": "Adopt evented patterns selectively",
|
||||
"goal": "Apply CQRS, event store, projections, and sagas only where required.",
|
||||
"recommendedSkills": [
|
||||
"cqrs-implementation",
|
||||
"event-store-design",
|
||||
"projection-patterns",
|
||||
"saga-orchestration"
|
||||
],
|
||||
"notes": "Use evented patterns where consistency and scale tradeoffs are explicit and accepted."
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user