[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP1QGV0QQSJRM1RRTHAAHA":3,"skill-same:01M7AP1QGV0QQSJRM1RRTHAAHA":163},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":5,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AP1QGV0QQSJRM1RRTHAAHA","prd-writing",null,"Step-by-step workflow for writing Product Requirements Documents. Use when creating PRDs, documenting features, writing specifications, or planning new products. Triggers on \"write PRD\", \"create PRD\", \"document requirements\", \"feature spec\", or \"product requirements\".","davidanthonyn\u002Fclaude-skills","davidanthonyn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55152980?v=4","01M7AJ4MY8S5C2RJCGX6626J0G","01M7AJ7JE1K98GRPH9Z57Z0R0W",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prd-writing\ndescription: Step-by-step workflow for writing Product Requirements Documents. Use when creating PRDs, documenting features, writing specifications, or planning new products. Triggers on \"write PRD\", \"create PRD\", \"document requirements\", \"feature spec\", or \"product requirements\".\nlicense: MIT\nmetadata:\n  author: agent-skills\n  version: \"1.0.0\"\n---\n\n# PRD Writing\n\nStep-by-step workflow for writing clear, actionable Product Requirements Documents. Follow the 6-step process below, using the 25 rules across 7 categories as supporting knowledge.\n\n## Metadata\n\n- **Version:** 1.0.0\n- **Rule Count:** 25 rules across 7 categories\n- **License:** MIT\n\n## Workflow\n\nFollow these steps in order. Skip a step only if the user has already provided that information. Do NOT start drafting before completing discovery.\n\n### Step 1: Assess Project State\n\nDetermine what you're working with:\n\n- **Existing project** — code exists → explore the codebase first (models, routes, controllers, auth, patterns). See `disc-codebase-exploration`.\n- **Empty\u002Fgreenfield project** — no code yet → ask the user what they want to build first. Brainstorm together until the product idea and core features are clear, then ask about planned stack, architecture decisions, and constraints.\n\n### Step 2: Ask Clarifying Questions\n\nAsk 3-5 targeted questions to fill knowledge gaps. Use **lettered options** (A\u002FB\u002FC) when there are clear choices, and open-ended questions when you need free-text answers. Focus on:\n\n1. **Problem** — What problem are we solving? Why now?\n2. **Users** — Who are the target users?\n3. **Scope** — What should it NOT do?\n4. **Success** — How do we know it's done?\n5. **Constraints** — Timeline, budget, team size?\n\nMark unknowns as TBD, not assumptions. See `disc-clarifying-questions`.\n\n### Step 3: Draft the PRD\n\nUse the template from `struct-prd-template` and fill in all 12 sections:\n\n1. **Executive Summary** — 1 paragraph: problem, solution, impact\n2. **Problem Statement** — what, who, evidence, why now\n3. **Goals & Success Metrics** — 3-5 measurable KPIs\n4. **User Personas** — primary and secondary with roles\u002Fgoals\u002Fpain points\n5. **User Stories & Acceptance Criteria** — \"As a \u002F I want \u002F So that\" with checkboxes\n6. **Functional Requirements** — numbered FR-1, FR-2, etc.\n7. **Non-Functional Requirements** — performance, security, accessibility with specific numbers\n8. **Technical Specifications** — data model, auth, routes, integrations\n9. **Out of Scope** — what we're NOT building and why\n10. **Non-Goals** — what we're NOT optimizing for\n11. **Dependencies & Risks** — blockers with owners and mitigations\n12. **Open Questions** — unresolved items with owners and due dates\n\n**Key rules to follow while drafting:**\n- Start with the problem, not the solution (`disc-problem-first`)\n- Replace vague language with numbers (`metric-no-vague-language`)\n- Every requirement must be testable (`quality-acceptance-criteria`)\n- Use Given\u002FWhen\u002FThen for complex acceptance criteria\n\n### Step 4: Present for Review\n\nShow the draft to the user. Ask specifically:\n- Does the problem statement match your understanding?\n- Are user stories missing any workflows?\n- Are the scope boundaries correct?\n- Any open questions I should resolve?\n\n### Step 5: Revise Based on Feedback\n\nIncorporate feedback, resolve open questions, and update the PRD. Add a review history entry if the PRD will be shared with a team.\n\n### Step 6: Save the PRD\n\nSave to `docs\u002Fprd\u002F{feature-name}.md` using kebab-case naming. Include frontmatter:\n\n```markdown\n---\ntitle: Feature Name\nstatus: draft\nauthor: Author Name\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\n---\n```\n\n## Rules Reference\n\nThe 25 rules below provide detailed guidance for each step. Read them when you need deeper context.\n\n### 1. Discovery (CRITICAL)\n\n- `disc-problem-first` - Start with the problem, not the solution\n- `disc-clarifying-questions` - Ask clarifying questions before writing\n- `disc-codebase-exploration` - Explore the codebase before drafting\n- `disc-stakeholder-alignment` - Align with stakeholders on goals and constraints\n\n### 2. Structure (CRITICAL)\n\n- `struct-standard-sections` - Use standardized PRD sections\n- `struct-executive-summary` - Write a concise executive summary\n- `struct-prd-template` - Provide a ready-to-use PRD template\n- `struct-output-location` - Save PRDs to a consistent file location\n- `struct-single-source-of-truth` - PRD is the definitive reference for a feature\n\n### 3. Requirements (HIGH)\n\n- `req-user-personas` - Define target user personas\n- `req-user-stories` - Write user stories with acceptance criteria\n- `req-functional` - Define specific functional requirements\n- `req-non-functional` - Define non-functional requirements\n\n### 4. Scope (HIGH)\n\n- `scope-out-of-scope` - Explicitly define what is out of scope\n- `scope-non-goals` - List non-goals to protect timeline\n- `scope-dependencies` - Identify dependencies and blockers\n\n### 5. Metrics (HIGH)\n\n- `metric-measurable-success` - Define measurable success criteria\n- `metric-no-vague-language` - Replace vague terms with quantifiable benchmarks\n- `metric-kpis` - Define 3-5 key performance indicators\n\n### 6. Technical (MEDIUM)\n\n- `tech-data-model` - Document the data model and relationships\n- `tech-auth-model` - Define authentication and authorization\n- `tech-api-routes` - Document API and route structure\n- `tech-integration-points` - Identify third-party integrations\n\n### 7. Quality (MEDIUM)\n\n- `quality-acceptance-criteria` - Write testable acceptance criteria\n- `quality-iterative-review` - Iterate with feedback before finalizing\n\n## References\n\n- [Lenny's Newsletter - How to Write a Great PRD](https:\u002F\u002Fwww.lennysnewsletter.com\u002Fp\u002Fhow-to-write-a-great-prd)\n- [Silicon Valley Product Group - Product Discovery](https:\u002F\u002Fwww.svpg.com\u002Fproduct-discovery\u002F)\n- [Shape Up - Basecamp](https:\u002F\u002Fbasecamp.com\u002Fshapeup)\n- [Writing Great Specifications - Kamil Nicieja](https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fwriting-great-specifications)\n- [Atlassian - Product Requirements Document](https:\u002F\u002Fwww.atlassian.com\u002Fagile\u002Fproduct-management\u002Frequirements)\n\n## Full Compiled Document\n\nFor the complete guide with all rules expanded: `AGENTS.md`\n","# PRD Writing\n\nStep-by-step workflow for writing clear, actionable Product Requirements Documents. Follow the 6-step process below, using the 25 rules across 7 categories as supporting knowledge.\n\n## Metadata\n\n- **Version:** 1.0.0\n- **Rule Count:** 25 rules across 7 categories\n- **License:** MIT\n\n## Workflow\n\nFollow these steps in order. Skip a step only if the user has already provided that information. Do NOT start drafting before completing discovery.\n\n### Step 1: Assess Project State\n\nDetermine what you're working with:\n\n- **Existing project** — code exists → explore the codebase first (models, routes, controllers, auth, patterns). See `disc-codebase-exploration`.\n- **Empty\u002Fgreenfield project** — no code yet → ask the user what they want to build first. Brainstorm together until the product idea and core features are clear, then ask about planned stack, architecture decisions, and constraints.\n\n### Step 2: Ask Clarifying Questions\n\nAsk 3-5 targeted questions to fill knowledge gaps. Use **lettered options** (A\u002FB\u002FC) when there are clear choices, and open-ended questions when you need free-text answers. Focus on:\n\n1. **Problem** — What problem are we solving? Why now?\n2. **Users** — Who are the target users?\n3. **Scope** — What should it NOT do?\n4. **Success** — How do we know it's done?\n5. **Constraints** — Timeline, budget, team size?\n\nMark unknowns as TBD, not assumptions. See `disc-clarifying-questions`.\n\n### Step 3: Draft the PRD\n\nUse the template from `struct-prd-template` and fill in all 12 sections:\n\n1. **Executive Summary** — 1 paragraph: problem, solution, impact\n2. **Problem Statement** — what, who, evidence, why now\n3. **Goals & Success Metrics** — 3-5 measurable KPIs\n4. **User Personas** — primary and secondary with roles\u002Fgoals\u002Fpain points\n5. **User Stories & Acceptance Criteria** — \"As a \u002F I want \u002F So that\" with checkboxes\n6. **Functional Requirements** — numbered FR-1, FR-2, etc.\n7. **Non-Functional Requirements** — performance, security, accessibility with specific numbers\n8. **Technical Specifications** — data model, auth, routes, integrations\n9. **Out of Scope** — what we're NOT building and why\n10. **Non-Goals** — what we're NOT optimizing for\n11. **Dependencies & Risks** — blockers with owners and mitigations\n12. **Open Questions** — unresolved items with owners and due dates\n\n**Key rules to follow while drafting:**\n- Start with the problem, not the solution (`disc-problem-first`)\n- Replace vague language with numbers (`metric-no-vague-language`)\n- Every requirement must be testable (`quality-acceptance-criteria`)\n- Use Given\u002FWhen\u002FThen for complex acceptance criteria\n\n### Step 4: Present for Review\n\nShow the draft to the user. Ask specifically:\n- Does the problem statement match your understanding?\n- Are user stories missing any workflows?\n- Are the scope boundaries correct?\n- Any open questions I should resolve?\n\n### Step 5: Revise Based on Feedback\n\nIncorporate feedback, resolve open questions, and update the PRD. Add a review history entry if the PRD will be shared with a team.\n\n### Step 6: Save the PRD\n\nSave to `docs\u002Fprd\u002F{feature-name}.md` using kebab-case naming. Include frontmatter:\n\n```markdown\n---\ntitle: Feature Name\nstatus: draft\nauthor: Author Name\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\n---\n```\n\n## Rules Reference\n\nThe 25 rules below provide detailed guidance for each step. Read them when you need deeper context.\n\n### 1. Discovery (CRITICAL)\n\n- `disc-problem-first` - Start with the problem, not the solution\n- `disc-clarifying-questions` - Ask clarifying questions before writing\n- `disc-codebase-exploration` - Explore the codebase before drafting\n- `disc-stakeholder-alignment` - Align with stakeholders on goals and constraints\n\n### 2. Structure (CRITICAL)\n\n- `struct-standard-sections` - Use standardized PRD sections\n- `struct-executive-summary` - Write a concise executive summary\n- `struct-prd-template` - Provide a ready-to-use PRD template\n- `struct-output-location` - Save PRDs to a consistent file location\n- `struct-single-source-of-truth` - PRD is the definitive reference for a feature\n\n### 3. Requirements (HIGH)\n\n- `req-user-personas` - Define target user personas\n- `req-user-stories` - Write user stories with acceptance criteria\n- `req-functional` - Define specific functional requirements\n- `req-non-functional` - Define non-functional requirements\n\n### 4. Scope (HIGH)\n\n- `scope-out-of-scope` - Explicitly define what is out of scope\n- `scope-non-goals` - List non-goals to protect timeline\n- `scope-dependencies` - Identify dependencies and blockers\n\n### 5. Metrics (HIGH)\n\n- `metric-measurable-success` - Define measurable success criteria\n- `metric-no-vague-language` - Replace vague terms with quantifiable benchmarks\n- `metric-kpis` - Define 3-5 key performance indicators\n\n### 6. Technical (MEDIUM)\n\n- `tech-data-model` - Document the data model and relationships\n- `tech-auth-model` - Define authentication and authorization\n- `tech-api-routes` - Document API and route structure\n- `tech-integration-points` - Identify third-party integrations\n\n### 7. Quality (MEDIUM)\n\n- `quality-acceptance-criteria` - Write testable acceptance criteria\n- `quality-iterative-review` - Iterate with feedback before finalizing\n\n## References\n\n- [Lenny's Newsletter - How to Write a Great PRD](https:\u002F\u002Fwww.lennysnewsletter.com\u002Fp\u002Fhow-to-write-a-great-prd)\n- [Silicon Valley Product Group - Product Discovery](https:\u002F\u002Fwww.svpg.com\u002Fproduct-discovery\u002F)\n- [Shape Up - Basecamp](https:\u002F\u002Fbasecamp.com\u002Fshapeup)\n- [Writing Great Specifications - Kamil Nicieja](https:\u002F\u002Fwww.manning.com\u002Fbooks\u002Fwriting-great-specifications)\n- [Atlassian - Product Requirements Document](https:\u002F\u002Fwww.atlassian.com\u002Fagile\u002Fproduct-management\u002Frequirements)\n\n## Full Compiled Document\n\nFor the complete guide with all rules expanded: `AGENTS.md`\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25},"agent-skills","1.0.0","main","45d5ac830c3e238eeba6d0b4e6fd7cf6b56bf380","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn","2026-09-09 16:05:56",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add davidanthonyn\u002Fclaude-skills --skill prd-writing",{"tool":37,"command":38},"bunx","bunx skills add davidanthonyn\u002Fclaude-skills --skill prd-writing",{"tool":40,"command":41},"pnpm","pnpm dlx skills add davidanthonyn\u002Fclaude-skills --skill prd-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"AGENTS.md","REFERENCE","参考文档",69781,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002FAGENTS.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"README.md",1876,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002FREADME.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"rules\u002F_sections.md",2571,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002F_sections.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"rules\u002F_template.md",889,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002F_template.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"rules\u002Fdisc-clarifying-questions.md",3779,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fdisc-clarifying-questions.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"rules\u002Fdisc-codebase-exploration.md",3587,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fdisc-codebase-exploration.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"rules\u002Fdisc-problem-first.md",2735,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fdisc-problem-first.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"rules\u002Fdisc-stakeholder-alignment.md",2706,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fdisc-stakeholder-alignment.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"rules\u002Fmetric-kpis.md",2714,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fmetric-kpis.md",{"path":84,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":85,"sourceHtmlUrl":86},"rules\u002Fmetric-measurable-success.md",2980,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fmetric-measurable-success.md",{"path":88,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":89,"sourceHtmlUrl":90},"rules\u002Fmetric-no-vague-language.md",2605,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fmetric-no-vague-language.md",{"path":92,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":93,"sourceHtmlUrl":94},"rules\u002Fquality-acceptance-criteria.md",2984,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fquality-acceptance-criteria.md",{"path":96,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":97,"sourceHtmlUrl":98},"rules\u002Fquality-iterative-review.md",2712,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fquality-iterative-review.md",{"path":100,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":101,"sourceHtmlUrl":102},"rules\u002Freq-functional.md",2874,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Freq-functional.md",{"path":104,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":105,"sourceHtmlUrl":106},"rules\u002Freq-non-functional.md",2740,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Freq-non-functional.md",{"path":108,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":109,"sourceHtmlUrl":110},"rules\u002Freq-user-personas.md",2522,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Freq-user-personas.md",{"path":112,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":113,"sourceHtmlUrl":114},"rules\u002Freq-user-stories.md",3107,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Freq-user-stories.md",{"path":116,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":117,"sourceHtmlUrl":118},"rules\u002Fscope-dependencies.md",2787,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fscope-dependencies.md",{"path":120,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":121,"sourceHtmlUrl":122},"rules\u002Fscope-non-goals.md",2292,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fscope-non-goals.md",{"path":124,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":125,"sourceHtmlUrl":126},"rules\u002Fscope-out-of-scope.md",2315,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fscope-out-of-scope.md",{"path":128,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":129,"sourceHtmlUrl":130},"rules\u002Fstruct-executive-summary.md",2468,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fstruct-executive-summary.md",{"path":132,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":133,"sourceHtmlUrl":134},"rules\u002Fstruct-output-location.md",2366,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fstruct-output-location.md",{"path":136,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":137,"sourceHtmlUrl":138},"rules\u002Fstruct-prd-template.md",4260,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fstruct-prd-template.md",{"path":140,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":141,"sourceHtmlUrl":142},"rules\u002Fstruct-single-source-of-truth.md",2472,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fstruct-single-source-of-truth.md",{"path":144,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":145,"sourceHtmlUrl":146},"rules\u002Fstruct-standard-sections.md",2811,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Fstruct-standard-sections.md",{"path":148,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":149,"sourceHtmlUrl":150},"rules\u002Ftech-api-routes.md",2925,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Ftech-api-routes.md",{"path":152,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":153,"sourceHtmlUrl":154},"rules\u002Ftech-auth-model.md",2675,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Ftech-auth-model.md",{"path":156,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":157,"sourceHtmlUrl":158},"rules\u002Ftech-data-model.md",2806,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Ftech-data-model.md",{"path":160,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":161,"sourceHtmlUrl":162},"rules\u002Ftech-integration-points.md",2627,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fprd-writing\u002Frules\u002Ftech-integration-points.md",[164,171,179,186,193,202],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":18},"01M7AQPHJF528A4MD52YZEZV3R","zustand-state-management","Production-tested setup for Zustand state management in React applications with TypeScript.\nThis skill provides comprehensive patterns for building scalable, type-safe global state.\n\nUse when: setting up global state in React, migrating from Redux or Context API, implementing\nstate persistence with localStorage, configuring TypeScript with Zustand, using slices pattern\nfor modular stores, adding devtools middleware for debugging, handling Next.js SSR hydration,\nor encountering hydration errors, TypeScript inference issues, or persist middleware problems.\n\nPrevents 5 documented issues: Next.js hydration mismatches, TypeScript double parentheses\nsyntax errors, persist middleware export errors, infinite render loops, and slices pattern\ntype inference failures.\n\nKeywords: zustand, state management, React state, TypeScript state, persist middleware,\ndevtools, slices pattern, global state, React hooks, create store, useBoundStore,\nStateCreator, hydration error, text content mismatch, infinite render, localStorage,\nsessionStorage, immer middleware, shallow equality, selector pattern, zustand v5","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzustand-state-management\u002FSKILL.md",[],[],{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":18},"01M7AQP2XJRPNYEH323GJ81NN5","zetic-mlange","Help users integrate the ZETIC Melange (MLange) on-device AI SDK into Android (Kotlin\u002FJava) and iOS (Swift) mobile apps. Use this skill whenever the user mentions Zetic, MLange, Melange, ZeticMLangeModel, ZeticMLangeLLMModel, ZeticMLangeHFModel, on-device NPU inference for mobile, or deploying ML models to Android\u002FiOS with NPU acceleration. Also trigger when users ask about running LLMs on-device with GGUF quantization, mobile NPU model deployment, or converting PyTorch\u002FONNX models for mobile inference. Covers general model inference, LLM inference (streaming token generation), and HuggingFace model loading.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FSKILL.md",[],[],{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":18},"01M7AQNEJHD27NNF5PYQDSW8B9","youtube-downloader","Download videos, audio, playlists, and channels from YouTube and 1000+ websites using yt-dlp. Supports quality selection, format conversion, subtitle download, playlist filtering, metadata extraction, thumbnail download, and batch operations. Use when downloading YouTube videos in any quality (4K, 8K, HDR), extracting audio as MP3\u002FM4A\u002FFLAC, downloading entire playlists\u002Fchannels, getting subtitles in multiple languages, converting to specific formats, downloading live streams, archiving content, or batch processing multiple URLs. Optimized for reliability with automatic retries, rate limiting, and error handling.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":18},"01M7AQJQSD2H04EE2EPNAQ8A3M","wordpress-plugin-core","This skill provides comprehensive knowledge for WordPress plugin development, covering core patterns, security best practices, database interactions, hooks\u002Ffilters, Settings API, custom post types, REST API, and AJAX. This skill should be used when creating WordPress plugins, troubleshooting security issues, implementing custom post types\u002Ftaxonomies, building admin interfaces, or working with the WordPress database.\n\nUse when: Creating new WordPress plugins, implementing nonces\u002Fsanitization\u002Fescaping, working with $wpdb and prepared statements, building Settings API pages, registering custom post types or taxonomies, implementing REST API endpoints, handling AJAX requests, debugging plugin activation\u002Fdeactivation issues, preventing SQL injection\u002FXSS\u002FCSRF vulnerabilities.\n\nKeywords: wordpress plugin development, wordpress security, wordpress hooks, wordpress filters, wordpress database, wpdb prepare, sanitize_text_field, esc_html, wp_nonce, custom post type, register_post_type, settings api, rest api, admin-ajax, wordpress sql injection, wordpress xss, wordpress csrf, plugin header, activation hook, deactivation hook, wordpress coding standards, wordpress plugin architecture","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwordpress-plugin-core\u002FSKILL.md",[],[],{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":197,"licenseFileUrl":198,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":18},"01M7AQJ91T970QCFMN9R1EHZXV","webapp-testing","Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":18},"01M7AQJ5E89MS8C5K3GZTY4B48","web-performance-audit","Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fweb-performance-audit\u002FSKILL.md",[],[]]