[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMRRYTZMN9BR9J4F037YA7":3,"skill-same:01M7EMRRYTZMN9BR9J4F037YA7":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMRRYTZMN9BR9J4F037YA7","ams-ddd-architecture",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-ddd-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ddd-architecture\ndescription: Domain-Driven Design: bounded contexts, ubiquitous language, aggregates, and tactical patterns. Use when modeling complex domains or structuring domain logic.\ncategory: development\n---\n\n# DDD Architecture\n\n## Overview\n\nDomain-Driven Design is **modeling software around the business domain** — building a shared\nlanguage with domain experts and letting that language shape the code. It's two things: strategic\ndesign (bounded contexts, context mapping — where the big seams go) and tactical patterns\n(aggregates, entities, value objects — how the model is built). DDD pays off in complex domains;\nit's overhead in simple CRUD.\n\nThe through-line: the code should speak the business's language, and the boundaries should match\nthe business's reality.\n\n## When to use\n\n- Modeling a complex, nuanced business domain (not simple CRUD).\n- Untangling a big ball of mud into bounded contexts.\n- Designing aggregates, domain events, and invariants.\n- Aligning software boundaries with organizational\u002Fteam reality.\n- Reviewing domain models for anemic or leaked abstractions.\n\n## Core concepts\n\n- **Ubiquitous language.** One shared, precise language used by developers *and* domain experts —\n  in code, docs, and conversation. \"Order,\" \"shipment,\" \"fulfillment\" mean exactly one thing each.\n  When the business uses two words, the code has two concepts; when language is sloppy, the model\n  will be too.\n- **Bounded contexts.** Explicit boundaries within which a model is consistent. The same word can\n  mean different things in different contexts (a \"product\" in catalog vs in shipping) — that's\n  fine *across* contexts, as long as each context is internally coherent and the translation\n  between them is explicit.\n- **Context mapping.** How contexts relate: shared kernel, customer\u002Fsupplier, conformist,\n  anti-corruption layer (ACL), separate ways. The ACL is the workhorse — a translation layer\n  protecting your model from an external system's concepts leaking in.\n- **Aggregates.** Consistency boundaries: a cluster of entities\u002Fvalue objects with one root;\n  all changes go through the root; invariants hold *within* the aggregate. Keep aggregates small\n  — large aggregates cause contention and complexity. One aggregate per transaction is the rule\n  of thumb.\n- **Entities vs value objects.** Entities have identity and lifecycle (`Order` #12345); value\n  objects are defined by their attributes and immutable (`Money(100, USD)`, `Address`). Most\n  domain concepts are values — reach for entities only when identity genuinely matters.\n- **Domain events.** Things that happened (`OrderPlaced`, `PaymentFailed`) — the language of\n  integration between aggregates and contexts. Events enable loose coupling and are the natural\n  fit for eventual consistency across boundaries.\n\n## Practical workflow\n\n1. **Learn the domain.** Event storming with domain experts: what happens, what triggers it, what\n   data's involved. Capture the language they actually use — that's your ubiquitous language seed.\n2. **Find the contexts.** Look for linguistic seams (same word, different meaning), different rates\n   of change, and team boundaries. Draw the context map with relationships labeled.\n3. **Model one context at a time.** Inside a context: identify aggregates (consistency boundaries),\n   their roots, entities vs value objects, and the invariants each aggregate protects.\n4. **Protect the boundaries.** Repositories per aggregate root; ACLs at external integrations;\n   domain events for cross-aggregate communication. Application services orchestrate; domain\n   objects decide.\n5. **Keep the domain pure.** Domain layer has no infrastructure dependencies (no ORM annotations\n   in entities if you can avoid it, no HTTP clients). Infrastructure adapts to the domain, not\n   vice versa.\n6. **Evolve with the language.** When experts change terminology, rename the code. Language drift\n   between business and code is model rot — treat renames as first-class work.\n\nTactical sketch:\n\n```text\nBounded context: Ordering\n  Aggregate: Order (root)\n    - Entities: OrderLine (identity within order)\n    - Value objects: Money, Address, OrderId\n    - Invariants: total == sum(lines); can't add lines after payment\n    - Domain events: OrderPlaced, OrderCancelled\n  Repository: OrderRepository (per aggregate root only)\n  ACL: PaymentGatewayAdapter translates gateway concepts → domain events\n```\n\n## Common pitfalls\n\n- **DDD for CRUD.** Applying aggregates, contexts, and event storming to a simple admin panel.\n  DDD's cost is justified by domain complexity — use the patterns proportionally.\n- **Anemic domain models.** \"Entities\" that are data bags with all logic in services. The domain\n  logic should live *in* the domain objects — that's the point.\n- **Giant aggregates.** An `Order` aggregate containing customer, products, and shipment history\n  — contention, huge transactions, and confused invariants. Small aggregates, referenced by ID.\n- **Leaky contexts.** One context's concepts (or worse, its database tables) used directly by\n  another. Explicit translation at boundaries — ACLs, not shared tables.\n- **Ubiquitous language as documentation.** Writing a glossary nobody uses in code. The language\n  lives in class\u002Fmethod names — if the code says `OrderManagerUtil`, the language failed.\n- **Event obsession.** Publishing domain events for everything, creating distributed-monolith\n  coupling through event choreography. Events for meaningful business occurrences, not every\n  state change.\n- **Analysis paralysis.** Modeling the perfect domain for months before shipping. Model the core\n  subdomain deeply; be pragmatic elsewhere (generic subdomains can be simple CRUD).\n","# DDD Architecture\n\n## Overview\n\nDomain-Driven Design is **modeling software around the business domain** — building a shared\nlanguage with domain experts and letting that language shape the code. It's two things: strategic\ndesign (bounded contexts, context mapping — where the big seams go) and tactical patterns\n(aggregates, entities, value objects — how the model is built). DDD pays off in complex domains;\nit's overhead in simple CRUD.\n\nThe through-line: the code should speak the business's language, and the boundaries should match\nthe business's reality.\n\n## When to use\n\n- Modeling a complex, nuanced business domain (not simple CRUD).\n- Untangling a big ball of mud into bounded contexts.\n- Designing aggregates, domain events, and invariants.\n- Aligning software boundaries with organizational\u002Fteam reality.\n- Reviewing domain models for anemic or leaked abstractions.\n\n## Core concepts\n\n- **Ubiquitous language.** One shared, precise language used by developers *and* domain experts —\n  in code, docs, and conversation. \"Order,\" \"shipment,\" \"fulfillment\" mean exactly one thing each.\n  When the business uses two words, the code has two concepts; when language is sloppy, the model\n  will be too.\n- **Bounded contexts.** Explicit boundaries within which a model is consistent. The same word can\n  mean different things in different contexts (a \"product\" in catalog vs in shipping) — that's\n  fine *across* contexts, as long as each context is internally coherent and the translation\n  between them is explicit.\n- **Context mapping.** How contexts relate: shared kernel, customer\u002Fsupplier, conformist,\n  anti-corruption layer (ACL), separate ways. The ACL is the workhorse — a translation layer\n  protecting your model from an external system's concepts leaking in.\n- **Aggregates.** Consistency boundaries: a cluster of entities\u002Fvalue objects with one root;\n  all changes go through the root; invariants hold *within* the aggregate. Keep aggregates small\n  — large aggregates cause contention and complexity. One aggregate per transaction is the rule\n  of thumb.\n- **Entities vs value objects.** Entities have identity and lifecycle (`Order` #12345); value\n  objects are defined by their attributes and immutable (`Money(100, USD)`, `Address`). Most\n  domain concepts are values — reach for entities only when identity genuinely matters.\n- **Domain events.** Things that happened (`OrderPlaced`, `PaymentFailed`) — the language of\n  integration between aggregates and contexts. Events enable loose coupling and are the natural\n  fit for eventual consistency across boundaries.\n\n## Practical workflow\n\n1. **Learn the domain.** Event storming with domain experts: what happens, what triggers it, what\n   data's involved. Capture the language they actually use — that's your ubiquitous language seed.\n2. **Find the contexts.** Look for linguistic seams (same word, different meaning), different rates\n   of change, and team boundaries. Draw the context map with relationships labeled.\n3. **Model one context at a time.** Inside a context: identify aggregates (consistency boundaries),\n   their roots, entities vs value objects, and the invariants each aggregate protects.\n4. **Protect the boundaries.** Repositories per aggregate root; ACLs at external integrations;\n   domain events for cross-aggregate communication. Application services orchestrate; domain\n   objects decide.\n5. **Keep the domain pure.** Domain layer has no infrastructure dependencies (no ORM annotations\n   in entities if you can avoid it, no HTTP clients). Infrastructure adapts to the domain, not\n   vice versa.\n6. **Evolve with the language.** When experts change terminology, rename the code. Language drift\n   between business and code is model rot — treat renames as first-class work.\n\nTactical sketch:\n\n```text\nBounded context: Ordering\n  Aggregate: Order (root)\n    - Entities: OrderLine (identity within order)\n    - Value objects: Money, Address, OrderId\n    - Invariants: total == sum(lines); can't add lines after payment\n    - Domain events: OrderPlaced, OrderCancelled\n  Repository: OrderRepository (per aggregate root only)\n  ACL: PaymentGatewayAdapter translates gateway concepts → domain events\n```\n\n## Common pitfalls\n\n- **DDD for CRUD.** Applying aggregates, contexts, and event storming to a simple admin panel.\n  DDD's cost is justified by domain complexity — use the patterns proportionally.\n- **Anemic domain models.** \"Entities\" that are data bags with all logic in services. The domain\n  logic should live *in* the domain objects — that's the point.\n- **Giant aggregates.** An `Order` aggregate containing customer, products, and shipment history\n  — contention, huge transactions, and confused invariants. Small aggregates, referenced by ID.\n- **Leaky contexts.** One context's concepts (or worse, its database tables) used directly by\n  another. Explicit translation at boundaries — ACLs, not shared tables.\n- **Ubiquitous language as documentation.** Writing a glossary nobody uses in code. The language\n  lives in class\u002Fmethod names — if the code says `OrderManagerUtil`, the language failed.\n- **Event obsession.** Publishing domain events for everything, creating distributed-monolith\n  coupling through event choreography. Events for meaningful business occurrences, not every\n  state change.\n- **Analysis paralysis.** Modeling the perfect domain for months before shipping. Model the core\n  subdomain deeply; be pragmatic elsewhere (generic subdomains can be simple CRUD).\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-ddd-architecture",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-ddd-architecture",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-ddd-architecture",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-ddd-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-ddd-architecture\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]