[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M745FFXG63F2SG00QCC2QRFP":3,"skill-same:01M745FFXG63F2SG00QCC2QRFP":62},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M745FFXG63F2SG00QCC2QRFP","prd",null,"Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.","TorchiaHub\u002FSkills","TorchiaHub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F125223386?v=4","01M71Q3SNKHMKJYN4HGMSQ2CEY","Mattia Torchia","01M71Q3SP6T1Z9NBADBCFP7GM5",0,"MIT","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: prd\ndescription: 'Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.'\nlicense: MIT\n---\n\n# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n\n## Vault Navigation\n\n- Skill summary: [[prd]]\n- Tools: [[tools]]\n- Examples: [[examples]]\n- Tests: [[tests]]\n","# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n\n## Vault Navigation\n\n- Skill summary: [[prd]]\n- Tools: [[tools]]\n- Examples: [[examples]]\n- Tests: [[tests]]\n",{"name":5,"license":15,"description":7},"master","e3489bc4e504668e9a2ff8fb73dc086da71328ab","10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills","https:\u002F\u002Fgithub.com\u002FTorchiaHub","2026-06-21 20:40:46",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add TorchiaHub\u002FSkills --skill prd",{"tool":36,"command":37},"bunx","bunx skills add TorchiaHub\u002FSkills --skill prd",{"tool":39,"command":40},"pnpm","pnpm dlx skills add TorchiaHub\u002FSkills --skill prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"examples.md","REFERENCE","参考文档",279,"https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002Fexamples.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"prd.md",990,"https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002Fprd.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"tests.md",405,"https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002Ftests.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"tools.md",391,"https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FEngineering\u002FPlanning\u002FProduct\u002Fprd\u002Ftools.md",[63,72,80,88,96,104],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M746D7EEPDC3H0Z80J8MZ0BC","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FFrontend\u002FGeneral\u002Ffrontend-design\u002Fsource\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FFrontend\u002FGeneral\u002Ffrontend-design\u002Fsource\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M746D21K5RYYE04HJ9R2VTPV","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FFrontend\u002FArtifacts\u002Fweb-artifacts-builder\u002Fsource\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FFrontend\u002FArtifacts\u002Fweb-artifacts-builder\u002Fsource\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M746CEHQ49XY53K8FAKFPWEW","screenshot","Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FVisual\u002Fscreenshot\u002Fsource\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FVisual\u002Fscreenshot\u002Fsource\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M746BS1AN6NSKD0CN4T7FC99","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FVisual\u002Fimagegen\u002Fsource\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FVisual\u002Fimagegen\u002Fsource\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M746B14M6QYGQ1GKZ9KYESF1","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FTheming\u002Ftheme-factory\u002Fsource\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FTheming\u002Ftheme-factory\u002Fsource\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M746ACZ46BBSRNY100Z7X18J","shadcn","Shadcn\u002Fui-inspired design with minimal, clean components, monochrome palette, and utility-first patterns.","https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F10-Skills\u002FWeb-Product\u002FDesign-UX\u002FStyles\u002Fshadcn\u002Fsource\u002FSKILL.md",[],[]]