[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7303DBCF7328B3GMPAS0CH7":3,"skill-same:01M7303DBCF7328B3GMPAS0CH7":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7303DBCF7328B3GMPAS0CH7","product-capability",null,"将PRD意图、路线图需求或产品讨论转化为可实施的方案计划，在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道，而不是模糊的规划文本时使用。","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fproduct-capability\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: product-capability\ndescription: 将PRD意图、路线图需求或产品讨论转化为可实施的方案计划，在开始多服务工作之前暴露约束、不变性、接口和未解决的决策。当用户需要ECC原生的PRD到SRS通道，而不是模糊的规划文本时使用。\norigin: ECC\n---\n\n# 产品能力\n\n该技能将产品意图转化为明确的工程约束。\n\n当问题不在于\"我们应该构建什么？\"，而在于\"在开始实现之前，必须明确哪些条件？\"时使用。\n\n## 使用时机\n\n* 存在PRD、路线图项、讨论或创始人笔记，但实现约束仍然隐式未明\n* 某个功能跨越多个服务、仓库或团队，在编码前需要一份能力契约\n* 产品意图明确，但架构、数据、生命周期或策略影响仍然模糊\n* 高级工程师在评审中反复重申相同的隐藏假设\n* 你需要一份可跨工具链和会话复用的持久化工件\n\n## 规范工件\n\n如果仓库中存在持久化的产品上下文文件，例如 `PRODUCT.md`、`docs\u002Fproduct\u002F` 或程序规范目录，请在此处更新。\n\n如果尚不存在能力清单，请使用以下模板创建：\n\n* `docs\u002Fexamples\u002Fproduct-capability-template.md`\n\n目标不是创建另一个规划栈，而是使隐藏的能力约束变得持久且可复用。\n\n## 不可妥协的规则\n\n* 不要编造产品事实。明确标记未解决的问题。\n* 将用户可见的承诺与实现细节分开。\n* 明确指出哪些是固定策略、哪些是架构偏好、哪些仍待定。\n* 如果请求与现有仓库约束冲突，请明确说明，而非粉饰太平。\n* 优先使用一份可复用的能力工件，而非零散的临时笔记。\n\n## 输入\n\n仅读取必要内容：\n\n1. 产品意图\n   * issue、讨论、PRD、路线图笔记、创始人消息\n2. 当前架构\n   * 相关仓库文档、契约、模式、路由、现有工作流\n3. 现有能力上下文\n   * `PRODUCT.md`、设计文档、RFC、迁移笔记、运营模式文档\n4. 交付约束\n   * 认证、计费、合规、发布、向后兼容、性能、评审策略\n\n## 核心工作流\n\n### 1. 重述能力\n\n将需求压缩为一个精确的陈述：\n\n* 用户或操作者是谁\n* 此功能上线后存在什么新能力\n* 因此带来了什么结果变化\n\n如果此陈述薄弱，实现将会偏离方向。\n\n### 2. 解析能力约束\n\n提取实现前必须满足的约束：\n\n* 业务规则\n* 范围边界\n* 不变性条件\n* 信任边界\n* 数据所有权\n* 生命周期转换\n* 发布\u002F迁移要求\n* 故障与恢复预期\n\n这些往往是仅存在于高级工程师记忆中的内容。\n\n### 3. 定义面向实现的契约\n\n制定一份SRS风格的能力计划，包含：\n\n* 能力摘要\n* 明确的非目标\n* 角色与界面\n* 所需状态与转换\n* 接口\u002F输入\u002F输出\n* 数据模型影响\n* 安全\u002F计费\u002F策略约束\n* 可观测性与运维要求\n* 阻碍实现的未解决问题\n\n### 4. 转化为执行\n\n以精确的交接点结束：\n\n* 可直接实现\n* 需先进行架构评审\n* 需先明确产品细节\n\n如有帮助，可指向下一个ECC原生通道：\n\n* `project-flow-ops`\n* `workspace-surface-audit`\n* `api-connector-builder`\n* `dashboard-builder`\n* `tdd-workflow`\n* `verification-loop`\n\n## 输出格式\n\n按以下顺序返回结果：\n\n```text\n能力\n- 一段重新陈述\n\n约束条件\n- 固定规则、不变项和边界\n\n实现契约\n- 参与者\n- 界面\n- 状态与转换\n- 接口\u002F数据影响\n\n非目标\n- 该通道明确不负责的内容\n\n待定问题\n- 仍需解决的阻碍或产品决策\n\n交接\n- 下一步应执行的操作及应由哪个ECC通道负责\n```\n\n## 良好成果\n\n* 产品意图已足够具体，无需在PR评审中重新发现隐藏约束即可实现。\n* 工程评审拥有持久化工件，而非依赖记忆或Slack上下文。\n* 生成的计划可在Claude Code、Codex、Cursor、OpenCode和ECC 2.0规划界面中复用。\n","# 产品能力\n\n该技能将产品意图转化为明确的工程约束。\n\n当问题不在于\"我们应该构建什么？\"，而在于\"在开始实现之前，必须明确哪些条件？\"时使用。\n\n## 使用时机\n\n* 存在PRD、路线图项、讨论或创始人笔记，但实现约束仍然隐式未明\n* 某个功能跨越多个服务、仓库或团队，在编码前需要一份能力契约\n* 产品意图明确，但架构、数据、生命周期或策略影响仍然模糊\n* 高级工程师在评审中反复重申相同的隐藏假设\n* 你需要一份可跨工具链和会话复用的持久化工件\n\n## 规范工件\n\n如果仓库中存在持久化的产品上下文文件，例如 `PRODUCT.md`、`docs\u002Fproduct\u002F` 或程序规范目录，请在此处更新。\n\n如果尚不存在能力清单，请使用以下模板创建：\n\n* `docs\u002Fexamples\u002Fproduct-capability-template.md`\n\n目标不是创建另一个规划栈，而是使隐藏的能力约束变得持久且可复用。\n\n## 不可妥协的规则\n\n* 不要编造产品事实。明确标记未解决的问题。\n* 将用户可见的承诺与实现细节分开。\n* 明确指出哪些是固定策略、哪些是架构偏好、哪些仍待定。\n* 如果请求与现有仓库约束冲突，请明确说明，而非粉饰太平。\n* 优先使用一份可复用的能力工件，而非零散的临时笔记。\n\n## 输入\n\n仅读取必要内容：\n\n1. 产品意图\n   * issue、讨论、PRD、路线图笔记、创始人消息\n2. 当前架构\n   * 相关仓库文档、契约、模式、路由、现有工作流\n3. 现有能力上下文\n   * `PRODUCT.md`、设计文档、RFC、迁移笔记、运营模式文档\n4. 交付约束\n   * 认证、计费、合规、发布、向后兼容、性能、评审策略\n\n## 核心工作流\n\n### 1. 重述能力\n\n将需求压缩为一个精确的陈述：\n\n* 用户或操作者是谁\n* 此功能上线后存在什么新能力\n* 因此带来了什么结果变化\n\n如果此陈述薄弱，实现将会偏离方向。\n\n### 2. 解析能力约束\n\n提取实现前必须满足的约束：\n\n* 业务规则\n* 范围边界\n* 不变性条件\n* 信任边界\n* 数据所有权\n* 生命周期转换\n* 发布\u002F迁移要求\n* 故障与恢复预期\n\n这些往往是仅存在于高级工程师记忆中的内容。\n\n### 3. 定义面向实现的契约\n\n制定一份SRS风格的能力计划，包含：\n\n* 能力摘要\n* 明确的非目标\n* 角色与界面\n* 所需状态与转换\n* 接口\u002F输入\u002F输出\n* 数据模型影响\n* 安全\u002F计费\u002F策略约束\n* 可观测性与运维要求\n* 阻碍实现的未解决问题\n\n### 4. 转化为执行\n\n以精确的交接点结束：\n\n* 可直接实现\n* 需先进行架构评审\n* 需先明确产品细节\n\n如有帮助，可指向下一个ECC原生通道：\n\n* `project-flow-ops`\n* `workspace-surface-audit`\n* `api-connector-builder`\n* `dashboard-builder`\n* `tdd-workflow`\n* `verification-loop`\n\n## 输出格式\n\n按以下顺序返回结果：\n\n```text\n能力\n- 一段重新陈述\n\n约束条件\n- 固定规则、不变项和边界\n\n实现契约\n- 参与者\n- 界面\n- 状态与转换\n- 接口\u002F数据影响\n\n非目标\n- 该通道明确不负责的内容\n\n待定问题\n- 仍需解决的阻碍或产品决策\n\n交接\n- 下一步应执行的操作及应由哪个ECC通道负责\n```\n\n## 良好成果\n\n* 产品意图已足够具体，无需在PR评审中重新发现隐藏约束即可实现。\n* 工程评审拥有持久化工件，而非依赖记忆或Slack上下文。\n* 生成的计划可在Claude Code、Codex、Cursor、OpenCode和ECC 2.0规划界面中复用。\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fproduct-capability",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill product-capability",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill product-capability",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill product-capability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fproduct-capability\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]