[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AKSFECF023Y09S63M71MW":3,"skill-same:01M71AKSFECF023Y09S63M71MW":70},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71AKSFECF023Y09S63M71MW","write-a-prd",null,"Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.","eiei114\u002Fclaude-code-template","eiei114","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60887155?v=4","01M71AG644Y7ZYKMN5WQQY0NGA","01M71AG64WKT3DJGHWWJJH84HQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-prd\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"prd","write a prd","write","exploration","new","when","user interview","codebase exploration","submit","as","module","feature","requirements","design","document","use","new feature","interview","plan","create","2026-11-10 10:12:30",false,"---\nname: write-a-prd\ndescription: Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.\n---\n\nThis skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n\n3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.\n\n4. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.\n\nA deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.\n\nCheck with the user that these modules match their expectations. Check with the user which modules they want tests written for.\n\n5. Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be submitted as a GitHub issue.\n\n\u003Cprd-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this PRD.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fprd-template>\n","This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.\n\n1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.\n\n2. Explore the repo to verify their assertions and understand the current state of the codebase.\n\n3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.\n\n4. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.\n\nA deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.\n\nCheck with the user that these modules match their expectations. Check with the user which modules they want tests written for.\n\n5. Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be submitted as a GitHub issue.\n\n\u003Cprd-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this PRD.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fprd-template>\n",{"name":5,"description":7},"main","7959c7e2d5ebcd9c684c4372eaa278dac53a1805","skills\u002Fwrite-a-prd","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template","https:\u002F\u002Fgithub.com\u002Feiei114","https:\u002F\u002Fspot-camelotia-ca8.notion.site\u002FPortfolio-66f9a6d667d84785afe1cecfea0fd2ab","Roblox & UEFN Engineer","2026-04-19 15:32:22",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add eiei114\u002Fclaude-code-template --skill write-a-prd",{"tool":62,"command":63},"bunx","bunx skills add eiei114\u002Fclaude-code-template --skill write-a-prd",{"tool":65,"command":66},"pnpm","pnpm dlx skills add eiei114\u002Fclaude-code-template --skill write-a-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-prd\u002FSKILL.md",true,[],[71,95,113,142,166,185],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":88,"publishedAt":43},"01M71AKWNFHFZ3R213KZZ02NV3","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[77,82,85],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[89,90,91,38,92,93,28,27,94],"writing","writing skills","deployment","editing","work","Existing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":103,"publishedAt":43},"01M71AKV2MQCJ0MYHT0JQ3N7T8","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[101,102],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},[89,104,105,106,38,28,107,35,108,109,110,111,112],"plans","writing plans","for","you","code","task","multi","spec","multi-step task",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":117,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":125,"publishedAt":43},"01M71AKQNV0SWR65KYTXV5PNTZ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[121,122],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":123,"categoryName":124,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",[126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,106,141],"webapp testing","testing","webapp","ui","behavior","web","playwright","with","browser","logs","toolkit","debugging","frontend","local","applications","screenshots",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":117,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":43},"01M71AKMVPPNG5S07QXZACP049","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\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[149],{"categoryNo":123,"categoryName":124,"taxonomyType":80,"taxonomyTypeDesc":81},[151,131,152,153,154,138,155,156,110,157,158,159,38,160,161,162,163,106,164,165],"web artifacts builder","artifacts","artifacts builder","builder","routing","state","react","components","file","single","state management","ui components","Tailwind","css","single-file",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":43},"01M71AKHAW8VXPPM2PM22H2P4Q","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[173,174,175,176,28,177,38,178,179,180,181,182,183,184,93],"verification before completion","verification","running","output","assertions","claim","prs","complete","evidence","claims","commands","about",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":43},"01M71AKFKJXEPCENYEWHB4FP9Y","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[192,193,28,38,194,195,196,197,198,199],"superpowers","using superpowers","how to","tool","questions","find","how","conversation"]