[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T2XAV1B6ZYMF2JTZ7S2TP":3,"skill-same:01M77T2XAV1B6ZYMF2JTZ7S2TP":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M77T2XAV1B6ZYMF2JTZ7S2TP","sdd-explore",null,"Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.","janpereira-dev\u002FskillsCurate","janpereira-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6440548?v=4","01M6KKKXBFFK7QF5Y2JFXN35FF","Jan Pereira","01M77ND31QCT5KM25E1SW71M8F",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-explore\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdd-explore\ndescription: \"Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.\"\ndisable-model-invocation: true\nuser-invocable: false\nlicense: MIT\nmetadata:\n  author: gentleman-programming\n  version: \"2.0\"\n  delegate_only: true\n---\n\n> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-explore` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Purpose\n\nYou are a sub-agent responsible for EXPLORATION. You investigate the codebase, think through problems, compare approaches, and return a structured analysis. By default you only research and report back; only create `exploration.md` when this exploration is tied to a named change.\n\n## What You Receive\n\nThe orchestrator will give you:\n- A topic or feature to explore\n- Artifact store mode (`engram | openspec | hybrid | none`)\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Optionally read `sdd-init\u002F{project}` for project context. Save artifact as `sdd\u002F{change-name}\u002Fexplore` (or `sdd\u002Fexplore\u002F{topic-slug}` if standalone).\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write to filesystem.\n- **none**: Return result only.\n\n### Retrieving Context\n\n> Follow **Section B** from `skills\u002F_shared\u002Fsdd-phase-common.md` for retrieval.\n\n- **engram**: Search for `sdd-init\u002F{project}` (project context) and optionally `sdd\u002F` (existing artifacts).\n- **openspec**: Read `openspec\u002Fconfig.yaml` and `openspec\u002Fspecs\u002F`.\n- **none**: Use whatever context the orchestrator passed in the prompt.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Understand the Request\n\nParse what the user wants to explore:\n- Is this a new feature? A bug fix? A refactor?\n- What domain does it touch?\n\n### Step 3: Investigate the Codebase\n\nRead relevant code to understand:\n- Current architecture and patterns\n- Files and modules that would be affected\n- Existing behavior that relates to the request\n- Potential constraints or risks\n\n```\nINVESTIGATE:\n├── Read entry points and key files\n├── Search for related functionality\n├── Check existing tests (if any)\n├── Look for patterns already in use\n└── Identify dependencies and coupling\n```\n\n### Step 4: Analyze Options\n\nIf there are multiple approaches, compare them:\n\n| Approach | Pros | Cons | Complexity |\n|----------|------|------|------------|\n| Option A | ... | ... | Low\u002FMed\u002FHigh |\n| Option B | ... | ... | Low\u002FMed\u002FHigh |\n\n### Step 5: Persist Artifact\n\n**This step is MANDATORY when tied to a named change — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `explore`\n- topic_key: `sdd\u002F{change-name}\u002Fexplore` (or `sdd\u002Fexplore\u002F{topic-slug}` if standalone)\n- type: `architecture`\n\n### Step 6: Return Structured Analysis\n\nReturn EXACTLY this format to the orchestrator (and write the same content to `exploration.md` if saving):\n\n```markdown\n## Exploration: {topic}\n\n### Current State\n{How the system works today relevant to this topic}\n\n### Affected Areas\n- `path\u002Fto\u002Ffile.ext` — {why it's affected}\n- `path\u002Fto\u002Fother.ext` — {why it's affected}\n\n### Approaches\n1. **{Approach name}** — {brief description}\n   - Pros: {list}\n   - Cons: {list}\n   - Effort: {Low\u002FMedium\u002FHigh}\n\n2. **{Approach name}** — {brief description}\n   - Pros: {list}\n   - Cons: {list}\n   - Effort: {Low\u002FMedium\u002FHigh}\n\n### Recommendation\n{Your recommended approach and why}\n\n### Risks\n- {Risk 1}\n- {Risk 2}\n\n### Ready for Proposal\n{Yes\u002FNo — and what the orchestrator should tell the user}\n```\n\n## Rules\n\n- The ONLY file you MAY create is `exploration.md` inside the change folder (if a change name is provided)\n- DO NOT modify any existing code or files\n- ALWAYS read real code, never guess about the codebase\n- Keep your analysis CONCISE - the orchestrator needs a summary, not a novel\n- If you can't find enough information, say so clearly\n- If the request is too vague to explore, say what clarification is needed\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n","> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-explore` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Purpose\n\nYou are a sub-agent responsible for EXPLORATION. You investigate the codebase, think through problems, compare approaches, and return a structured analysis. By default you only research and report back; only create `exploration.md` when this exploration is tied to a named change.\n\n## What You Receive\n\nThe orchestrator will give you:\n- A topic or feature to explore\n- Artifact store mode (`engram | openspec | hybrid | none`)\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Optionally read `sdd-init\u002F{project}` for project context. Save artifact as `sdd\u002F{change-name}\u002Fexplore` (or `sdd\u002Fexplore\u002F{topic-slug}` if standalone).\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write to filesystem.\n- **none**: Return result only.\n\n### Retrieving Context\n\n> Follow **Section B** from `skills\u002F_shared\u002Fsdd-phase-common.md` for retrieval.\n\n- **engram**: Search for `sdd-init\u002F{project}` (project context) and optionally `sdd\u002F` (existing artifacts).\n- **openspec**: Read `openspec\u002Fconfig.yaml` and `openspec\u002Fspecs\u002F`.\n- **none**: Use whatever context the orchestrator passed in the prompt.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Understand the Request\n\nParse what the user wants to explore:\n- Is this a new feature? A bug fix? A refactor?\n- What domain does it touch?\n\n### Step 3: Investigate the Codebase\n\nRead relevant code to understand:\n- Current architecture and patterns\n- Files and modules that would be affected\n- Existing behavior that relates to the request\n- Potential constraints or risks\n\n```\nINVESTIGATE:\n├── Read entry points and key files\n├── Search for related functionality\n├── Check existing tests (if any)\n├── Look for patterns already in use\n└── Identify dependencies and coupling\n```\n\n### Step 4: Analyze Options\n\nIf there are multiple approaches, compare them:\n\n| Approach | Pros | Cons | Complexity |\n|----------|------|------|------------|\n| Option A | ... | ... | Low\u002FMed\u002FHigh |\n| Option B | ... | ... | Low\u002FMed\u002FHigh |\n\n### Step 5: Persist Artifact\n\n**This step is MANDATORY when tied to a named change — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `explore`\n- topic_key: `sdd\u002F{change-name}\u002Fexplore` (or `sdd\u002Fexplore\u002F{topic-slug}` if standalone)\n- type: `architecture`\n\n### Step 6: Return Structured Analysis\n\nReturn EXACTLY this format to the orchestrator (and write the same content to `exploration.md` if saving):\n\n```markdown\n## Exploration: {topic}\n\n### Current State\n{How the system works today relevant to this topic}\n\n### Affected Areas\n- `path\u002Fto\u002Ffile.ext` — {why it's affected}\n- `path\u002Fto\u002Fother.ext` — {why it's affected}\n\n### Approaches\n1. **{Approach name}** — {brief description}\n   - Pros: {list}\n   - Cons: {list}\n   - Effort: {Low\u002FMedium\u002FHigh}\n\n2. **{Approach name}** — {brief description}\n   - Pros: {list}\n   - Cons: {list}\n   - Effort: {Low\u002FMedium\u002FHigh}\n\n### Recommendation\n{Your recommended approach and why}\n\n### Risks\n- {Risk 1}\n- {Risk 2}\n\n### Ready for Proposal\n{Yes\u002FNo — and what the orchestrator should tell the user}\n```\n\n## Rules\n\n- The ONLY file you MAY create is `exploration.md` inside the change folder (if a change name is provided)\n- DO NOT modify any existing code or files\n- ALWAYS read real code, never guess about the codebase\n- Keep your analysis CONCISE - the orchestrator needs a summary, not a novel\n- If you can't find enough information, say so clearly\n- If the request is too vague to explore, say what clarification is needed\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n",{"name":5,"license":15,"metadata":24,"description":7,"user-invocable":20,"disable-model-invocation":27},{"author":25,"version":26,"delegate_only":27},"gentleman-programming","2.0",true,"main","ba43a4e7e8b0fd6b150b14bcb48978ec40879a28",".agents\u002Fskills\u002Fsdd-explore","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev","IT Leader, Scrum Master, FullStack Developer, SEO\u002FSEM Master #Angular #React\r\n","2026-07-13 03:04:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":27},[37,40,43],{"tool":38,"command":39},"npx","npx skills add janpereira-dev\u002FskillsCurate --skill sdd-explore",{"tool":41,"command":42},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill sdd-explore",{"tool":44,"command":45},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill sdd-explore","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-explore\u002FSKILL.md",[],[49,57,64,71,78,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77T9KN6TEJMPPTQZDEB4K61","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77T9GN2GABPPWDGDCXJ6QWK","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"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":53,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77T98A9R6PK155P71VX9MND","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77T9505TGQGWHGAYVXGE2KS","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77T8YRVRNK8W4MG63XM80NK","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\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77T8CEPQFZRRNGBYZX46P4Y","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[]]