[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T2PNDBCDXWX6SE4FK05VR":3,"skill-same:01M77T2PNDBCDXWX6SE4FK05VR":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},"01M77T2PNDBCDXWX6SE4FK05VR","sdd-archive",null,"Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.","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-archive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdd-archive\ndescription: \"Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.\"\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-archive` 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 ARCHIVING. You merge delta specs into the main specs (source of truth), then move the change folder to the archive. You complete the SDD cycle.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\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**: Read `sdd\u002F{change-name}\u002Fproposal`, `sdd\u002F{change-name}\u002Fspec`, `sdd\u002F{change-name}\u002Fdesign`, `sdd\u002F{change-name}\u002Ftasks`, `sdd\u002F{change-name}\u002Fverify-report` (all required). Record all observation IDs in the archive report for traceability. Save as `sdd\u002F{change-name}\u002Farchive-report`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`. Perform merge and archive folder moves.\n- **hybrid**: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive folder moves.\n- **none**: Return closure summary only. Do not perform archive file operations.\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: Sync Delta Specs to Main Specs\n\n**IF mode is `engram`:** Skip filesystem sync — artifacts live in Engram only. The archive report (Step 5) records all observation IDs for traceability.\n\n**IF mode is `none`:** Skip — no artifacts to sync.\n\n**IF mode is `openspec` or `hybrid`:** For each delta spec in `openspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F`:\n\n#### If Main Spec Exists (`openspec\u002Fspecs\u002F{domain}\u002Fspec.md`)\n\nRead the existing main spec and apply the delta:\n\n```\nFOR EACH SECTION in delta spec:\n├── ADDED Requirements → Append to main spec's Requirements section\n├── MODIFIED Requirements → Replace the matching requirement in main spec\n└── REMOVED Requirements → Delete the matching requirement from main spec\n```\n\n**Merge carefully:**\n- Match requirements by name (e.g., \"### Requirement: Session Expiration\")\n- Preserve all OTHER requirements that aren't in the delta\n- Maintain proper Markdown formatting and heading hierarchy\n\n#### If Main Spec Does NOT Exist\n\nThe delta spec IS a full spec (not a delta). Copy it directly:\n\n```bash\n# Copy new spec to main specs\nopenspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F{domain}\u002Fspec.md\n  → openspec\u002Fspecs\u002F{domain}\u002Fspec.md\n```\n\n### Step 3: Move to Archive\n\n**IF mode is `engram`:** Skip — there are no `openspec\u002F` directories to move. The archive report in Engram serves as the audit trail.\n\n**IF mode is `none`:** Skip — no filesystem operations.\n\n**IF mode is `openspec` or `hybrid`:** Move the entire change folder to archive with date prefix:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n  → openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-{change-name}\u002F\n```\n\nUse today's date in ISO format (e.g., `2026-02-16`).\n\n### Step 4: Verify Archive\n\n**IF mode is `openspec` or `hybrid`:** Confirm:\n- [ ] Main specs updated correctly\n- [ ] Change folder moved to archive\n- [ ] Archive contains all artifacts (proposal, specs, design, tasks)\n- [ ] Active changes directory no longer has this change\n\n**IF mode is `engram`:** Confirm all artifact observation IDs are recorded in the archive report.\n\n**IF mode is `none`:** Skip verification — no persisted artifacts.\n\n### Step 5: Persist Archive Report\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `archive-report`\n- topic_key: `sdd\u002F{change-name}\u002Farchive-report`\n- type: `architecture`\n\n### Step 6: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Change Archived\n\n**Change**: {change-name}\n**Archived to**: `openspec\u002Fchanges\u002Farchive\u002F{YYYY-MM-DD}-{change-name}\u002F` (openspec\u002Fhybrid) | Engram archive report (engram) | inline (none)\n\n### Specs Synced\n| Domain | Action | Details |\n|--------|--------|---------|\n| {domain} | Created\u002FUpdated | {N added, M modified, K removed requirements} |\n\n### Archive Contents\n- proposal.md ✅\n- specs\u002F ✅\n- design.md ✅\n- tasks.md ✅ ({N}\u002F{N} tasks complete)\n\n### Source of Truth Updated\nThe following specs now reflect the new behavior:\n- `openspec\u002Fspecs\u002F{domain}\u002Fspec.md`\n\n### SDD Cycle Complete\nThe change has been fully planned, implemented, verified, and archived.\nReady for the next change.\n```\n\n## Rules\n\n- NEVER archive a change that has CRITICAL issues in its verification report\n- ALWAYS sync delta specs BEFORE moving to archive\n- When merging into existing specs, PRESERVE requirements not mentioned in the delta\n- Use ISO date format (YYYY-MM-DD) for archive folder prefix\n- If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation\n- The archive is an AUDIT TRAIL — never delete or modify archived changes\n- If `openspec\u002Fchanges\u002Farchive\u002F` doesn't exist, create it\n- Apply any `rules.archive` from `openspec\u002Fconfig.yaml`\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-archive` 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 ARCHIVING. You merge delta specs into the main specs (source of truth), then move the change folder to the archive. You complete the SDD cycle.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\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**: Read `sdd\u002F{change-name}\u002Fproposal`, `sdd\u002F{change-name}\u002Fspec`, `sdd\u002F{change-name}\u002Fdesign`, `sdd\u002F{change-name}\u002Ftasks`, `sdd\u002F{change-name}\u002Fverify-report` (all required). Record all observation IDs in the archive report for traceability. Save as `sdd\u002F{change-name}\u002Farchive-report`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`. Perform merge and archive folder moves.\n- **hybrid**: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive folder moves.\n- **none**: Return closure summary only. Do not perform archive file operations.\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: Sync Delta Specs to Main Specs\n\n**IF mode is `engram`:** Skip filesystem sync — artifacts live in Engram only. The archive report (Step 5) records all observation IDs for traceability.\n\n**IF mode is `none`:** Skip — no artifacts to sync.\n\n**IF mode is `openspec` or `hybrid`:** For each delta spec in `openspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F`:\n\n#### If Main Spec Exists (`openspec\u002Fspecs\u002F{domain}\u002Fspec.md`)\n\nRead the existing main spec and apply the delta:\n\n```\nFOR EACH SECTION in delta spec:\n├── ADDED Requirements → Append to main spec's Requirements section\n├── MODIFIED Requirements → Replace the matching requirement in main spec\n└── REMOVED Requirements → Delete the matching requirement from main spec\n```\n\n**Merge carefully:**\n- Match requirements by name (e.g., \"### Requirement: Session Expiration\")\n- Preserve all OTHER requirements that aren't in the delta\n- Maintain proper Markdown formatting and heading hierarchy\n\n#### If Main Spec Does NOT Exist\n\nThe delta spec IS a full spec (not a delta). Copy it directly:\n\n```bash\n# Copy new spec to main specs\nopenspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F{domain}\u002Fspec.md\n  → openspec\u002Fspecs\u002F{domain}\u002Fspec.md\n```\n\n### Step 3: Move to Archive\n\n**IF mode is `engram`:** Skip — there are no `openspec\u002F` directories to move. The archive report in Engram serves as the audit trail.\n\n**IF mode is `none`:** Skip — no filesystem operations.\n\n**IF mode is `openspec` or `hybrid`:** Move the entire change folder to archive with date prefix:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n  → openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-{change-name}\u002F\n```\n\nUse today's date in ISO format (e.g., `2026-02-16`).\n\n### Step 4: Verify Archive\n\n**IF mode is `openspec` or `hybrid`:** Confirm:\n- [ ] Main specs updated correctly\n- [ ] Change folder moved to archive\n- [ ] Archive contains all artifacts (proposal, specs, design, tasks)\n- [ ] Active changes directory no longer has this change\n\n**IF mode is `engram`:** Confirm all artifact observation IDs are recorded in the archive report.\n\n**IF mode is `none`:** Skip verification — no persisted artifacts.\n\n### Step 5: Persist Archive Report\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `archive-report`\n- topic_key: `sdd\u002F{change-name}\u002Farchive-report`\n- type: `architecture`\n\n### Step 6: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Change Archived\n\n**Change**: {change-name}\n**Archived to**: `openspec\u002Fchanges\u002Farchive\u002F{YYYY-MM-DD}-{change-name}\u002F` (openspec\u002Fhybrid) | Engram archive report (engram) | inline (none)\n\n### Specs Synced\n| Domain | Action | Details |\n|--------|--------|---------|\n| {domain} | Created\u002FUpdated | {N added, M modified, K removed requirements} |\n\n### Archive Contents\n- proposal.md ✅\n- specs\u002F ✅\n- design.md ✅\n- tasks.md ✅ ({N}\u002F{N} tasks complete)\n\n### Source of Truth Updated\nThe following specs now reflect the new behavior:\n- `openspec\u002Fspecs\u002F{domain}\u002Fspec.md`\n\n### SDD Cycle Complete\nThe change has been fully planned, implemented, verified, and archived.\nReady for the next change.\n```\n\n## Rules\n\n- NEVER archive a change that has CRITICAL issues in its verification report\n- ALWAYS sync delta specs BEFORE moving to archive\n- When merging into existing specs, PRESERVE requirements not mentioned in the delta\n- Use ISO date format (YYYY-MM-DD) for archive folder prefix\n- If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation\n- The archive is an AUDIT TRAIL — never delete or modify archived changes\n- If `openspec\u002Fchanges\u002Farchive\u002F` doesn't exist, create it\n- Apply any `rules.archive` from `openspec\u002Fconfig.yaml`\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-archive","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-archive",{"tool":41,"command":42},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill sdd-archive",{"tool":44,"command":45},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill sdd-archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-archive\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",[],[]]