[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG0AN2SXF8564GH471KRPV":3,"skill-same:01M6MG0AN2SXF8564GH471KRPV":74},{"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":34,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":73},"01M6MG0AN2SXF8564GH471KRPV","frontend\u002Fcomponent-development",null,"前端组件开发方法论，包括组件设计原则、状态管理、样式实现和性能优化","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\u002FechoVic\u002Fboss-skill\u002Fskill\u002Fskills\u002Ffrontend\u002Fcomponent-development\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43],"frontend","component","development","frontend component","component development","frontend component development","design","methodology","true","2026-11-10 10:12:30",false,"---\n\nname: frontend\u002Fcomponent-development\ndescription: 前端组件开发方法论，包括组件设计原则、状态管理、样式实现和性能优化\ntype: methodology\nagent: boss-frontend\nmetadata:\ninternal: true\n---\n\n# 前端组件开发方法论\n\n## 组件设计原则\n\n### 单一职责原则\n\n- 每个组件只负责一个功能模块\n- 复杂组件拆分为多个子组件\n- 容器组件（逻辑）与展示组件（UI）分离\n\n### 可复用性设计\n\n- 通过 Props\u002F属性实现组件配置化\n- 避免硬编码业务逻辑\n- 提供合理的默认值\n- 支持插槽\u002Fchildren 扩展\n\n### 组件命名规范\n\n- 使用 PascalCase 命名组件\n- 名称应清晰描述组件功能\n- 避免过于通用的名称（如 Item、Component）\n- 文件名与组件名保持一致\n\n## 状态管理策略\n\n### 状态分类\n\n| 状态类型   | 管理方式      | 适用场景                            |\n| ---------- | ------------- | ----------------------------------- |\n| 本地状态   | useState\u002Fref  | 组件内部状态（表单输入、展开\u002F收起） |\n| 共享状态   | Context\u002FStore | 跨组件共享（用户信息、主题）        |\n| 服务端状态 | Query库\u002FSWR   | API 数据缓存和同步                  |\n| URL 状态   | Router        | 页面参数、筛选条件                  |\n\n### 状态提升原则\n\n- 状态放在最近的公共父组件\n- 避免过度提升导致不必要的重渲染\n- 使用 Context 避免 Props 层层传递\n\n### 副作用管理\n\n- 使用框架的副作用 Hook（useEffect\u002FonMounted）\n- 清理订阅和定时器\n- 依赖数组准确声明\n- 避免在渲染函数中执行副作用\n\n## 样式实现规范\n\n### UI 规范优先级\n\n```\nui-design.json > ui-spec.md > 项目现有样式 > 框架默认值\n```\n\n### ui-design.json 集成\n\n当 `.boss\u002F\u003Cfeature>\u002Fui-design.json` 存在时：\n1. **读取 tokens**：映射为 CSS 变量或主题对象\n\n   ```typescript\n   \u002F\u002F 示例：从 tokens 生成 CSS 变量\n   const colors = uiDesign.tokens.colors;\n   \u002F\u002F --color-primary: #007AFF\n   ```\n\n2. **解析 pages 和 frames**：推导页面结构和布局\n   - 从 `pages[].frames[]` 提取页面组件层级\n   - 从 `frames[].layout` 获取布局约束（宽度、间距、对齐）\n\n3. **实现 prototype.links**：推导导航和交互\n   - 按钮点击跳转\n   - 表单提交流程\n   - 模态框打开\u002F关闭\n\n4. **复用 components**：提取可复用组件\n   - 从 `components[]` 识别通用组件（Button、Input、Card）\n   - 实现为独立组件文件\n\n### 样式编写原则\n\n- 使用项目约定的样式方案（CSS Modules\u002FTailwind\u002FCSS-in-JS）\n- 响应式设计：移动端优先或桌面端优先（按项目约定）\n- 使用设计系统的间距、颜色、字体变量\n- 避免魔法数字，使用语义化变量\n\n### 无障碍实现\n\n- 添加正确的 ARIA 属性（role、aria-label、aria-describedby）\n- 确保键盘导航可用（tabindex、focus 样式）\n- 表单元素关联 label\n- 图片添加 alt 文本\n\n## 性能优化技巧\n\n### 渲染优化\n\n- 使用 Memo\u002FshouldComponentUpdate 避免不必要的重渲染\n- 列表渲染使用稳定的 key\n- 虚拟滚动处理长列表\n- 避免在渲染函数中创建新对象\u002F函数\n\n### 代码分割\n\n- 路由级别的懒加载\n- 大型组件按需加载\n- 第三方库按需引入\n\n### 资源优化\n\n- 图片懒加载和响应式图片\n- 使用 WebP 等现代图片格式\n- SVG 图标内联或雪碧图\n\n## API 契约管理\n\n### 契约来源\n\n实现前端 API 调用前，必须阅读：\n1. **architecture.md §5（API 设计）**：获取端点列表、请求\u002F响应格式\n2. **后端共享类型**（如有）：复用类型定义\n\n### API 调用层设计\n\n```typescript\n\u002F\u002F services\u002Fapi\u002Fusers.ts\nexport const userApi = {\n  async getUser(id: string): Promise\u003CUser> {\n    const response = await fetch(`\u002Fapi\u002Fusers\u002F${id}`);\n    return response.json();\n  },\n\n  async createUser(data: CreateUserRequest): Promise\u003CUser> {\n    const response = await fetch('\u002Fapi\u002Fusers', {\n      method: 'POST',\n      body: JSON.stringify(data),\n    });\n    return response.json();\n  },\n};\n```\n\n### 错误处理\n\n- 统一错误处理：按 architecture.md 定义的错误格式\n- 用户友好的错误提示\n- 网络错误重试机制\n- 加载和错误状态展示\n\n### Mock 策略\n\n后端未就绪时，基于 architecture.md §5 创建 Mock：\n```typescript\n\u002F\u002F services\u002Fapi\u002Fusers.mock.ts\nexport const mockUserApi = {\n  async getUser(id: string): Promise\u003CUser> {\n    return { id, name: 'Mock User', email: 'mock@example.com' };\n  },\n};\n```\n\n## 组件测试策略（TDD）\n\n> **必须遵循 TDD**：先写失败测试（RED）→ 最小实现（GREEN）→ 重构（REFACTOR）。详见 `shared\u002Ftdd` skill。\n\n### 测试金字塔\n\n| 测试类型 | 占比 | 工具示例               |\n| -------- | ---- | ---------------------- |\n| 单元测试 | 70%  | Jest + Testing Library |\n| 集成测试 | 20%  | Testing Library        |\n| E2E 测试 | 10%  | Playwright\u002FCypress     |\n\n### 单元测试覆盖\n\n- 组件渲染：关键元素是否存在\n- Props 变化：不同 Props 下的渲染结果\n- 用户交互：点击、输入、表单提交\n- Hooks 逻辑：自定义 Hook 的状态变化\n\n### 集成测试覆盖\n\n- 组件间交互：父子组件通信\n- 状态管理：全局状态变化对组件的影响\n- 路由导航：页面跳转和参数传递\n\n### E2E 测试覆盖（必须）\n\n- 创建流程：填写表单 → 提交 → 验证结果\n- 编辑流程：打开编辑 → 修改 → 保存 → 验证\n- 删除流程：点击删除 → 确认 → 验证消失\n- 列表展示：加载列表 → 筛选 → 分页\n- 核心业务流程：完整用户路径\n\n## 实现检查清单\n\n实现组件前：\n- [ ] 阅读 ui-design.json（如有）和 ui-spec.md\n- [ ] 阅读 architecture.md §5 API 设计\n- [ ] 探索项目现有组件模式和样式方案\n- [ ] 确认状态管理方案（本地\u002F共享\u002F服务端）\n\n实现组件后：\n- [ ] 组件符合单一职责原则\n- [ ] 添加必要的 Props 类型定义\n- [ ] 实现响应式布局\n- [ ] 添加无障碍属性\n- [ ] TDD：每个组件先有失败测试，已验证 RED\n- [ ] 编写单元测试（70%）\n- [ ] 编写集成测试（20%）\n- [ ] 编写 E2E 测试（10%，必须）\n- [ ] 测试覆盖率达标\n- [ ] 代码通过 Lint 检查\n","# 前端组件开发方法论\n\n## 组件设计原则\n\n### 单一职责原则\n\n- 每个组件只负责一个功能模块\n- 复杂组件拆分为多个子组件\n- 容器组件（逻辑）与展示组件（UI）分离\n\n### 可复用性设计\n\n- 通过 Props\u002F属性实现组件配置化\n- 避免硬编码业务逻辑\n- 提供合理的默认值\n- 支持插槽\u002Fchildren 扩展\n\n### 组件命名规范\n\n- 使用 PascalCase 命名组件\n- 名称应清晰描述组件功能\n- 避免过于通用的名称（如 Item、Component）\n- 文件名与组件名保持一致\n\n## 状态管理策略\n\n### 状态分类\n\n| 状态类型   | 管理方式      | 适用场景                            |\n| ---------- | ------------- | ----------------------------------- |\n| 本地状态   | useState\u002Fref  | 组件内部状态（表单输入、展开\u002F收起） |\n| 共享状态   | Context\u002FStore | 跨组件共享（用户信息、主题）        |\n| 服务端状态 | Query库\u002FSWR   | API 数据缓存和同步                  |\n| URL 状态   | Router        | 页面参数、筛选条件                  |\n\n### 状态提升原则\n\n- 状态放在最近的公共父组件\n- 避免过度提升导致不必要的重渲染\n- 使用 Context 避免 Props 层层传递\n\n### 副作用管理\n\n- 使用框架的副作用 Hook（useEffect\u002FonMounted）\n- 清理订阅和定时器\n- 依赖数组准确声明\n- 避免在渲染函数中执行副作用\n\n## 样式实现规范\n\n### UI 规范优先级\n\n```\nui-design.json > ui-spec.md > 项目现有样式 > 框架默认值\n```\n\n### ui-design.json 集成\n\n当 `.boss\u002F\u003Cfeature>\u002Fui-design.json` 存在时：\n1. **读取 tokens**：映射为 CSS 变量或主题对象\n\n   ```typescript\n   \u002F\u002F 示例：从 tokens 生成 CSS 变量\n   const colors = uiDesign.tokens.colors;\n   \u002F\u002F --color-primary: #007AFF\n   ```\n\n2. **解析 pages 和 frames**：推导页面结构和布局\n   - 从 `pages[].frames[]` 提取页面组件层级\n   - 从 `frames[].layout` 获取布局约束（宽度、间距、对齐）\n\n3. **实现 prototype.links**：推导导航和交互\n   - 按钮点击跳转\n   - 表单提交流程\n   - 模态框打开\u002F关闭\n\n4. **复用 components**：提取可复用组件\n   - 从 `components[]` 识别通用组件（Button、Input、Card）\n   - 实现为独立组件文件\n\n### 样式编写原则\n\n- 使用项目约定的样式方案（CSS Modules\u002FTailwind\u002FCSS-in-JS）\n- 响应式设计：移动端优先或桌面端优先（按项目约定）\n- 使用设计系统的间距、颜色、字体变量\n- 避免魔法数字，使用语义化变量\n\n### 无障碍实现\n\n- 添加正确的 ARIA 属性（role、aria-label、aria-describedby）\n- 确保键盘导航可用（tabindex、focus 样式）\n- 表单元素关联 label\n- 图片添加 alt 文本\n\n## 性能优化技巧\n\n### 渲染优化\n\n- 使用 Memo\u002FshouldComponentUpdate 避免不必要的重渲染\n- 列表渲染使用稳定的 key\n- 虚拟滚动处理长列表\n- 避免在渲染函数中创建新对象\u002F函数\n\n### 代码分割\n\n- 路由级别的懒加载\n- 大型组件按需加载\n- 第三方库按需引入\n\n### 资源优化\n\n- 图片懒加载和响应式图片\n- 使用 WebP 等现代图片格式\n- SVG 图标内联或雪碧图\n\n## API 契约管理\n\n### 契约来源\n\n实现前端 API 调用前，必须阅读：\n1. **architecture.md §5（API 设计）**：获取端点列表、请求\u002F响应格式\n2. **后端共享类型**（如有）：复用类型定义\n\n### API 调用层设计\n\n```typescript\n\u002F\u002F services\u002Fapi\u002Fusers.ts\nexport const userApi = {\n  async getUser(id: string): Promise\u003CUser> {\n    const response = await fetch(`\u002Fapi\u002Fusers\u002F${id}`);\n    return response.json();\n  },\n\n  async createUser(data: CreateUserRequest): Promise\u003CUser> {\n    const response = await fetch('\u002Fapi\u002Fusers', {\n      method: 'POST',\n      body: JSON.stringify(data),\n    });\n    return response.json();\n  },\n};\n```\n\n### 错误处理\n\n- 统一错误处理：按 architecture.md 定义的错误格式\n- 用户友好的错误提示\n- 网络错误重试机制\n- 加载和错误状态展示\n\n### Mock 策略\n\n后端未就绪时，基于 architecture.md §5 创建 Mock：\n```typescript\n\u002F\u002F services\u002Fapi\u002Fusers.mock.ts\nexport const mockUserApi = {\n  async getUser(id: string): Promise\u003CUser> {\n    return { id, name: 'Mock User', email: 'mock@example.com' };\n  },\n};\n```\n\n## 组件测试策略（TDD）\n\n> **必须遵循 TDD**：先写失败测试（RED）→ 最小实现（GREEN）→ 重构（REFACTOR）。详见 `shared\u002Ftdd` skill。\n\n### 测试金字塔\n\n| 测试类型 | 占比 | 工具示例               |\n| -------- | ---- | ---------------------- |\n| 单元测试 | 70%  | Jest + Testing Library |\n| 集成测试 | 20%  | Testing Library        |\n| E2E 测试 | 10%  | Playwright\u002FCypress     |\n\n### 单元测试覆盖\n\n- 组件渲染：关键元素是否存在\n- Props 变化：不同 Props 下的渲染结果\n- 用户交互：点击、输入、表单提交\n- Hooks 逻辑：自定义 Hook 的状态变化\n\n### 集成测试覆盖\n\n- 组件间交互：父子组件通信\n- 状态管理：全局状态变化对组件的影响\n- 路由导航：页面跳转和参数传递\n\n### E2E 测试覆盖（必须）\n\n- 创建流程：填写表单 → 提交 → 验证结果\n- 编辑流程：打开编辑 → 修改 → 保存 → 验证\n- 删除流程：点击删除 → 确认 → 验证消失\n- 列表展示：加载列表 → 筛选 → 分页\n- 核心业务流程：完整用户路径\n\n## 实现检查清单\n\n实现组件前：\n- [ ] 阅读 ui-design.json（如有）和 ui-spec.md\n- [ ] 阅读 architecture.md §5 API 设计\n- [ ] 探索项目现有组件模式和样式方案\n- [ ] 确认状态管理方案（本地\u002F共享\u002F服务端）\n\n实现组件后：\n- [ ] 组件符合单一职责原则\n- [ ] 添加必要的 Props 类型定义\n- [ ] 实现响应式布局\n- [ ] 添加无障碍属性\n- [ ] TDD：每个组件先有失败测试，已验证 RED\n- [ ] 编写单元测试（70%）\n- [ ] 编写集成测试（20%）\n- [ ] 编写 E2E 测试（10%，必须）\n- [ ] 测试覆盖率达标\n- [ ] 代码通过 Lint 检查\n",{"name":5,"type":42,"agent":49,"internal":50,"metadata":6,"description":7},"boss-frontend",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FechoVic\u002Fboss-skill\u002Fskill\u002Fskills\u002Ffrontend\u002Fcomponent-development",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":62,"prompt":72,"zipAvailable":50},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill frontend\u002Fcomponent-development",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill frontend\u002Fcomponent-development",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill frontend\u002Fcomponent-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FechoVic\u002Fboss-skill\u002Fskill\u002Fskills\u002Ffrontend\u002Fcomponent-development\u002FSKILL.md",[],[75,85,93,101,109,117],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"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",[],[]]