[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDPHHB89G33H01EN5VJK9J":3,"skill-same:01M6PDPHHB89G33H01EN5VJK9J":60},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6PDPHHB89G33H01EN5VJK9J","openspec-continue-change",null,"Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.","castle-x\u002Fsonar","castle-x","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68362913?v=4","01M6PDKZEWWT760P3FFZZQ42SD","castlexu","01M6PDKZJTJXTRH54309WXD6YR",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-continue-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"change","openspec continue change","continue","openspec","cli","workflow","create","user","use","next","artifact","progress","2026-11-10 10:12:30",false,"---\nname: openspec-continue-change\ndescription: Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.2.0\"\n---\n\nContinue working on a change by creating the next artifact.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.\n\n   Present the top 3-4 most recently modified changes as options, showing:\n   - Change name\n   - Schema (from `schema` field if present, otherwise \"spec-driven\")\n   - Status (e.g., \"0\u002F5 tasks\", \"complete\", \"no tasks\")\n   - How recently it was modified (from `lastModified` field)\n\n   Mark the most recently modified change as \"(Recommended)\" since it's likely what the user wants to continue.\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check current status**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand current state. The response includes:\n   - `schemaName`: The workflow schema being used (e.g., \"spec-driven\")\n   - `artifacts`: Array of artifacts with their status (\"done\", \"ready\", \"blocked\")\n   - `isComplete`: Boolean indicating if all artifacts are complete\n\n3. **Act based on status**:\n\n   ---\n\n   **If all artifacts are complete (`isComplete: true`)**:\n   - Congratulate the user\n   - Show final status including the schema used\n   - Suggest: \"All artifacts created! You can now implement this change or archive it.\"\n   - STOP\n\n   ---\n\n   **If artifacts are ready to create** (status shows artifacts with `status: \"ready\"`):\n   - Pick the FIRST artifact with `status: \"ready\"` from the status output\n   - Get its instructions:\n     ```bash\n     openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json\n     ```\n   - Parse the JSON. The key fields are:\n     - `context`: Project background (constraints for you - do NOT include in output)\n     - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)\n     - `template`: The structure to use for your output file\n     - `instruction`: Schema-specific guidance\n     - `outputPath`: Where to write the artifact\n     - `dependencies`: Completed artifacts to read for context\n   - **Create the artifact file**:\n     - Read any completed dependency files for context\n     - Use `template` as the structure - fill in its sections\n     - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file\n     - Write to the output path specified in instructions\n   - Show what was created and what's now unlocked\n   - STOP after creating ONE artifact\n\n   ---\n\n   **If no artifacts are ready (all blocked)**:\n   - This shouldn't happen with a valid schema\n   - Show status and suggest checking for issues\n\n4. **After creating an artifact, show progress**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n\n**Output**\n\nAfter each invocation, show:\n- Which artifact was created\n- Schema workflow being used\n- Current progress (N\u002FM complete)\n- What artifacts are now unlocked\n- Prompt: \"Want to continue? Just ask me to continue or tell me what to do next.\"\n\n**Artifact Creation Guidelines**\n\nThe artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.\n\nCommon artifact patterns:\n\n**spec-driven schema** (proposal → specs → design → tasks):\n- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.\n  - The Capabilities section is critical - each capability listed will need a spec file.\n- **specs\u002F\u003Ccapability>\u002Fspec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).\n- **design.md**: Document technical decisions, architecture, and implementation approach.\n- **tasks.md**: Break down implementation into checkboxed tasks.\n\nFor other schemas, follow the `instruction` field from the CLI output.\n\n**Guardrails**\n- Create ONE artifact per invocation\n- Always read dependency artifacts before creating a new one\n- Never skip artifacts or create out of order\n- If context is unclear, ask the user before creating\n- Verify the artifact file exists after writing before marking progress\n- Use the schema's artifact sequence, don't assume specific artifact names\n- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file\n  - Do NOT copy `\u003Ccontext>`, `\u003Crules>`, `\u003Cproject_context>` blocks into the artifact\n  - These guide what you write, but should never appear in the output\n","Continue working on a change by creating the next artifact.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.\n\n   Present the top 3-4 most recently modified changes as options, showing:\n   - Change name\n   - Schema (from `schema` field if present, otherwise \"spec-driven\")\n   - Status (e.g., \"0\u002F5 tasks\", \"complete\", \"no tasks\")\n   - How recently it was modified (from `lastModified` field)\n\n   Mark the most recently modified change as \"(Recommended)\" since it's likely what the user wants to continue.\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check current status**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand current state. The response includes:\n   - `schemaName`: The workflow schema being used (e.g., \"spec-driven\")\n   - `artifacts`: Array of artifacts with their status (\"done\", \"ready\", \"blocked\")\n   - `isComplete`: Boolean indicating if all artifacts are complete\n\n3. **Act based on status**:\n\n   ---\n\n   **If all artifacts are complete (`isComplete: true`)**:\n   - Congratulate the user\n   - Show final status including the schema used\n   - Suggest: \"All artifacts created! You can now implement this change or archive it.\"\n   - STOP\n\n   ---\n\n   **If artifacts are ready to create** (status shows artifacts with `status: \"ready\"`):\n   - Pick the FIRST artifact with `status: \"ready\"` from the status output\n   - Get its instructions:\n     ```bash\n     openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json\n     ```\n   - Parse the JSON. The key fields are:\n     - `context`: Project background (constraints for you - do NOT include in output)\n     - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)\n     - `template`: The structure to use for your output file\n     - `instruction`: Schema-specific guidance\n     - `outputPath`: Where to write the artifact\n     - `dependencies`: Completed artifacts to read for context\n   - **Create the artifact file**:\n     - Read any completed dependency files for context\n     - Use `template` as the structure - fill in its sections\n     - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file\n     - Write to the output path specified in instructions\n   - Show what was created and what's now unlocked\n   - STOP after creating ONE artifact\n\n   ---\n\n   **If no artifacts are ready (all blocked)**:\n   - This shouldn't happen with a valid schema\n   - Show status and suggest checking for issues\n\n4. **After creating an artifact, show progress**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n\n**Output**\n\nAfter each invocation, show:\n- Which artifact was created\n- Schema workflow being used\n- Current progress (N\u002FM complete)\n- What artifacts are now unlocked\n- Prompt: \"Want to continue? Just ask me to continue or tell me what to do next.\"\n\n**Artifact Creation Guidelines**\n\nThe artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.\n\nCommon artifact patterns:\n\n**spec-driven schema** (proposal → specs → design → tasks):\n- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.\n  - The Capabilities section is critical - each capability listed will need a spec file.\n- **specs\u002F\u003Ccapability>\u002Fspec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).\n- **design.md**: Document technical decisions, architecture, and implementation approach.\n- **tasks.md**: Break down implementation into checkboxed tasks.\n\nFor other schemas, follow the `instruction` field from the CLI output.\n\n**Guardrails**\n- Create ONE artifact per invocation\n- Always read dependency artifacts before creating a new one\n- Never skip artifacts or create out of order\n- If context is unclear, ask the user before creating\n- Verify the artifact file exists after writing before marking progress\n- Use the schema's artifact sequence, don't assume specific artifact names\n- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file\n  - Do NOT copy `\u003Ccontext>`, `\u003Crules>`, `\u003Cproject_context>` blocks into the artifact\n  - These guide what you write, but should never appear in the output\n",{"name":5,"license":15,"metadata":36,"description":7,"compatibility":39},{"author":22,"version":37,"generatedBy":38},"1.0","1.2.0","Requires openspec CLI.","main","62141d825eb73b2f691358c081d3da7d67278315",".claude\u002Fskills\u002Fopenspec-continue-change","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar","https:\u002F\u002Fgithub.com\u002Fcastle-x","2026-06-01 15:59:22",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add castle-x\u002Fsonar --skill openspec-continue-change",{"tool":52,"command":53},"bunx","bunx skills add castle-x\u002Fsonar --skill openspec-continue-change",{"tool":55,"command":56},"pnpm","pnpm dlx skills add castle-x\u002Fsonar --skill openspec-continue-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-continue-change\u002FSKILL.md",true,[],[61,95,121,147,170,188],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":75,"publishedAt":31},"01M6PE1J3SKAAEVNCW7NTJ3TWH","tailwind-css-patterns","Comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React\u002FVue\u002FSvelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.legacy\u002Fdatasource\u002F.codebuddy\u002Fskills\u002Ftailwind-css-patterns\u002FSKILL.md",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000015","视觉设计",[76,77,78,79,80,81,82,24,83,84,85,86,87,88,89,90,91,92,93,94],"css","Tailwind","patterns","Tailwind CSS","tailwind css patterns","design","tailwindcss","components","react","design systems","styling","tsx","responsive design","layout","svelte","utility","Utilities","spacing","implementing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":107,"publishedAt":31},"01M6PE0PCVCSDMP855MEAXEHCD","shadcn-ui","Complete shadcn\u002Fui component library guide including installation, configuration, and implementation of accessible React components. Use when setting up shadcn\u002Fui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like buttons, dialogs, dropdowns, tables, and complex form layouts.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.legacy\u002Fdatasource\u002F.codebuddy\u002Fskills\u002Fshadcn-ui\u002FSKILL.md",[101,102],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[108,109,110,76,82,83,84,111,112,113,114,77,115,116,117,118,87,119,94,120],"shadcn","ui","shadcn ui","react components","component","component library","nextjs","Bash","zod","read","up","themes","ui patterns",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":134,"publishedAt":31},"01M6PDZXXE4RRAVMJB5JH8S7B7","react-patterns","Comprehensive React 19 patterns expert covering Server Components, Actions, use() hook, useOptimistic, useFormStatus, useFormState, React Compiler, concurrent features, Suspense, and modern TypeScript development. Proactively use for any React development, component architecture, state management, performance optimization, or when implementing React 19's latest features.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.legacy\u002Fdatasource\u002F.codebuddy\u002Fskills\u002Freact-patterns\u002FSKILL.md",[127,130,131],{"categoryNo":128,"categoryName":129,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":132,"categoryName":133,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000010","后端与接口",[84,135,78,136,137,138,83,112,139,140,141,142,115,117,143,87,144,145,146,94],"react patterns","testing","frontend","performance","architecture","component architecture","server","actions","hooks","expert","react 19","Server Components",{"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":154,"publishedAt":31},"01M6PDZK79YYADCGJTJDBRK1HQ","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.legacy\u002Fdatasource\u002F.codebuddy\u002Fskills\u002Freact-native-skills\u002FSKILL.md",[153],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[84,155,156,157,158,159,138,83,160,161,27,162,163,164,165,166,167,94,168,169],"vercel react native skills","react native","vercel","react native skills","native","tasks","best practices","modules","platform","triggers","apps","react native components","with","for","animations",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"publishedAt":31},"01M6PDZ8YY9QHYZQFWHAFJSJGK","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.legacy\u002Fdatasource\u002F.codebuddy\u002Fskills\u002Freact-best-practices\u002FSKILL.md",[176],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[84,178,161,179,157,180,138,83,111,181,160,182,183,184,185,78,28,186,164,187],"vercel react best practices","react best practices","writing","guidelines","code","Optimization","data","refactoring","pages","data fetching",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":31},"01M6PDR22TXCNQ5220G6Y1WZ83","openspec-verify-change","Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.","https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-verify-change\u002FSKILL.md",[],[19,195,196,197,22,23,198,199,200,26,27,201,202,203,204],"openspec verify change","verify","verify change","validate","artifacts","correct","implementation","coherent","verify implementation","complete"]