[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FTB7ESNNZPVC3EFNYHDCDY":3,"skill-same:01M6FTB7ESNNZPVC3EFNYHDCDY":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6FTB7ESNNZPVC3EFNYHDCDY","domain-driven-design",null,"Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fdata\u002Fdomain-driven-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"driven","domain driven design","domain","design","implementation","strategic","modeling","self","tactical","bounded-context","route","patterns","context","work","plan","architecture patterns","ddd","architecture","safe","2026-11-10 10:12:30",false,"---\nname: domain-driven-design\ndescription: \"Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.\"\nrisk: safe\nsource: self\ntags: [ddd, domain, bounded-context, architecture]\n---\n\n# Domain-Driven Design\n\n## Use this skill when\n\n- You need to model a complex business domain with explicit boundaries.\n- You want to decide whether full DDD is worth the added complexity.\n- You need to connect strategic design decisions to implementation patterns.\n- You are planning CQRS, event sourcing, sagas, or projections from domain needs.\n\n## Do not use this skill when\n\n- The problem is simple CRUD with low business complexity.\n- You only need localized bug fixes.\n- There is no access to domain knowledge and no proxy product expert.\n\n## Instructions\n\n1. Run a viability check before committing to full DDD.\n2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary.\n3. Route to specialized skills based on current task.\n4. Define success criteria and evidence for each stage.\n\n### Viability check\n\nUse full DDD only when at least two of these are true:\n\n- Business rules are complex or fast-changing.\n- Multiple teams are causing model collisions.\n- Integration contracts are unstable.\n- Auditability and explicit invariants are critical.\n\n### Routing map\n\n- Strategic model and boundaries: `@ddd-strategic-design`\n- Cross-context integrations and translation: `@ddd-context-mapping`\n- Tactical code modeling: `@ddd-tactical-patterns`\n- Read\u002Fwrite separation: `@cqrs-implementation`\n- Event history as source of truth: `@event-sourcing-architect` and `@event-store-design`\n- Long-running workflows: `@saga-orchestration`\n- Read models: `@projection-patterns`\n- Decision log: `@architecture-decision-records`\n\nIf templates are needed, open `references\u002Fddd-deliverables.md`.\n\n## Output requirements\n\nAlways return:\n\n- Scope and assumptions\n- Current stage (strategic, tactical, or evented)\n- Explicit artifacts produced\n- Open risks and next step recommendation\n\n## Examples\n\n```text\nUse @domain-driven-design to assess if this billing platform should adopt full DDD.\nThen route to the right next skill and list artifacts we must produce this week.\n```\n\n## Limitations\n\n- This skill does not replace direct workshops with domain experts.\n- It does not provide framework-specific code generation.\n- It should not be used as a justification to over-engineer simple systems.\n","# Domain-Driven Design\n\n## Use this skill when\n\n- You need to model a complex business domain with explicit boundaries.\n- You want to decide whether full DDD is worth the added complexity.\n- You need to connect strategic design decisions to implementation patterns.\n- You are planning CQRS, event sourcing, sagas, or projections from domain needs.\n\n## Do not use this skill when\n\n- The problem is simple CRUD with low business complexity.\n- You only need localized bug fixes.\n- There is no access to domain knowledge and no proxy product expert.\n\n## Instructions\n\n1. Run a viability check before committing to full DDD.\n2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary.\n3. Route to specialized skills based on current task.\n4. Define success criteria and evidence for each stage.\n\n### Viability check\n\nUse full DDD only when at least two of these are true:\n\n- Business rules are complex or fast-changing.\n- Multiple teams are causing model collisions.\n- Integration contracts are unstable.\n- Auditability and explicit invariants are critical.\n\n### Routing map\n\n- Strategic model and boundaries: `@ddd-strategic-design`\n- Cross-context integrations and translation: `@ddd-context-mapping`\n- Tactical code modeling: `@ddd-tactical-patterns`\n- Read\u002Fwrite separation: `@cqrs-implementation`\n- Event history as source of truth: `@event-sourcing-architect` and `@event-store-design`\n- Long-running workflows: `@saga-orchestration`\n- Read models: `@projection-patterns`\n- Decision log: `@architecture-decision-records`\n\nIf templates are needed, open `references\u002Fddd-deliverables.md`.\n\n## Output requirements\n\nAlways return:\n\n- Scope and assumptions\n- Current stage (strategic, tactical, or evented)\n- Explicit artifacts produced\n- Open risks and next step recommendation\n\n## Examples\n\n```text\nUse @domain-driven-design to assess if this billing platform should adopt full DDD.\nThen route to the right next skill and list artifacts we must produce this week.\n```\n\n## Limitations\n\n- This skill does not replace direct workshops with domain experts.\n- It does not provide framework-specific code generation.\n- It should not be used as a justification to over-engineer simple systems.\n",{"name":5,"risk":47,"tags":53,"source":36,"description":7},[45,31,38,46],"master","dff58085da947e81e8418c922055644bf0082b1b","data\u002Fdomain-driven-design","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add reikiplanet\u002Fdaoskills --skill domain-driven-design",{"tool":68,"command":69},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill domain-driven-design",{"tool":71,"command":72},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill domain-driven-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fdata\u002Fdomain-driven-design\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fddd-deliverables.md","REFERENCE","参考文档",615,"https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fdata\u002Fdomain-driven-design\u002Freferences\u002Fddd-deliverables.md",[83,110,122,137,156,179],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":48},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"games","web games","web","grep","principles","selection","community","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":48},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[117,118,108,119,120,96,98,99,100,93,121,94],"ar","vr ar","interaction","requirements","performance",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":48},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[124,129,130,131,132,133,96,134,100,135,136,93],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":48},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[144,145,40,146,147,96,148,149,150,151,134,152,153,154,155],"wcag audit patterns","wcag audit","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":48},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,96,100,93,171,94,172,173,174,175,176,177,178],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":48},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[35,186,187,188,189,190,191,46,176,134,192,193,194,96,195,196,197,173,198,199],"threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]