[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPB5HWQ8GMAHJN7DHN2M50":3,"skill-same:01M6MPB5HWQ8GMAHJN7DHN2M50":113},{"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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6MPB5HWQ8GMAHJN7DHN2M50","ddd-best-practices",null,"DDD（领域驱动设计）架构最佳实践指南。当用户在 Java\u002FSpring Boot 项目中遇到分层架构、领域建模、模块边界、代码评审或测试分层问题时使用。包括：纠结是否引入 application\u002Fapi\u002Fquerys 模块；设计或审查实体、聚合、仓储、防腐层、领域事件；贫血模型重构（setter 全开、规则全在 Service）；多入口共享用例是否补 application 层；策略模式 Map 注入、责任链、Node 流程编排的取舍；Controller 测试 @WebMvcTest vs @SpringBootTest 选型；MVC 渐进迁移 DDD；DDD 命名规范。仅适用 Java\u002FSpring Boot 生态，Go\u002FPython\u002FNode 等其他语言不适用。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"ddd best practices","best practices","ddd","controller","规则","service","application","map","node","spring","api","testing","spring boot","java","boot","python","go","design","2026-11-10 10:12:30",false,"---\nname: ddd-best-practices\ndescription: \"DDD（领域驱动设计）架构最佳实践指南。当用户在 Java\u002FSpring Boot 项目中遇到分层架构、领域建模、模块边界、代码评审或测试分层问题时使用。包括：纠结是否引入 application\u002Fapi\u002Fquerys 模块；设计或审查实体、聚合、仓储、防腐层、领域事件；贫血模型重构（setter 全开、规则全在 Service）；多入口共享用例是否补 application 层；策略模式 Map 注入、责任链、Node 流程编排的取舍；Controller 测试 @WebMvcTest vs @SpringBootTest 选型；MVC 渐进迁移 DDD；DDD 命名规范。仅适用 Java\u002FSpring Boot 生态，Go\u002FPython\u002FNode 等其他语言不适用。\"\n---\n\n# DDD Best Practices\n\n## Overview\n\n面向 Java \u002F Spring Boot 项目的 DDD 落地指南，提供分层决策、领域建模、代码模板、测试策略、审查清单与重构路线图。\n\n**Core principle:** 先判断复杂度与边界 -> 先收紧依赖与模型 -> 先补关键测试 -> 再按真实信号演进分层与模式。\n\n**Announce at start:** \"正在使用 ddd-best-practices skill 为你提供 DDD 架构指导。\"\n\n## Prerequisites\n\n- 目标项目为 Java \u002F Spring Boot 技术栈\n- 非 Java 项目（Go \u002F Python \u002F Node）请勿使用本 skill\n\n## Workflow\n\n### Phase 1: 判断当前阶段，选择对应参考\n\n根据用户的问题类型，读取对应的 reference 文档：\n\n| 用户场景 | 读取文档 |\n|---|---|\n| 初始化 \u002F 新模块设计 | [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) → [project-structure.md](references\u002Fproject-structure.md) |\n| 领域建模 \u002F 聚合 \u002F ACL 设计 | [domain-modeling.md](references\u002Fdomain-modeling.md) |\n| 快速落地查模板 | [code-templates.md](references\u002Fcode-templates.md)（~1100 行，用顶部对照表定位） |\n| 命名拿不准 | [naming-conventions.md](references\u002Fnaming-conventions.md) |\n| 测试策略 \u002F TDD 落地 | [testing-strategy.md](references\u002Ftesting-strategy.md) |\n| 代码审查 \u002F 边界收紧 | [code-review-checklist.md](references\u002Fcode-review-checklist.md) → [boundary-smells.md](references\u002Fboundary-smells.md) |\n| MVC → DDD 渐进重构 | [refactoring-guide.md](references\u002Frefactoring-guide.md) |\n| 复杂规则建模 \u002F 流程编排 | [design-patterns.md](references\u002Fdesign-patterns.md)（~900 行，按目录跳转） |\n\n### Phase 2: 确保最小闭环\n\n在给出建议时，优先检查这 5 条基线是否满足，再考虑引入更多抽象：\n\n1. `domain` 纯净，依赖方向正确\n2. `trigger` 不直接依赖 `repository \u002F mapper \u002F 外部客户端`\n3. `repository` 接口不暴露 `refreshCache \u002F evictCache \u002F cacheXxx` 等技术语义\n4. ACL \u002F 外部适配器返回领域对象，而不是把外部 DTO 直接带进领域\n5. 关键不变量有领域单元测试，并按职责边界补齐各层测试\n\n### Phase 3: 按场景执行\n\n#### 场景 A: 新项目 \u002F 新模块\n\n1. 用 [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) 判断最小可行分层\n2. 用 [project-structure.md](references\u002Fproject-structure.md) 选择目录结构与 POM 多模块依赖\n3. 用 [domain-modeling.md](references\u002Fdomain-modeling.md) 设计实体 \u002F 值对象 \u002F 聚合 \u002F 仓储 \u002F Port\n4. 用 [code-templates.md](references\u002Fcode-templates.md) 按层拷贝代码骨架\n5. 命名拿不准时查 [naming-conventions.md](references\u002Fnaming-conventions.md)\n6. 用 [testing-strategy.md](references\u002Ftesting-strategy.md) 规划测试分层\n7. 只在规则明显膨胀时，再引入 [design-patterns.md](references\u002Fdesign-patterns.md) 中的模式\n\n#### 场景 B: 测试策略与 TDD 落地\n\n1. 先判断当前要验证的是**领域规则**、**用例编排**、**HTTP 契约**，还是**持久化\u002F外部集成**风险\n2. 领域规则优先写纯单测，不启动 Spring；关键不变量在 Entity \u002F VO \u002F DomainService 层锁住\n3. `application \u002F use case` 只测编排、事务边界、幂等与跨聚合协调；可 mock 仓储接口、Port，不要 mock Entity \u002F VO\n4. Controller 默认使用 `@WebMvcTest + MockMvc`；默认 mock 应用服务 \u002F use case\n5. Repository \u002F Adapter \u002F 复杂 Mapper 通过集成测试验证，必要时使用 Testcontainers\n6. 仅保留少量 `@SpringBootTest` 烟雾测试验证关键全链路 wiring\n\n#### 场景 C: 审查与边界收紧\n\n1. 用 [code-review-checklist.md](references\u002Fcode-review-checklist.md) 做结构化检查\n2. 用 [boundary-smells.md](references\u002Fboundary-smells.md) 对照常见反模式\n3. 检查测试边界：是否用 controller 测试兜底领域规则、是否大量 mock mapper、是否缺少集成测试\n4. 先修\"依赖方向、边界绕过、DTO 穿透、缓存语义泄漏、测试边界错位\"\n5. 修完后立刻补领域测试与关键集成测试，锁住行为\n\n#### 场景 D: MVC 到 DDD 重构\n\n1. 先识别限界上下文与用例边界\n2. 先封装 Repository \u002F Port，再重构模型\n3. 先做最小模块拆分，避免一次性把 `application \u002F api \u002F querys` 全预埋\n4. 优先把关键规则沉回模型或领域服务\n5. 每次边界收紧前后，优先补 `domain` 与 `application` 层的保护性测试\n\n### Phase 4: 判断是否继续演进\n\n只有当出现真实信号时，再建议引入：\n\n| 信号 | 引入 |\n|---|---|\n| 多入口共用同一用例编排、跨聚合编排膨胀 | `application` 层 |\n| 需要对外发布\u002F复用 RPC 契约 | `api` 模块 |\n| 出现独立读模型、CQRS、报表\u002F搜索等读侧复杂性 | `querys` 模块 |\n| 跨聚合一致性问题已真实出现 | 领域事件 \u002F MQ |\n\n## Common Mistakes\n\n- **为了\"像 DDD\"而盲目补层**：模块数量不是成熟度的代名词，先满足当前复杂度\n- **Domain 层混入技术细节**：不要在 `domain` 中放 Spring \u002F MyBatis \u002F Redis \u002F HTTP 客户端\n- **先上模式再有场景**：两个 `if-else` 不值得上责任链 \u002F 决策树\n- **用一种测试覆盖所有**：领域规则、编排、HTTP 契约和持久化风险应按责任边界分层测试\n- **`@SpringBootTest` 当默认**：Controller 默认使用切片测试，Repository \u002F Adapter 默认使用真实集成测试\n- **大量 mock mapper**：若 `application \u002F domain` 测试必须 mock mapper，优先回看职责划分是否混乱\n\n## References\n\n- [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) — 分层增减决策矩阵\n- [project-structure.md](references\u002Fproject-structure.md) — 渐进式项目结构与 Maven 多模块 POM\n- [domain-modeling.md](references\u002Fdomain-modeling.md) — 领域建模指南 + 速查模板\n- [code-templates.md](references\u002Fcode-templates.md) — 按层代码模板速查 + 端到端示例（~1100 行，用顶部对照表定位）\n- [naming-conventions.md](references\u002Fnaming-conventions.md) — 包\u002F类\u002F接口\u002F方法\u002F数据库命名速查\n- [design-patterns.md](references\u002Fdesign-patterns.md) — 领域层模式落地范式（~900 行，按目录跳转）\n- [testing-strategy.md](references\u002Ftesting-strategy.md) — DDD 测试分层与 Mock 边界\n- [code-review-checklist.md](references\u002Fcode-review-checklist.md) — DDD 代码审查清单\n- [boundary-smells.md](references\u002Fboundary-smells.md) — 常见边界异味与修复策略\n- [refactoring-guide.md](references\u002Frefactoring-guide.md) — MVC 到 DDD 渐进重构指南\n","# DDD Best Practices\n\n## Overview\n\n面向 Java \u002F Spring Boot 项目的 DDD 落地指南，提供分层决策、领域建模、代码模板、测试策略、审查清单与重构路线图。\n\n**Core principle:** 先判断复杂度与边界 -> 先收紧依赖与模型 -> 先补关键测试 -> 再按真实信号演进分层与模式。\n\n**Announce at start:** \"正在使用 ddd-best-practices skill 为你提供 DDD 架构指导。\"\n\n## Prerequisites\n\n- 目标项目为 Java \u002F Spring Boot 技术栈\n- 非 Java 项目（Go \u002F Python \u002F Node）请勿使用本 skill\n\n## Workflow\n\n### Phase 1: 判断当前阶段，选择对应参考\n\n根据用户的问题类型，读取对应的 reference 文档：\n\n| 用户场景 | 读取文档 |\n|---|---|\n| 初始化 \u002F 新模块设计 | [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) → [project-structure.md](references\u002Fproject-structure.md) |\n| 领域建模 \u002F 聚合 \u002F ACL 设计 | [domain-modeling.md](references\u002Fdomain-modeling.md) |\n| 快速落地查模板 | [code-templates.md](references\u002Fcode-templates.md)（~1100 行，用顶部对照表定位） |\n| 命名拿不准 | [naming-conventions.md](references\u002Fnaming-conventions.md) |\n| 测试策略 \u002F TDD 落地 | [testing-strategy.md](references\u002Ftesting-strategy.md) |\n| 代码审查 \u002F 边界收紧 | [code-review-checklist.md](references\u002Fcode-review-checklist.md) → [boundary-smells.md](references\u002Fboundary-smells.md) |\n| MVC → DDD 渐进重构 | [refactoring-guide.md](references\u002Frefactoring-guide.md) |\n| 复杂规则建模 \u002F 流程编排 | [design-patterns.md](references\u002Fdesign-patterns.md)（~900 行，按目录跳转） |\n\n### Phase 2: 确保最小闭环\n\n在给出建议时，优先检查这 5 条基线是否满足，再考虑引入更多抽象：\n\n1. `domain` 纯净，依赖方向正确\n2. `trigger` 不直接依赖 `repository \u002F mapper \u002F 外部客户端`\n3. `repository` 接口不暴露 `refreshCache \u002F evictCache \u002F cacheXxx` 等技术语义\n4. ACL \u002F 外部适配器返回领域对象，而不是把外部 DTO 直接带进领域\n5. 关键不变量有领域单元测试，并按职责边界补齐各层测试\n\n### Phase 3: 按场景执行\n\n#### 场景 A: 新项目 \u002F 新模块\n\n1. 用 [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) 判断最小可行分层\n2. 用 [project-structure.md](references\u002Fproject-structure.md) 选择目录结构与 POM 多模块依赖\n3. 用 [domain-modeling.md](references\u002Fdomain-modeling.md) 设计实体 \u002F 值对象 \u002F 聚合 \u002F 仓储 \u002F Port\n4. 用 [code-templates.md](references\u002Fcode-templates.md) 按层拷贝代码骨架\n5. 命名拿不准时查 [naming-conventions.md](references\u002Fnaming-conventions.md)\n6. 用 [testing-strategy.md](references\u002Ftesting-strategy.md) 规划测试分层\n7. 只在规则明显膨胀时，再引入 [design-patterns.md](references\u002Fdesign-patterns.md) 中的模式\n\n#### 场景 B: 测试策略与 TDD 落地\n\n1. 先判断当前要验证的是**领域规则**、**用例编排**、**HTTP 契约**，还是**持久化\u002F外部集成**风险\n2. 领域规则优先写纯单测，不启动 Spring；关键不变量在 Entity \u002F VO \u002F DomainService 层锁住\n3. `application \u002F use case` 只测编排、事务边界、幂等与跨聚合协调；可 mock 仓储接口、Port，不要 mock Entity \u002F VO\n4. Controller 默认使用 `@WebMvcTest + MockMvc`；默认 mock 应用服务 \u002F use case\n5. Repository \u002F Adapter \u002F 复杂 Mapper 通过集成测试验证，必要时使用 Testcontainers\n6. 仅保留少量 `@SpringBootTest` 烟雾测试验证关键全链路 wiring\n\n#### 场景 C: 审查与边界收紧\n\n1. 用 [code-review-checklist.md](references\u002Fcode-review-checklist.md) 做结构化检查\n2. 用 [boundary-smells.md](references\u002Fboundary-smells.md) 对照常见反模式\n3. 检查测试边界：是否用 controller 测试兜底领域规则、是否大量 mock mapper、是否缺少集成测试\n4. 先修\"依赖方向、边界绕过、DTO 穿透、缓存语义泄漏、测试边界错位\"\n5. 修完后立刻补领域测试与关键集成测试，锁住行为\n\n#### 场景 D: MVC 到 DDD 重构\n\n1. 先识别限界上下文与用例边界\n2. 先封装 Repository \u002F Port，再重构模型\n3. 先做最小模块拆分，避免一次性把 `application \u002F api \u002F querys` 全预埋\n4. 优先把关键规则沉回模型或领域服务\n5. 每次边界收紧前后，优先补 `domain` 与 `application` 层的保护性测试\n\n### Phase 4: 判断是否继续演进\n\n只有当出现真实信号时，再建议引入：\n\n| 信号 | 引入 |\n|---|---|\n| 多入口共用同一用例编排、跨聚合编排膨胀 | `application` 层 |\n| 需要对外发布\u002F复用 RPC 契约 | `api` 模块 |\n| 出现独立读模型、CQRS、报表\u002F搜索等读侧复杂性 | `querys` 模块 |\n| 跨聚合一致性问题已真实出现 | 领域事件 \u002F MQ |\n\n## Common Mistakes\n\n- **为了\"像 DDD\"而盲目补层**：模块数量不是成熟度的代名词，先满足当前复杂度\n- **Domain 层混入技术细节**：不要在 `domain` 中放 Spring \u002F MyBatis \u002F Redis \u002F HTTP 客户端\n- **先上模式再有场景**：两个 `if-else` 不值得上责任链 \u002F 决策树\n- **用一种测试覆盖所有**：领域规则、编排、HTTP 契约和持久化风险应按责任边界分层测试\n- **`@SpringBootTest` 当默认**：Controller 默认使用切片测试，Repository \u002F Adapter 默认使用真实集成测试\n- **大量 mock mapper**：若 `application \u002F domain` 测试必须 mock mapper，优先回看职责划分是否混乱\n\n## References\n\n- [layering-decision-matrix.md](references\u002Flayering-decision-matrix.md) — 分层增减决策矩阵\n- [project-structure.md](references\u002Fproject-structure.md) — 渐进式项目结构与 Maven 多模块 POM\n- [domain-modeling.md](references\u002Fdomain-modeling.md) — 领域建模指南 + 速查模板\n- [code-templates.md](references\u002Fcode-templates.md) — 按层代码模板速查 + 端到端示例（~1100 行，用顶部对照表定位）\n- [naming-conventions.md](references\u002Fnaming-conventions.md) — 包\u002F类\u002F接口\u002F方法\u002F数据库命名速查\n- [design-patterns.md](references\u002Fdesign-patterns.md) — 领域层模式落地范式（~900 行，按目录跳转）\n- [testing-strategy.md](references\u002Ftesting-strategy.md) — DDD 测试分层与 Mock 边界\n- [code-review-checklist.md](references\u002Fcode-review-checklist.md) — DDD 代码审查清单\n- [boundary-smells.md](references\u002Fboundary-smells.md) — 常见边界异味与修复策略\n- [refactoring-guide.md](references\u002Frefactoring-guide.md) — MVC 到 DDD 渐进重构指南\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ddd-best-practices",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ddd-best-practices",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ddd-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002FSKILL.md",true,[71,77,81,85,89,93,97,101,105,109],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fboundary-smells.md","REFERENCE","参考文档",6282,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fboundary-smells.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fcode-review-checklist.md",4160,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fcode-review-checklist.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcode-templates.md",33784,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fcode-templates.md",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdesign-patterns.md",30891,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fdesign-patterns.md",{"path":90,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdomain-modeling.md",20352,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fdomain-modeling.md",{"path":94,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Flayering-decision-matrix.md",4255,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Flayering-decision-matrix.md",{"path":98,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fnaming-conventions.md",13589,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fnaming-conventions.md",{"path":102,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fproject-structure.md",21512,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Fproject-structure.md",{"path":106,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Frefactoring-guide.md",6161,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Frefactoring-guide.md",{"path":110,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Ftesting-strategy.md",7292,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Fddd-best-practices\u002Freferences\u002Ftesting-strategy.md",[114,124,132,140,148,156],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":123},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":123},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":123},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":123},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":123},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"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":118,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":123},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]