[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWB4DNHJFWX32AKXCGSPJA":3,"skill-same:01M6KWB4DNHJFWX32AKXCGSPJA":73},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6KWB4DNHJFWX32AKXCGSPJA","github-cd-automation",null,"Structured workflow for designing GitHub Actions continuous deployment for HypermediaEngine. Covers release workflows triggered by tags or manual dispatch, environments and environment secrets, approval gates, NuGet package deployment, GitHub Releases with changelogs, and separating preview vs production deployment flows. Invoked by the devops-engineer agent when release\u002Fdeploy workflows must be created or updated.","rafsanulhasan\u002FHypermediaEngine","rafsanulhasan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2341142?v=4","01M6KW2HWPTZWK051N7B0HTBVG","Rafsanul Hasan","01M6KW2J0N3613382MF5DRN79H",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgithub-cd-automation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"automation","github cd automation","cd","github","engineer","nuget package deployment","for","environments","flows","continuous deployment","preview","releases","environment","secrets","github actions","actions","release","deployment","workflows","workflow","2026-11-10 10:12:30",false,"---\nname: github-cd-automation\ndescription: Structured workflow for designing GitHub Actions continuous deployment for HypermediaEngine. Covers release workflows triggered by tags or manual dispatch, environments and environment secrets, approval gates, NuGet package deployment, GitHub Releases with changelogs, and separating preview vs production deployment flows. Invoked by the devops-engineer agent when release\u002Fdeploy workflows must be created or updated.\n---\n\n# GitHub CD Automation\n\nYou are executing the `github-cd-automation` skill on behalf of the devops-engineer agent. Your job is to produce or modify release workflow files that publish HypermediaEngine packages and create GitHub Releases — with safeguards (approval, environment-scoped secrets) that distinguish preview from production flows.\n\n## When to Invoke\n\n- A new release workflow must be created (e.g., `release.yml`, `preview.yml`)\n- An existing release workflow needs new steps (changelog generation, GitHub Release creation, attestation)\n- Approval gates or environments must be added before NuGet publishing\n- Migrating from manual `dotnet nuget push` to fully automated tag-driven deploys\n\n## Prerequisites\n\n- A working CI workflow already validates every push (see `github-ci-automation`)\n- NuGet API key stored as an environment-scoped secret (e.g., `NUGET_API_KEY` in the `nuget-org-production` environment)\n- Repository configured with GitHub Environments (`Settings → Environments`) for at least: `nuget-preview`, `nuget-production`\n- Required reviewers configured on the `nuget-production` environment\n- Tag convention defined: `vMAJOR.MINOR.PATCH` for stable, `vMAJOR.MINOR.PATCH-preview.N` for previews\n\n## Workflow Structure — Production Release\n\n```yaml\nname: Release\n\non:\n  push:\n    tags: ['v[0-9]+.[0-9]+.[0-9]+']\n  workflow_dispatch:\n    inputs:\n      version:\n        description: 'Version to release (e.g. 1.4.0)'\n        required: true\n\npermissions:\n  contents: write   # required to create a GitHub Release\n  id-token: write   # for OIDC if used\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - uses: actions\u002Fsetup-dotnet@v4\n        with:\n          dotnet-version: '9.0.x'\n      - run: dotnet restore\n      - run: dotnet build --configuration Release --no-restore\n      - run: dotnet test --configuration Release --no-build\n      - name: Pack\n        run: dotnet pack --configuration Release --no-build --output .\u002Fartifacts --include-symbols -p:SymbolPackageFormat=snupkg\n      - uses: actions\u002Fupload-artifact@v4\n        with:\n          name: nupkg\n          path: .\u002Fartifacts\u002F*.*nupkg\n\n  publish:\n    needs: build\n    runs-on: ubuntu-latest\n    environment:\n      name: nuget-production\n      url: https:\u002F\u002Fwww.nuget.org\u002Fpackages\u002FHypermediaEngine\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: nupkg\n          path: .\u002Fartifacts\n      - name: Push to nuget.org\n        run: |\n          dotnet nuget push .\u002Fartifacts\u002F*.nupkg \\\n            --api-key ${{ secrets.NUGET_API_KEY }} \\\n            --source https:\u002F\u002Fapi.nuget.org\u002Fv3\u002Findex.json \\\n            --skip-duplicate\n\n  release:\n    needs: publish\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - name: Generate changelog\n        id: changelog\n        run: |\n          PREV_TAG=$(git describe --tags --abbrev=0 HEAD^ 2>\u002Fdev\u002Fnull || echo \"\")\n          if [ -n \"$PREV_TAG\" ]; then\n            git log \"$PREV_TAG..HEAD\" --pretty=format:\"- %s (%h)\" > CHANGELOG.md\n          else\n            git log --pretty=format:\"- %s (%h)\" > CHANGELOG.md\n          fi\n      - name: Create GitHub Release\n        uses: softprops\u002Faction-gh-release@v2\n        with:\n          tag_name: ${{ github.ref_name }}\n          name: ${{ github.ref_name }}\n          body_path: CHANGELOG.md\n          prerelease: false\n```\n\n## Workflow Structure — Preview Release\n\nDifferences from production:\n\n- Trigger on tag pattern `v[0-9]+.[0-9]+.[0-9]+-(preview|alpha|beta|rc).*` or `workflow_dispatch`\n- Use `environment: nuget-preview` (no required reviewers, or lighter approval)\n- `prerelease: true` on the GitHub Release\n- Optionally publish to a private feed first, then nuget.org\n\n## Workflow\n\n### Phase 0 — Context Load\n\n1. Read `CLAUDE.md` for project conventions.\n2. List `.github\u002Fworkflows\u002F` to see existing workflows.\n3. Confirm which Environments exist in `Settings → Environments` (ask the user if uncertain).\n4. Read the `nuget-package-deployment` skill — your `publish` job must satisfy its protocol.\n\n### Phase 1 — Triggers\n\nUse tags for the primary path:\n- Stable: `v[0-9]+.[0-9]+.[0-9]+`\n- Preview: `v[0-9]+.[0-9]+.[0-9]+-*`\n\nAlways also provide `workflow_dispatch` for manual republish\u002Fretry.\n\n### Phase 2 — Environments and Approvals\n\nEach `publish` job must declare `environment:`. This:\n- Scopes the `NUGET_API_KEY` secret to that environment only\n- Enforces required reviewers configured in the environment settings\n- Records the deployment on the repo's Deployments page\n\nStable production releases require human approval. Previews can be auto-approved.\n\n### Phase 3 — Build → Publish → Release Job Chain\n\nUse `needs:` to enforce ordering. Never combine build and publish in one job — the artifact must be the same artifact that was tested.\n\n### Phase 4 — Changelog Generation\n\nGenerate a changelog from `git log` between the previous tag and the current tag. For richer notes, integrate `release-drafter` or `git-cliff` — both available as GitHub Actions.\n\n### Phase 5 — GitHub Release Creation\n\nUse `softprops\u002Faction-gh-release@v2`:\n- Stable: `prerelease: false`\n- Preview: `prerelease: true`\n- Attach the `.nupkg` and `.snupkg` artifacts if useful for offline consumers\n\n### Phase 6 — Verification\n\nAdd a post-publish smoke step (in production releases):\n- `dotnet add package \u003CPackageId> --version ${VERSION}` in a fresh folder\n- Assert exit code zero\n\n## Stable vs Preview Flow Summary\n\n| Aspect | Stable (`release.yml`) | Preview (`preview.yml`) |\n|--------|------------------------|-------------------------|\n| Trigger | Tag `v1.4.0` | Tag `v1.5.0-preview.2` |\n| Environment | `nuget-production` (required reviewers) | `nuget-preview` (auto-approve) |\n| GitHub Release `prerelease:` | `false` | `true` |\n| Changelog scope | Since last stable tag | Since last preview tag |\n| Audience | Default consumers | Opt-in via `--prerelease` |\n\n## Common Pitfalls\n\n- **No environment on publish job**: secrets become repo-wide; required reviewers don't apply.\n- **Publishing untested artifacts**: rebuild in the publish job loses traceability. Always download the build artifact.\n- **Missing `contents: write`**: `action-gh-release` fails silently with permission denied.\n- **Tag-pattern overlap**: a single workflow trying to handle both stable and preview tags often leaks preview secrets. Separate workflows are safer.\n- **Forgotten `--skip-duplicate`**: retry runs fail when re-pushing matching `.snupkg`.\n- **Changelog includes merge commits noise**: filter `--no-merges` or use a curated tool.\n- **No rollback plan**: document the unlist procedure on nuget.org in the workflow README.\n\n## Output\n\nReturn to the calling agent:\n- Workflow files created or modified\n- Environments and secrets required\n- Approval gate configuration steps for the maintainer\n- Tag patterns that trigger each workflow\n- Verification step status\n","# GitHub CD Automation\n\nYou are executing the `github-cd-automation` skill on behalf of the devops-engineer agent. Your job is to produce or modify release workflow files that publish HypermediaEngine packages and create GitHub Releases — with safeguards (approval, environment-scoped secrets) that distinguish preview from production flows.\n\n## When to Invoke\n\n- A new release workflow must be created (e.g., `release.yml`, `preview.yml`)\n- An existing release workflow needs new steps (changelog generation, GitHub Release creation, attestation)\n- Approval gates or environments must be added before NuGet publishing\n- Migrating from manual `dotnet nuget push` to fully automated tag-driven deploys\n\n## Prerequisites\n\n- A working CI workflow already validates every push (see `github-ci-automation`)\n- NuGet API key stored as an environment-scoped secret (e.g., `NUGET_API_KEY` in the `nuget-org-production` environment)\n- Repository configured with GitHub Environments (`Settings → Environments`) for at least: `nuget-preview`, `nuget-production`\n- Required reviewers configured on the `nuget-production` environment\n- Tag convention defined: `vMAJOR.MINOR.PATCH` for stable, `vMAJOR.MINOR.PATCH-preview.N` for previews\n\n## Workflow Structure — Production Release\n\n```yaml\nname: Release\n\non:\n  push:\n    tags: ['v[0-9]+.[0-9]+.[0-9]+']\n  workflow_dispatch:\n    inputs:\n      version:\n        description: 'Version to release (e.g. 1.4.0)'\n        required: true\n\npermissions:\n  contents: write   # required to create a GitHub Release\n  id-token: write   # for OIDC if used\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - uses: actions\u002Fsetup-dotnet@v4\n        with:\n          dotnet-version: '9.0.x'\n      - run: dotnet restore\n      - run: dotnet build --configuration Release --no-restore\n      - run: dotnet test --configuration Release --no-build\n      - name: Pack\n        run: dotnet pack --configuration Release --no-build --output .\u002Fartifacts --include-symbols -p:SymbolPackageFormat=snupkg\n      - uses: actions\u002Fupload-artifact@v4\n        with:\n          name: nupkg\n          path: .\u002Fartifacts\u002F*.*nupkg\n\n  publish:\n    needs: build\n    runs-on: ubuntu-latest\n    environment:\n      name: nuget-production\n      url: https:\u002F\u002Fwww.nuget.org\u002Fpackages\u002FHypermediaEngine\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: nupkg\n          path: .\u002Fartifacts\n      - name: Push to nuget.org\n        run: |\n          dotnet nuget push .\u002Fartifacts\u002F*.nupkg \\\n            --api-key ${{ secrets.NUGET_API_KEY }} \\\n            --source https:\u002F\u002Fapi.nuget.org\u002Fv3\u002Findex.json \\\n            --skip-duplicate\n\n  release:\n    needs: publish\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - name: Generate changelog\n        id: changelog\n        run: |\n          PREV_TAG=$(git describe --tags --abbrev=0 HEAD^ 2>\u002Fdev\u002Fnull || echo \"\")\n          if [ -n \"$PREV_TAG\" ]; then\n            git log \"$PREV_TAG..HEAD\" --pretty=format:\"- %s (%h)\" > CHANGELOG.md\n          else\n            git log --pretty=format:\"- %s (%h)\" > CHANGELOG.md\n          fi\n      - name: Create GitHub Release\n        uses: softprops\u002Faction-gh-release@v2\n        with:\n          tag_name: ${{ github.ref_name }}\n          name: ${{ github.ref_name }}\n          body_path: CHANGELOG.md\n          prerelease: false\n```\n\n## Workflow Structure — Preview Release\n\nDifferences from production:\n\n- Trigger on tag pattern `v[0-9]+.[0-9]+.[0-9]+-(preview|alpha|beta|rc).*` or `workflow_dispatch`\n- Use `environment: nuget-preview` (no required reviewers, or lighter approval)\n- `prerelease: true` on the GitHub Release\n- Optionally publish to a private feed first, then nuget.org\n\n## Workflow\n\n### Phase 0 — Context Load\n\n1. Read `CLAUDE.md` for project conventions.\n2. List `.github\u002Fworkflows\u002F` to see existing workflows.\n3. Confirm which Environments exist in `Settings → Environments` (ask the user if uncertain).\n4. Read the `nuget-package-deployment` skill — your `publish` job must satisfy its protocol.\n\n### Phase 1 — Triggers\n\nUse tags for the primary path:\n- Stable: `v[0-9]+.[0-9]+.[0-9]+`\n- Preview: `v[0-9]+.[0-9]+.[0-9]+-*`\n\nAlways also provide `workflow_dispatch` for manual republish\u002Fretry.\n\n### Phase 2 — Environments and Approvals\n\nEach `publish` job must declare `environment:`. This:\n- Scopes the `NUGET_API_KEY` secret to that environment only\n- Enforces required reviewers configured in the environment settings\n- Records the deployment on the repo's Deployments page\n\nStable production releases require human approval. Previews can be auto-approved.\n\n### Phase 3 — Build → Publish → Release Job Chain\n\nUse `needs:` to enforce ordering. Never combine build and publish in one job — the artifact must be the same artifact that was tested.\n\n### Phase 4 — Changelog Generation\n\nGenerate a changelog from `git log` between the previous tag and the current tag. For richer notes, integrate `release-drafter` or `git-cliff` — both available as GitHub Actions.\n\n### Phase 5 — GitHub Release Creation\n\nUse `softprops\u002Faction-gh-release@v2`:\n- Stable: `prerelease: false`\n- Preview: `prerelease: true`\n- Attach the `.nupkg` and `.snupkg` artifacts if useful for offline consumers\n\n### Phase 6 — Verification\n\nAdd a post-publish smoke step (in production releases):\n- `dotnet add package \u003CPackageId> --version ${VERSION}` in a fresh folder\n- Assert exit code zero\n\n## Stable vs Preview Flow Summary\n\n| Aspect | Stable (`release.yml`) | Preview (`preview.yml`) |\n|--------|------------------------|-------------------------|\n| Trigger | Tag `v1.4.0` | Tag `v1.5.0-preview.2` |\n| Environment | `nuget-production` (required reviewers) | `nuget-preview` (auto-approve) |\n| GitHub Release `prerelease:` | `false` | `true` |\n| Changelog scope | Since last stable tag | Since last preview tag |\n| Audience | Default consumers | Opt-in via `--prerelease` |\n\n## Common Pitfalls\n\n- **No environment on publish job**: secrets become repo-wide; required reviewers don't apply.\n- **Publishing untested artifacts**: rebuild in the publish job loses traceability. Always download the build artifact.\n- **Missing `contents: write`**: `action-gh-release` fails silently with permission denied.\n- **Tag-pattern overlap**: a single workflow trying to handle both stable and preview tags often leaks preview secrets. Separate workflows are safer.\n- **Forgotten `--skip-duplicate`**: retry runs fail when re-pushing matching `.snupkg`.\n- **Changelog includes merge commits noise**: filter `--no-merges` or use a curated tool.\n- **No rollback plan**: document the unlist procedure on nuget.org in the workflow README.\n\n## Output\n\nReturn to the calling agent:\n- Workflow files created or modified\n- Environments and secrets required\n- Approval gate configuration steps for the maintainer\n- Tag patterns that trigger each workflow\n- Verification step status\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".github\u002Fskills\u002Fgithub-cd-automation","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine","https:\u002F\u002Fgithub.com\u002Frafsanulhasan","\r\n    MCSD || A-CSD || Software Architect\r\n\r\n","2026-06-06 07:47:06",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill github-cd-automation",{"tool":65,"command":66},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill github-cd-automation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill github-cd-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgithub-cd-automation\u002FSKILL.md",true,[],[74,102,121,140,169,190],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":83,"publishedAt":47},"01M6KWEJD606FG3DBBRM0W4DKW","write-tests","Test implementation skill for HypermediaEngine. Takes a confirmed test plan from design-test-cases and produces compilable, runnable xUnit tests following project conventions. Validates coverage quality through mutation testing. Invoked by the sqa-engineer agent after the test plan is approved.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,31,99,100,101,33],"write tests","write","tests","testing","design","test","project conventions","test plan","Bash","plan","quality","xunit","read","edit","coverage","mutation testing","project","mutation",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":47},"01M6KWEF2XQ00C1Y6QCK7YHZ1H","write-documentation","Structured documentation writing workflow for HypermediaEngine. Writes or updates README.md files at the repo root and in each project directory (src\u002F, tests\u002F, samples\u002F, etc.) based on current implementation, ADRs, and architecture decisions.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-documentation\u002FSKILL.md",[],[109,85,110,111,112,46,113,92,114,115,116,117,96,97,118,100,86,119,120,33],"documentation","write documentation","writing","directory","architecture","src","repo","decisions","README","files","updates","at",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":47},"01M6KWEBDXTXAVPQ3BHS3YYYNT","write-adr","Writes a numbered Architecture Decision Record (ADR) for a significant architectural choice in the HypermediaEngine project. Invoked by the software-architect agent whenever a consequential design decision is made or ratified. Saves the ADR to docs\u002Farchitecture\u002Fdecisions\u002F.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-adr\u002FSKILL.md",[],[128,85,129,88,130,113,131,132,133,134,116,96,135,136,100,137,138,33,139],"adr","write adr","docs","architect","decision","choice","grep","architecture decision record","record","software","opus","architecture decision",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":47},"01M6KWE76TM3QHGQ08PEB3KY6D","tunit-playwright-ui-testing","Comprehensive guidance for writing coded end-to-end UI tests in C# using TUnit.Playwright. Tests inherit from PageTest — the base class manages all browser lifecycle. Covers NuGet setup, PageTest inheritance, Page Object Model, browser configuration, parallelism limiting, and CI integration. Based on the official TUnit docs at https:\u002F\u002Ftunit.dev\u002Fdocs\u002Fexamples\u002Fplaywright.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftunit-playwright-ui-testing\u002FSKILL.md",[146,147],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[87,153,154,155,156,157,158,111,159,160,161,162,163,164,165,166,86,167,168,33],"playwright","ui","playwright ui testing","ui testing","tunit","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":47},"01M6KWE44A738GDK65QS02XJBG","triage","Task classification, decomposition, dependency mapping, and routing skill. Invoked by the triage-agent to break any user request into discrete, independently-routable work items with assigned priorities and agent chains.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[175],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[171,177,178,179,180,181,182,183,184,185,186,187,188,189],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":47},"01M6KWDZ3W9ZKPR7FTTTSX8H2K","system-design","Expert system design skill. Use PROACTIVELY to design systems, review architectures, and assist software engineers in learning design principles and implementing them in the code with design patterns.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsystem-design\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},[88,201,202,203,204,205,206,134,96,207,208,209,210,211,212,137,213,214,187,215],"system","system design","web","design systems","learning","haiku","use","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]