[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XG8WFPG25QC25SS5Q1F40W":3,"skill-same:01M6XG8WFPG25QC25SS5Q1F40W":81},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":14,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6XG8WFPG25QC25SS5Q1F40W","domain-driven-design",null,"Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\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,48],"driven","domain driven design","domain","design","[ddd, domain, bounded-context, architecture]","2026","strategic","modeling","self","tactical","bounded-context","route","patterns","implementation","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]\"\ndate_added: \"2026-02-27\"\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":48,"tags":33,"source":37,"date_added":54,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fdomain-driven-design","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill domain-driven-design",{"tool":67,"command":68},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill domain-driven-design",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill domain-driven-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fdomain-driven-design\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fddd-deliverables.md","REFERENCE","参考文档",615,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fdomain-driven-design\u002Freferences\u002Fddd-deliverables.md",[82,103,129,139,152,169],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":49},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[92,93,94,95,96,32,97,98,99,100,101,102],"wechat search","wechat","search","capabilities","openclaw","web search","compliance","web","official","fetch","with",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":49},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[110,111,112,113,114,115,94,116,117,118,119,120,121,122,123,124,125,126,127,128],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":49},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[136,137,110,121,122,123,124,114,94,126,138,127,128,120,118,117,116,125,115,113],"trend radar","radar","pulse",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":49},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[146,147,148,149,150,151],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":49},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[154,99,162,163,164,102,121,165,166,167,112,168,125],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":49},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[171,176,177,178,125,179,166,180,181,182,183,184],"status","play","go","latest","github","discover","control","cmd","volume"]