[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BV53KBA6B52N0HT8Q0H5P2":3,"skill-same:01M6BV53KBA6B52N0HT8Q0H5P2":68},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6BV53KBA6B52N0HT8Q0H5P2","create-tasks",null,"Generate a task list from requirements. Use when the user wants to break down a feature into implementation steps or create a development plan.","bnferguson\u002Fdotfiles","bnferguson","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47749?v=4","01M6BV4H2TJKK8P14W86V1ZCPP","Brandon Ferguson","01M6BV4H7GJWTZJ1BVHQ1TX11Y",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-tasks\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"create","create tasks","tasks","implementation","when","task list","down","break","break down","feature","requirements","task","use","user","list","plan","generate","development","2026-11-10 10:12:30",false,"---\nname: create-tasks\ndescription: \"Generate a task list from requirements. Use when the user wants to break down a feature into implementation steps or create a development plan.\"\n---\n\nRule: Generating a Task List from User Requirements\n\n## Goal\n\nTo guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on user requirements, feature requests, or existing documentation. The task list should guide a developer through implementation.\n\n## Output\n\n- **Format:** Markdown (`.md`)\n- **Location:** `\u002Ftasks\u002F`\n- **Filename:** `tasks-[feature-name].md` (e.g., `tasks-user-profile-editing.md`)\n\n## Process\n\n1.  **Receive Requirements:** The user provides a feature request, task description, or points to existing documentation\n2.  **Analyze Requirements:** The AI analyzes the functional requirements, user needs, and implementation scope from the provided information\n3.  **Phase 1: Generate Parent Tasks:** Based on the requirements analysis, create the file and generate the main, high-level tasks required to implement the feature. **IMPORTANT: Always include task 0.0 \"Create feature branch\" as the first task, unless the user specifically requests not to create a branch.** Use your judgement on how many additional high-level tasks to use. It's likely to be about 5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: \"I have generated the high-level tasks based on your requirements. Ready to generate the sub-tasks? Respond with 'Go' to proceed.\"\n4.  **Wait for Confirmation:** Pause and wait for the user to respond with \"Go\".\n5.  **Phase 2: Generate Sub-Tasks:** Once the user confirms, break down each parent task into smaller, actionable sub-tasks necessary to complete the parent task. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the requirements.\n6.  **Identify Relevant Files:** Based on the tasks and requirements, identify potential files that will need to be created or modified. List these under the `Relevant Files` section, including corresponding test files if applicable.\n7.  **Generate Final Output:** Combine the parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.\n8.  **Save Task List:** Save the generated document in the `\u002Ftasks\u002F` directory with the filename `tasks-[feature-name].md`, where `[feature-name]` describes the main feature or task being implemented (e.g., if the request was about user profile editing, the output is `tasks-user-profile-editing.md`).\n\n## Output Format\n\nThe generated task list _must_ follow this structure:\n\n```markdown\n## Relevant Files\n\n- `path\u002Fto\u002Fpotential\u002Ffile1.ts` - Brief description of why this file is relevant (e.g., Contains the main component for this feature).\n- `path\u002Fto\u002Ffile1.test.ts` - Unit tests for `file1.ts`.\n- `path\u002Fto\u002Fanother\u002Ffile.tsx` - Brief description (e.g., API route handler for data submission).\n- `path\u002Fto\u002Fanother\u002Ffile.test.tsx` - Unit tests for `another\u002Ffile.tsx`.\n- `lib\u002Futils\u002Fhelpers.ts` - Brief description (e.g., Utility functions needed for calculations).\n- `lib\u002Futils\u002Fhelpers.test.ts` - Unit tests for `helpers.ts`.\n\n### Notes\n\n- Unit tests should typically be placed alongside the code files they are testing (e.g., `MyComponent.tsx` and `MyComponent.test.tsx` in the same directory).\n- Use `npx jest [optional\u002Fpath\u002Fto\u002Ftest\u002Ffile]` to run tests. Running without a path executes all tests found by the Jest configuration.\n\n## Instructions for Completing Tasks\n\n**IMPORTANT:** As you complete each task, you must check it off in this markdown file by changing `- [ ]` to `- [x]`. This helps track progress and ensures you don't skip any steps.\n\nExample:\n- `- [ ] 1.1 Read file` → `- [x] 1.1 Read file` (after completing)\n\nUpdate the file after completing each sub-task, not just after completing an entire parent task.\n\n## Tasks\n\n- [ ] 0.0 Create feature branch\n  - [ ] 0.1 Create and checkout a new branch for this feature (e.g., `git checkout -b feature\u002F[feature-name]`)\n- [ ] 1.0 Parent Task Title\n  - [ ] 1.1 [Sub-task description 1.1]\n  - [ ] 1.2 [Sub-task description 1.2]\n- [ ] 2.0 Parent Task Title\n  - [ ] 2.1 [Sub-task description 2.1]\n- [ ] 3.0 Parent Task Title (may not require sub-tasks if purely structural or configuration)\n```\n\n## Interaction Model\n\nThe process explicitly requires a pause after generating parent tasks to get user confirmation (\"Go\") before proceeding to generate the detailed sub-tasks. This ensures the high-level plan aligns with user expectations before diving into details.\n\n## Target Audience\n\nAssume the primary reader of the task list is a **junior developer** who will implement the feature.\n","Rule: Generating a Task List from User Requirements\n\n## Goal\n\nTo guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on user requirements, feature requests, or existing documentation. The task list should guide a developer through implementation.\n\n## Output\n\n- **Format:** Markdown (`.md`)\n- **Location:** `\u002Ftasks\u002F`\n- **Filename:** `tasks-[feature-name].md` (e.g., `tasks-user-profile-editing.md`)\n\n## Process\n\n1.  **Receive Requirements:** The user provides a feature request, task description, or points to existing documentation\n2.  **Analyze Requirements:** The AI analyzes the functional requirements, user needs, and implementation scope from the provided information\n3.  **Phase 1: Generate Parent Tasks:** Based on the requirements analysis, create the file and generate the main, high-level tasks required to implement the feature. **IMPORTANT: Always include task 0.0 \"Create feature branch\" as the first task, unless the user specifically requests not to create a branch.** Use your judgement on how many additional high-level tasks to use. It's likely to be about 5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: \"I have generated the high-level tasks based on your requirements. Ready to generate the sub-tasks? Respond with 'Go' to proceed.\"\n4.  **Wait for Confirmation:** Pause and wait for the user to respond with \"Go\".\n5.  **Phase 2: Generate Sub-Tasks:** Once the user confirms, break down each parent task into smaller, actionable sub-tasks necessary to complete the parent task. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the requirements.\n6.  **Identify Relevant Files:** Based on the tasks and requirements, identify potential files that will need to be created or modified. List these under the `Relevant Files` section, including corresponding test files if applicable.\n7.  **Generate Final Output:** Combine the parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.\n8.  **Save Task List:** Save the generated document in the `\u002Ftasks\u002F` directory with the filename `tasks-[feature-name].md`, where `[feature-name]` describes the main feature or task being implemented (e.g., if the request was about user profile editing, the output is `tasks-user-profile-editing.md`).\n\n## Output Format\n\nThe generated task list _must_ follow this structure:\n\n```markdown\n## Relevant Files\n\n- `path\u002Fto\u002Fpotential\u002Ffile1.ts` - Brief description of why this file is relevant (e.g., Contains the main component for this feature).\n- `path\u002Fto\u002Ffile1.test.ts` - Unit tests for `file1.ts`.\n- `path\u002Fto\u002Fanother\u002Ffile.tsx` - Brief description (e.g., API route handler for data submission).\n- `path\u002Fto\u002Fanother\u002Ffile.test.tsx` - Unit tests for `another\u002Ffile.tsx`.\n- `lib\u002Futils\u002Fhelpers.ts` - Brief description (e.g., Utility functions needed for calculations).\n- `lib\u002Futils\u002Fhelpers.test.ts` - Unit tests for `helpers.ts`.\n\n### Notes\n\n- Unit tests should typically be placed alongside the code files they are testing (e.g., `MyComponent.tsx` and `MyComponent.test.tsx` in the same directory).\n- Use `npx jest [optional\u002Fpath\u002Fto\u002Ftest\u002Ffile]` to run tests. Running without a path executes all tests found by the Jest configuration.\n\n## Instructions for Completing Tasks\n\n**IMPORTANT:** As you complete each task, you must check it off in this markdown file by changing `- [ ]` to `- [x]`. This helps track progress and ensures you don't skip any steps.\n\nExample:\n- `- [ ] 1.1 Read file` → `- [x] 1.1 Read file` (after completing)\n\nUpdate the file after completing each sub-task, not just after completing an entire parent task.\n\n## Tasks\n\n- [ ] 0.0 Create feature branch\n  - [ ] 0.1 Create and checkout a new branch for this feature (e.g., `git checkout -b feature\u002F[feature-name]`)\n- [ ] 1.0 Parent Task Title\n  - [ ] 1.1 [Sub-task description 1.1]\n  - [ ] 1.2 [Sub-task description 1.2]\n- [ ] 2.0 Parent Task Title\n  - [ ] 2.1 [Sub-task description 2.1]\n- [ ] 3.0 Parent Task Title (may not require sub-tasks if purely structural or configuration)\n```\n\n## Interaction Model\n\nThe process explicitly requires a pause after generating parent tasks to get user confirmation (\"Go\") before proceeding to generate the detailed sub-tasks. This ensures the high-level plan aligns with user expectations before diving into details.\n\n## Target Audience\n\nAssume the primary reader of the task list is a **junior developer** who will implement the feature.\n",{"name":5,"description":7},"main","e63965e4644984470d4cc8b3014a8b001f0c2666",".agents\u002Fskills\u002Fcreate-tasks","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fbnferguson","2026-11-11 03:04:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add bnferguson\u002Fdotfiles --skill create-tasks",{"tool":54,"command":55},"bunx","bunx skills add bnferguson\u002Fdotfiles --skill create-tasks",{"tool":57,"command":58},"pnpm","pnpm dlx skills add bnferguson\u002Fdotfiles --skill create-tasks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-tasks\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"REFERENCE.md","REFERENCE","参考文档",7559,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fkubernetes-plugin\u002Fskills\u002Fhelm-values-management\u002FREFERENCE.md",[69,100,117,147,156,169],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":37},"01M6BVA3RS3M016FANZ6792F9H","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude\u002Fconfig\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude\u002Fconfig\u002Fskills\u002Fskill-creator\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[83,84,85,86,19,87,88,89,90,91,92,93,94,95,96,97,98,23,99],"creator","skill creator","specialized","workflows","update","capabilities","knowledge","tool","integrations","guide","new skill","existing skill","users","with","for","Existing","new",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":114,"publishedAt":37},"01M6BV94WN2RPYM8N6PN8TBNT8","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[115,116],"writing shape","writing",{"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":73,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":130,"publishedAt":37},"01M6BV8QDFJ6PXBVK5NFBZT5M7","webapp-testing","Test local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":128,"categoryName":129,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",[131,132,133,134,135,136,137,138,139,140,141,142,143,144,31,145,146,23],"webapp","webapp testing","testing","browser","frontend","screenshots","playwright","test","web","debugging","ui","logs","applications","behavior","local","test local",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":37},"01M6BV8MDXKXNVHKS3QF3YDFTF","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[154,155],"wait what","land",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":165,"publishedAt":37},"01M6BV756DJHT5BDA1HVRVHJJ7","prototype","Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprototype\u002FSKILL.md",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000032","设计师",[158,166,167,141,168],"design","explore","state",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":37},"01M6BV6SBW166685KVBPWM2K4N","improve-codebase-architecture","Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[175],{"categoryNo":128,"categoryName":129,"taxonomyType":80,"taxonomyTypeDesc":81},[177,178,179,180],"architecture","improve","improve codebase architecture","report"]