[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDQ51KVSW4M26EVMV70M41":3,"skill-same:01M6PDQ51KVSW4M26EVMV70M41":63},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6PDQ51KVSW4M26EVMV70M41","openspec-new-change",null,"Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.","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-new-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"change","openspec new change","openspec","cli","workflow","create","start","user","fix","new feature","use","artifact","structured","feature","with","2026-11-10 10:12:30",false,"---\nname: openspec-new-change\ndescription: Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.2.0\"\n---\n\nStart a new change using the experimental artifact-driven approach.\n\n**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.\n\n**Steps**\n\n1. **If no clear input provided, ask what they want to build**\n\n   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:\n   > \"What change do you want to work on? Describe what you want to build or fix.\"\n\n   From their description, derive a kebab-case name (e.g., \"add user authentication\" → `add-user-auth`).\n\n   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.\n\n2. **Determine the workflow schema**\n\n   Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.\n\n   **Use a different schema only if the user mentions:**\n   - A specific schema name → use `--schema \u003Cname>`\n   - \"show workflows\" or \"what workflows\" → run `openspec schemas --json` and let them choose\n\n   **Otherwise**: Omit `--schema` to use the default.\n\n3. **Create the change directory**\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n   Add `--schema \u003Cname>` only if the user requested a specific workflow.\n   This creates a scaffolded change at `openspec\u002Fchanges\u002F\u003Cname>\u002F` with the selected schema.\n\n4. **Show the artifact status**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n   This shows which artifacts need to be created and which are ready (dependencies satisfied).\n\n5. **Get instructions for the first artifact**\n   The first artifact depends on the schema (e.g., `proposal` for spec-driven).\n   Check the status output to find the first artifact with status \"ready\".\n   ```bash\n   openspec instructions \u003Cfirst-artifact-id> --change \"\u003Cname>\"\n   ```\n   This outputs the template and context for creating the first artifact.\n\n6. **STOP and wait for user direction**\n\n**Output**\n\nAfter completing the steps, summarize:\n- Change name and location\n- Schema\u002Fworkflow being used and its artifact sequence\n- Current status (0\u002FN artifacts complete)\n- The template for the first artifact\n- Prompt: \"Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue.\"\n\n**Guardrails**\n- Do NOT create any artifacts yet - just show the instructions\n- Do NOT advance beyond showing the first artifact template\n- If the name is invalid (not kebab-case), ask for a valid name\n- If a change with that name already exists, suggest continuing that change instead\n- Pass --schema if using a non-default workflow\n","Start a new change using the experimental artifact-driven approach.\n\n**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.\n\n**Steps**\n\n1. **If no clear input provided, ask what they want to build**\n\n   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:\n   > \"What change do you want to work on? Describe what you want to build or fix.\"\n\n   From their description, derive a kebab-case name (e.g., \"add user authentication\" → `add-user-auth`).\n\n   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.\n\n2. **Determine the workflow schema**\n\n   Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.\n\n   **Use a different schema only if the user mentions:**\n   - A specific schema name → use `--schema \u003Cname>`\n   - \"show workflows\" or \"what workflows\" → run `openspec schemas --json` and let them choose\n\n   **Otherwise**: Omit `--schema` to use the default.\n\n3. **Create the change directory**\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n   Add `--schema \u003Cname>` only if the user requested a specific workflow.\n   This creates a scaffolded change at `openspec\u002Fchanges\u002F\u003Cname>\u002F` with the selected schema.\n\n4. **Show the artifact status**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n   This shows which artifacts need to be created and which are ready (dependencies satisfied).\n\n5. **Get instructions for the first artifact**\n   The first artifact depends on the schema (e.g., `proposal` for spec-driven).\n   Check the status output to find the first artifact with status \"ready\".\n   ```bash\n   openspec instructions \u003Cfirst-artifact-id> --change \"\u003Cname>\"\n   ```\n   This outputs the template and context for creating the first artifact.\n\n6. **STOP and wait for user direction**\n\n**Output**\n\nAfter completing the steps, summarize:\n- Change name and location\n- Schema\u002Fworkflow being used and its artifact sequence\n- Current status (0\u002FN artifacts complete)\n- The template for the first artifact\n- Prompt: \"Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue.\"\n\n**Guardrails**\n- Do NOT create any artifacts yet - just show the instructions\n- Do NOT advance beyond showing the first artifact template\n- If the name is invalid (not kebab-case), ask for a valid name\n- If a change with that name already exists, suggest continuing that change instead\n- Pass --schema if using a non-default workflow\n",{"name":5,"license":15,"metadata":39,"description":7,"compatibility":42},{"author":21,"version":40,"generatedBy":41},"1.0","1.2.0","Requires openspec CLI.","main","62141d825eb73b2f691358c081d3da7d67278315",".claude\u002Fskills\u002Fopenspec-new-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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add castle-x\u002Fsonar --skill openspec-new-change",{"tool":55,"command":56},"bunx","bunx skills add castle-x\u002Fsonar --skill openspec-new-change",{"tool":58,"command":59},"pnpm","pnpm dlx skills add castle-x\u002Fsonar --skill openspec-new-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcastle-x\u002Fsonar\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-new-change\u002FSKILL.md",true,[],[64,98,124,150,172,191],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":78,"publishedAt":34},"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",[70,75],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":76,"categoryName":77,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000015","视觉设计",[79,80,81,82,83,84,85,23,86,87,88,89,90,91,92,93,94,95,96,97],"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":110,"publishedAt":34},"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",[104,105],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[111,112,113,79,85,86,87,114,115,116,117,80,118,119,120,121,90,122,97,123],"shadcn","ui","shadcn ui","react components","component","component library","nextjs","Bash","zod","read","up","themes","ui patterns",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":137,"publishedAt":34},"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",[130,133,134],{"categoryNo":131,"categoryName":132,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":135,"categoryName":136,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",[87,138,81,139,140,141,86,115,142,143,144,145,118,120,146,90,147,148,149,97],"react patterns","testing","frontend","performance","architecture","component architecture","server","actions","hooks","expert","react 19","Server Components",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":34},"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",[156],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[87,158,159,160,161,162,141,86,163,164,29,165,166,167,168,169,33,97,170,171],"vercel react native skills","react native","vercel","react native skills","native","tasks","best practices","modules","platform","triggers","apps","react native components","for","animations",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":34},"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",[178],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[87,180,164,181,160,182,141,86,114,183,163,184,185,186,187,81,188,189,167,190],"vercel react best practices","react best practices","writing","guidelines","code","Optimization","data","refactoring","next","pages","data fetching",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":34},"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,198,199,200,21,22,201,202,203,26,29,204,205,206,207],"openspec verify change","verify","verify change","validate","artifacts","correct","implementation","coherent","verify implementation","complete"]