[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T31CCYEBPCS4DF97HP13W":3,"skill-same:01M77T31CCYEBPCS4DF97HP13W":54},{"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},"01M77T31CCYEBPCS4DF97HP13W","sdd-init",null,"Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.","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-init\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdd-init\ndescription: \"Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.\"\ndisable-model-invocation: true\nuser-invocable: false\nlicense: MIT\nmetadata:\n  author: gentleman-programming\n  version: \"3.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-init` 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## Activation Contract\n\nRun this phase when the orchestrator\u002Fuser asks to initialize SDD in a project. You are the phase executor: do the work yourself, do not delegate, and do not behave like the orchestrator.\n\n## Hard Rules\n\n- Detect the real stack, conventions, architecture, testing tools, and persistence mode; never guess.\n- In `engram` mode, do **not** create `openspec\u002F`.\n- In `openspec` mode, follow `..\u002F_shared\u002Fopenspec-convention.md` and write file artifacts.\n- In `hybrid` mode, write both openspec files and Engram observations.\n- Always persist testing capabilities separately as `sdd\u002F{project}\u002Ftesting-capabilities` or `openspec\u002Fconfig.yaml` `testing:`.\n- Always build `.atl\u002Fskill-registry.md`; also save `skill-registry` to Engram when available.\n- Use `capture_prompt: false` for automated SDD\u002Fconfig saves when supported; omit it if the tool schema lacks it.\n- If `openspec\u002F` already exists, report what exists and ask before updating it.\n\n## Decision Gates\n\n| Input | Action |\n|---|---|\n| `mode=engram` | Save context and capabilities to Engram only. |\n| `mode=openspec` | Create\u002Fupdate openspec bootstrap files only. |\n| `mode=hybrid` | Do both Engram and openspec persistence. |\n| `mode=none` | Return detected context only; write no SDD artifacts except registry if required. |\n| strict TDD marker\u002Fconfig found | Use that value. |\n| no marker\u002Fconfig but test runner exists | Default `strict_tdd: true`. |\n| no test runner | Set `strict_tdd: false` and explain unavailable. |\n\n## Execution Steps\n\n1. Inspect project files (`package.json`, `go.mod`, `pyproject.toml`, CI, lint\u002Ftest config) and summarize stack\u002Fconventions.\n2. Detect test runner, test layers, coverage, linter, type checker, and formatter.\n3. Resolve Strict TDD from agent marker, `openspec\u002Fconfig.yaml`, detected runner fallback, or no-runner fallback.\n4. Initialize persistence for the resolved mode.\n5. Build `.atl\u002Fskill-registry.md` using the skill-registry scan rules.\n6. Persist testing capabilities and project context.\n7. Return the structured initialization envelope.\n\n## Output Contract\n\nReturn `status`, `executive_summary`, `artifacts`, `next_recommended`, and `risks`. Include project, stack, persistence mode, Strict TDD status, testing capability table, saved observation IDs\u002Fpaths, registry path, and next `\u002Fsdd-explore` or `\u002Fsdd-new` step.\n\n## References\n\n- [references\u002Finit-details.md](references\u002Finit-details.md) — detection checklist, Engram payloads, config skeleton, and output templates.\n- `..\u002F_shared\u002Fengram-convention.md` — Engram artifact naming.\n- `..\u002F_shared\u002Fopenspec-convention.md` — openspec layout and rules.\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-init` 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## Activation Contract\n\nRun this phase when the orchestrator\u002Fuser asks to initialize SDD in a project. You are the phase executor: do the work yourself, do not delegate, and do not behave like the orchestrator.\n\n## Hard Rules\n\n- Detect the real stack, conventions, architecture, testing tools, and persistence mode; never guess.\n- In `engram` mode, do **not** create `openspec\u002F`.\n- In `openspec` mode, follow `..\u002F_shared\u002Fopenspec-convention.md` and write file artifacts.\n- In `hybrid` mode, write both openspec files and Engram observations.\n- Always persist testing capabilities separately as `sdd\u002F{project}\u002Ftesting-capabilities` or `openspec\u002Fconfig.yaml` `testing:`.\n- Always build `.atl\u002Fskill-registry.md`; also save `skill-registry` to Engram when available.\n- Use `capture_prompt: false` for automated SDD\u002Fconfig saves when supported; omit it if the tool schema lacks it.\n- If `openspec\u002F` already exists, report what exists and ask before updating it.\n\n## Decision Gates\n\n| Input | Action |\n|---|---|\n| `mode=engram` | Save context and capabilities to Engram only. |\n| `mode=openspec` | Create\u002Fupdate openspec bootstrap files only. |\n| `mode=hybrid` | Do both Engram and openspec persistence. |\n| `mode=none` | Return detected context only; write no SDD artifacts except registry if required. |\n| strict TDD marker\u002Fconfig found | Use that value. |\n| no marker\u002Fconfig but test runner exists | Default `strict_tdd: true`. |\n| no test runner | Set `strict_tdd: false` and explain unavailable. |\n\n## Execution Steps\n\n1. Inspect project files (`package.json`, `go.mod`, `pyproject.toml`, CI, lint\u002Ftest config) and summarize stack\u002Fconventions.\n2. Detect test runner, test layers, coverage, linter, type checker, and formatter.\n3. Resolve Strict TDD from agent marker, `openspec\u002Fconfig.yaml`, detected runner fallback, or no-runner fallback.\n4. Initialize persistence for the resolved mode.\n5. Build `.atl\u002Fskill-registry.md` using the skill-registry scan rules.\n6. Persist testing capabilities and project context.\n7. Return the structured initialization envelope.\n\n## Output Contract\n\nReturn `status`, `executive_summary`, `artifacts`, `next_recommended`, and `risks`. Include project, stack, persistence mode, Strict TDD status, testing capability table, saved observation IDs\u002Fpaths, registry path, and next `\u002Fsdd-explore` or `\u002Fsdd-new` step.\n\n## References\n\n- [references\u002Finit-details.md](references\u002Finit-details.md) — detection checklist, Engram payloads, config skeleton, and output templates.\n- `..\u002F_shared\u002Fengram-convention.md` — Engram artifact naming.\n- `..\u002F_shared\u002Fopenspec-convention.md` — openspec layout and rules.\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","3.0",true,"main","ba43a4e7e8b0fd6b150b14bcb48978ec40879a28",".agents\u002Fskills\u002Fsdd-init","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-init",{"tool":41,"command":42},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill sdd-init",{"tool":44,"command":45},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill sdd-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-init\u002FSKILL.md",[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Finit-details.md","REFERENCE","参考文档",4757,"https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-init\u002Freferences\u002Finit-details.md",[55,63,70,77,84,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]