[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T3DM0V1BKDYP4Z8MRHMPH":3,"skill-same:01M77T3DM0V1BKDYP4Z8MRHMPH":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},"01M77T3DM0V1BKDYP4Z8MRHMPH","sdd-tasks",null,"Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.","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-tasks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdd-tasks\ndescription: \"Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.\"\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-tasks` 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 creating the TASK BREAKDOWN. You take the proposal, specs, and design, then produce a `tasks.md` with concrete, actionable implementation steps organized by phase.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n- Delivery strategy (`ask-on-risk | auto-chain | single-pr | exception-ok`)\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` (required), `sdd\u002F{change-name}\u002Fspec` (required), `sdd\u002F{change-name}\u002Fdesign` (required). Save as `sdd\u002F{change-name}\u002Ftasks`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write `tasks.md` to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.\n- **none**: Return result only. Never create or modify project files.\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: Analyze the Design\n\nFrom the design document, identify:\n- All files that need to be created\u002Fmodified\u002Fdeleted\n- The dependency order (what must come first)\n- Testing requirements per component\n\n### Step 3: Write tasks.md\n\n**IF mode is `openspec` or `hybrid`:** Create the task file:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n├── proposal.md\n├── specs\u002F\n├── design.md\n└── tasks.md               ← You create this\n```\n\n**IF mode is `engram` or `none`:** Do NOT create any `openspec\u002F` directories or files. Compose the tasks content in memory — you will persist it in Step 4.\n\n#### Task File Format\n\n```markdown\n# Tasks: {Change Title}\n\n## Review Workload Forecast\n\n| Field | Value |\n|-------|-------|\n| Estimated changed lines | \u003Crough estimate or range> |\n| 400-line budget risk | Low \u002F Medium \u002F High |\n| Chained PRs recommended | Yes \u002F No |\n| Suggested split | \u003Csingle PR or PR 1 → PR 2 → PR 3> |\n| Delivery strategy | \u003Cask-on-risk \u002F auto-chain \u002F single-pr \u002F exception-ok> |\n| Chain strategy | \u003Cstacked-to-main \u002F feature-branch-chain \u002F size-exception \u002F pending> |\n\nDecision needed before apply: \u003CYes|No>\nChained PRs recommended: \u003CYes|No>\nChain strategy: \u003Cstacked-to-main|feature-branch-chain|size-exception|pending>\n400-line budget risk: \u003CLow|Medium|High>\n\n### Suggested Work Units\n\n| Unit | Goal | Likely PR | Notes |\n|------|------|-----------|-------|\n| 1 | \u003Cstandalone deliverable> | PR 1 | \u003Cbase branch; tests\u002Fdocs included> |\n| 2 | \u003Cstandalone deliverable> | PR 2 | \u003Cimmediate parent\u002Fbase branch boundary; depends on PR 1 or independent> |\n\n## Phase 1: {Phase Name} (e.g., Infrastructure \u002F Foundation)\n\n- [ ] 1.1 {Concrete action — what file, what change}\n- [ ] 1.2 {Concrete action}\n- [ ] 1.3 {Concrete action}\n\n## Phase 2: {Phase Name} (e.g., Core Implementation)\n\n- [ ] 2.1 {Concrete action}\n- [ ] 2.2 {Concrete action}\n- [ ] 2.3 {Concrete action}\n- [ ] 2.4 {Concrete action}\n\n## Phase 3: {Phase Name} (e.g., Testing \u002F Verification)\n\n- [ ] 3.1 {Write tests for ...}\n- [ ] 3.2 {Write tests for ...}\n- [ ] 3.3 {Verify integration between ...}\n\n## Phase 4: {Phase Name} (e.g., Cleanup \u002F Documentation)\n\n- [ ] 4.1 {Update docs\u002Fcomments}\n- [ ] 4.2 {Remove temporary code}\n```\n\n### Task Writing Rules\n\nEach task MUST be:\n\n| Criteria | Example ✅ | Anti-example ❌ |\n|----------|-----------|----------------|\n| **Specific** | \"Create `internal\u002Fauth\u002Fmiddleware.go` with JWT validation\" | \"Add auth\" |\n| **Actionable** | \"Add `ValidateToken()` method to `AuthService`\" | \"Handle tokens\" |\n| **Verifiable** | \"Test: `POST \u002Flogin` returns 401 without token\" | \"Make sure it works\" |\n| **Small** | One file or one logical unit of work | \"Implement the feature\" |\n\n### Review Workload Forecast Rules\n\nBefore finalizing tasks, estimate whether implementation is likely to exceed the **400 changed-line review budget** (`additions + deletions`). This is a planning guard, not an exact diff count.\n\nUse available signals: number of files, phases, integration points, tests, docs, generated artifacts, migrations, and how many concerns the change crosses.\n\nIf the estimate is **High** or likely above 400 lines:\n\n1. Mark `Chained PRs recommended` as `Yes`.\n2. Split tasks into **work units** that can become chained or stacked PRs.\n3. Each suggested PR must have a clear start, clear finish, verification, and autonomous scope.\n4. **Ask the user which chain strategy to use** (this is a team decision):\n   - **Stacked PRs to main** — each PR merges to main in order. Fast iteration, fix on the go. Best for speed-first teams and independent slices.\n   - **Feature Branch Chain** — the feature\u002Ftracker branch accumulates the final integration; PR #1 targets the tracker branch, later PRs target the immediate previous PR branch so each child diff stays focused. Only the tracker merges to main. Best for rollback control and coordinated releases.\n   - **size:exception** — keep it as a single PR with maintainer approval. Best for generated code, migrations, or vendor diffs.\n5. Cache the user's choice and set `Decision needed before apply` from delivery strategy:\n   - `ask-on-risk`: `Yes` — orchestrator asks before apply.\n   - `auto-chain`: `No` — orchestrator proceeds with the first slice using the chosen chain strategy.\n   - `single-pr`: `Yes` — orchestrator must require `size:exception` before apply.\n   - `exception-ok`: `No` — maintainer has accepted `size:exception`.\n\nDo not bury this in prose. Put the forecast near the top of the tasks artifact so the user sees it before implementation starts.\n\nThe forecast MUST include these exact plain-text lines so downstream guards can match them literally:\n\n```text\nDecision needed before apply: Yes|No\nChained PRs recommended: Yes|No\nChain strategy: stacked-to-main|feature-branch-chain|size-exception|pending\n400-line budget risk: Low|Medium|High\n```\n\nYou may keep the table for readability, but the plain-text lines are the guard contract.\n\nFor `feature-branch-chain`, suggested work units SHOULD name the intended base boundary: PR #1 base = feature\u002Ftracker branch; PR #2 base = PR #1 branch; PR #3 base = PR #2 branch. If a child PR would show previous PR changes, the base is wrong and must be retargeted\u002Frebased before review.\n\n### Phase Organization Guidelines\n\n```\nPhase 1: Foundation \u002F Infrastructure\n  └─ New types, interfaces, database changes, config\n  └─ Things other tasks depend on\n\nPhase 2: Core Implementation\n  └─ Main logic, business rules, core behavior\n  └─ The meat of the change\n\nPhase 3: Integration \u002F Wiring\n  └─ Connect components, routes, UI wiring\n  └─ Make everything work together\n\nPhase 4: Testing\n  └─ Unit tests, integration tests, e2e tests\n  └─ Verify against spec scenarios\n\nPhase 5: Cleanup (if needed)\n  └─ Documentation, remove dead code, polish\n```\n\n### Step 4: Persist Artifact\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `tasks`\n- topic_key: `sdd\u002F{change-name}\u002Ftasks`\n- type: `architecture`\n\n### Step 5: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Tasks Created\n\n**Change**: {change-name}\n**Location**: `openspec\u002Fchanges\u002F{change-name}\u002Ftasks.md` (openspec\u002Fhybrid) | Engram `sdd\u002F{change-name}\u002Ftasks` (engram) | inline (none)\n\n### Breakdown\n| Phase | Tasks | Focus |\n|-------|-------|-------|\n| Phase 1 | {N} | {Phase name} |\n| Phase 2 | {N} | {Phase name} |\n| Phase 3 | {N} | {Phase name} |\n| Total | {N} | |\n\n### Implementation Order\n{Brief description of the recommended order and why}\n\n### Review Workload Forecast\n- Estimated changed lines: {estimate or range}\n- 400-line budget risk: {Low | Medium | High}\n- Chained PRs recommended: {Yes | No}\n- Delivery strategy: {ask-on-risk | auto-chain | single-pr | exception-ok}\n- Decision needed before apply: {Yes | No}\n- Suggested work-unit PR split: {brief list or \"Not needed\"}\n\n### Next Step\n{Ready for implementation (sdd-apply) OR ask the user whether to use chained PRs before sdd-apply.}\n```\n\n## Rules\n\n- ALWAYS reference concrete file paths in tasks\n- Tasks MUST be ordered by dependency — Phase 1 tasks shouldn't depend on Phase 2\n- Testing tasks should reference specific scenarios from the specs\n- Each task should be completable in ONE session (if a task feels too big, split it)\n- Use hierarchical numbering: 1.1, 1.2, 2.1, 2.2, etc.\n- NEVER include vague tasks like \"implement feature\" or \"add tests\"\n- Apply any `rules.tasks` from `openspec\u002Fconfig.yaml`\n- If the project uses TDD, integrate test-first tasks: RED task (write failing test) → GREEN task (make it pass) → REFACTOR task (clean up)\n- **Size budget**: Tasks artifact MUST be under 530 words. Each task: 1-2 lines max. Use checklist format, not paragraphs.\n- **Review workload guard**: ALWAYS include the Review Workload Forecast. If likely above 400 changed lines, recommend chained PRs and honor the received delivery strategy for whether a decision\u002Fexception is needed before apply.\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-tasks` 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 creating the TASK BREAKDOWN. You take the proposal, specs, and design, then produce a `tasks.md` with concrete, actionable implementation steps organized by phase.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n- Delivery strategy (`ask-on-risk | auto-chain | single-pr | exception-ok`)\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` (required), `sdd\u002F{change-name}\u002Fspec` (required), `sdd\u002F{change-name}\u002Fdesign` (required). Save as `sdd\u002F{change-name}\u002Ftasks`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write `tasks.md` to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.\n- **none**: Return result only. Never create or modify project files.\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: Analyze the Design\n\nFrom the design document, identify:\n- All files that need to be created\u002Fmodified\u002Fdeleted\n- The dependency order (what must come first)\n- Testing requirements per component\n\n### Step 3: Write tasks.md\n\n**IF mode is `openspec` or `hybrid`:** Create the task file:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n├── proposal.md\n├── specs\u002F\n├── design.md\n└── tasks.md               ← You create this\n```\n\n**IF mode is `engram` or `none`:** Do NOT create any `openspec\u002F` directories or files. Compose the tasks content in memory — you will persist it in Step 4.\n\n#### Task File Format\n\n```markdown\n# Tasks: {Change Title}\n\n## Review Workload Forecast\n\n| Field | Value |\n|-------|-------|\n| Estimated changed lines | \u003Crough estimate or range> |\n| 400-line budget risk | Low \u002F Medium \u002F High |\n| Chained PRs recommended | Yes \u002F No |\n| Suggested split | \u003Csingle PR or PR 1 → PR 2 → PR 3> |\n| Delivery strategy | \u003Cask-on-risk \u002F auto-chain \u002F single-pr \u002F exception-ok> |\n| Chain strategy | \u003Cstacked-to-main \u002F feature-branch-chain \u002F size-exception \u002F pending> |\n\nDecision needed before apply: \u003CYes|No>\nChained PRs recommended: \u003CYes|No>\nChain strategy: \u003Cstacked-to-main|feature-branch-chain|size-exception|pending>\n400-line budget risk: \u003CLow|Medium|High>\n\n### Suggested Work Units\n\n| Unit | Goal | Likely PR | Notes |\n|------|------|-----------|-------|\n| 1 | \u003Cstandalone deliverable> | PR 1 | \u003Cbase branch; tests\u002Fdocs included> |\n| 2 | \u003Cstandalone deliverable> | PR 2 | \u003Cimmediate parent\u002Fbase branch boundary; depends on PR 1 or independent> |\n\n## Phase 1: {Phase Name} (e.g., Infrastructure \u002F Foundation)\n\n- [ ] 1.1 {Concrete action — what file, what change}\n- [ ] 1.2 {Concrete action}\n- [ ] 1.3 {Concrete action}\n\n## Phase 2: {Phase Name} (e.g., Core Implementation)\n\n- [ ] 2.1 {Concrete action}\n- [ ] 2.2 {Concrete action}\n- [ ] 2.3 {Concrete action}\n- [ ] 2.4 {Concrete action}\n\n## Phase 3: {Phase Name} (e.g., Testing \u002F Verification)\n\n- [ ] 3.1 {Write tests for ...}\n- [ ] 3.2 {Write tests for ...}\n- [ ] 3.3 {Verify integration between ...}\n\n## Phase 4: {Phase Name} (e.g., Cleanup \u002F Documentation)\n\n- [ ] 4.1 {Update docs\u002Fcomments}\n- [ ] 4.2 {Remove temporary code}\n```\n\n### Task Writing Rules\n\nEach task MUST be:\n\n| Criteria | Example ✅ | Anti-example ❌ |\n|----------|-----------|----------------|\n| **Specific** | \"Create `internal\u002Fauth\u002Fmiddleware.go` with JWT validation\" | \"Add auth\" |\n| **Actionable** | \"Add `ValidateToken()` method to `AuthService`\" | \"Handle tokens\" |\n| **Verifiable** | \"Test: `POST \u002Flogin` returns 401 without token\" | \"Make sure it works\" |\n| **Small** | One file or one logical unit of work | \"Implement the feature\" |\n\n### Review Workload Forecast Rules\n\nBefore finalizing tasks, estimate whether implementation is likely to exceed the **400 changed-line review budget** (`additions + deletions`). This is a planning guard, not an exact diff count.\n\nUse available signals: number of files, phases, integration points, tests, docs, generated artifacts, migrations, and how many concerns the change crosses.\n\nIf the estimate is **High** or likely above 400 lines:\n\n1. Mark `Chained PRs recommended` as `Yes`.\n2. Split tasks into **work units** that can become chained or stacked PRs.\n3. Each suggested PR must have a clear start, clear finish, verification, and autonomous scope.\n4. **Ask the user which chain strategy to use** (this is a team decision):\n   - **Stacked PRs to main** — each PR merges to main in order. Fast iteration, fix on the go. Best for speed-first teams and independent slices.\n   - **Feature Branch Chain** — the feature\u002Ftracker branch accumulates the final integration; PR #1 targets the tracker branch, later PRs target the immediate previous PR branch so each child diff stays focused. Only the tracker merges to main. Best for rollback control and coordinated releases.\n   - **size:exception** — keep it as a single PR with maintainer approval. Best for generated code, migrations, or vendor diffs.\n5. Cache the user's choice and set `Decision needed before apply` from delivery strategy:\n   - `ask-on-risk`: `Yes` — orchestrator asks before apply.\n   - `auto-chain`: `No` — orchestrator proceeds with the first slice using the chosen chain strategy.\n   - `single-pr`: `Yes` — orchestrator must require `size:exception` before apply.\n   - `exception-ok`: `No` — maintainer has accepted `size:exception`.\n\nDo not bury this in prose. Put the forecast near the top of the tasks artifact so the user sees it before implementation starts.\n\nThe forecast MUST include these exact plain-text lines so downstream guards can match them literally:\n\n```text\nDecision needed before apply: Yes|No\nChained PRs recommended: Yes|No\nChain strategy: stacked-to-main|feature-branch-chain|size-exception|pending\n400-line budget risk: Low|Medium|High\n```\n\nYou may keep the table for readability, but the plain-text lines are the guard contract.\n\nFor `feature-branch-chain`, suggested work units SHOULD name the intended base boundary: PR #1 base = feature\u002Ftracker branch; PR #2 base = PR #1 branch; PR #3 base = PR #2 branch. If a child PR would show previous PR changes, the base is wrong and must be retargeted\u002Frebased before review.\n\n### Phase Organization Guidelines\n\n```\nPhase 1: Foundation \u002F Infrastructure\n  └─ New types, interfaces, database changes, config\n  └─ Things other tasks depend on\n\nPhase 2: Core Implementation\n  └─ Main logic, business rules, core behavior\n  └─ The meat of the change\n\nPhase 3: Integration \u002F Wiring\n  └─ Connect components, routes, UI wiring\n  └─ Make everything work together\n\nPhase 4: Testing\n  └─ Unit tests, integration tests, e2e tests\n  └─ Verify against spec scenarios\n\nPhase 5: Cleanup (if needed)\n  └─ Documentation, remove dead code, polish\n```\n\n### Step 4: Persist Artifact\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `tasks`\n- topic_key: `sdd\u002F{change-name}\u002Ftasks`\n- type: `architecture`\n\n### Step 5: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Tasks Created\n\n**Change**: {change-name}\n**Location**: `openspec\u002Fchanges\u002F{change-name}\u002Ftasks.md` (openspec\u002Fhybrid) | Engram `sdd\u002F{change-name}\u002Ftasks` (engram) | inline (none)\n\n### Breakdown\n| Phase | Tasks | Focus |\n|-------|-------|-------|\n| Phase 1 | {N} | {Phase name} |\n| Phase 2 | {N} | {Phase name} |\n| Phase 3 | {N} | {Phase name} |\n| Total | {N} | |\n\n### Implementation Order\n{Brief description of the recommended order and why}\n\n### Review Workload Forecast\n- Estimated changed lines: {estimate or range}\n- 400-line budget risk: {Low | Medium | High}\n- Chained PRs recommended: {Yes | No}\n- Delivery strategy: {ask-on-risk | auto-chain | single-pr | exception-ok}\n- Decision needed before apply: {Yes | No}\n- Suggested work-unit PR split: {brief list or \"Not needed\"}\n\n### Next Step\n{Ready for implementation (sdd-apply) OR ask the user whether to use chained PRs before sdd-apply.}\n```\n\n## Rules\n\n- ALWAYS reference concrete file paths in tasks\n- Tasks MUST be ordered by dependency — Phase 1 tasks shouldn't depend on Phase 2\n- Testing tasks should reference specific scenarios from the specs\n- Each task should be completable in ONE session (if a task feels too big, split it)\n- Use hierarchical numbering: 1.1, 1.2, 2.1, 2.2, etc.\n- NEVER include vague tasks like \"implement feature\" or \"add tests\"\n- Apply any `rules.tasks` from `openspec\u002Fconfig.yaml`\n- If the project uses TDD, integrate test-first tasks: RED task (write failing test) → GREEN task (make it pass) → REFACTOR task (clean up)\n- **Size budget**: Tasks artifact MUST be under 530 words. Each task: 1-2 lines max. Use checklist format, not paragraphs.\n- **Review workload guard**: ALWAYS include the Review Workload Forecast. If likely above 400 changed lines, recommend chained PRs and honor the received delivery strategy for whether a decision\u002Fexception is needed before apply.\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-tasks","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-tasks",{"tool":41,"command":42},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill sdd-tasks",{"tool":44,"command":45},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill sdd-tasks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdd-tasks\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",[],[]]