[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BAAFW6F1PCVRDM4MTY31Y":3,"skill-same:01M69BAAFW6F1PCVRDM4MTY31Y":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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M69BAAFW6F1PCVRDM4MTY31Y","release-package",null,"Prepare a release of @coreai-ds\u002Freact-components: reconcile the changelog, bump the version, validate the package, and open a release PR. Use when asked to release or publish the npm package.","microsoft\u002Fcoreai-design-system","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B9ED3TGFRHF93Y8JF1Y18",2,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-package\u002FSKILL.md",[],[19,20,21,22,23,24],"release package","components","react","validate","prepare","pr","2026-11-10 10:12:30",false,"---\nname: release-package\ndescription: 'Prepare a release of @coreai-ds\u002Freact-components: reconcile the changelog, bump the version, validate the package, and open a release PR. Use when asked to release or publish the npm package.'\n---\n\n# Prepare a package release PR\n\nRead [RELEASING.md](..\u002F..\u002F..\u002Fpackages\u002Freact-components\u002FRELEASING.md) first.\nThe deliverable is an open pull request against `microsoft\u002Fcoreai-design-system:main`,\nnot a local plan. Do not merge it, create tags\u002Freleases, publish locally, or change\nrepository variables, environment protections, or credentials. Once enabled, Actions\npublishes the version-changing main commit after CI succeeds and tags it `vVERSION`.\n\n1. Check the remote, worktree, GitHub account, and existing release PRs. Follow the\n   `github-accounts` skill before using `gh`. Use `arniebradfo` for this repository.\n   Preserve unrelated edits; do not include them in the release. Start from current\n   `origin\u002Fmain` on `release\u002FvVERSION`. If unrelated work prevents a clean release,\n   use a separate worktree or ask the user rather than resetting their work.\n2. Read the manifest, root lockfile, changelog, publishing workflow, Git tags, and\n   public npm version metadata. Confirm the requested version; if unspecified,\n   propose the appropriate semver increment and ask before bumping. The first public\n   release is **0.12.0**, not the manifest's historical 0.11.1 plus a patch.\n3. Establish the last released source baseline. Review every merged PR and commit\n   since it, including first-parent merges and package source differences. Reconcile\n   user-visible changes with `[Unreleased]` and give explicit consumer migrations for\n   breaking changes. No tags exist before the first public release: document that\n   limitation and review the available history rather than inventing a baseline\u002Ftag.\n   Historical 0.11.2 includes provider circular-dependency fix `567dc9a`, merged in\n   PR #9; its exact privately published source baseline is unconfirmed.\n4. Run `npm version VERSION --workspace packages\u002Freact-components --no-git-tag-version`.\n   Update the package manifest and root lockfile together. Roll `[Unreleased]` into\n   `[VERSION] - YYYY-MM-DD`, add a fresh `[Unreleased]`, and update heading anchors.\n   For 0.12.0, retain the first-public-npm-release statement and historical fixes.\n   Do not add comparison links to tags that do not exist yet.\n5. Run the release guide's local checks with existing dependencies. Install\u002Frestore\n   dependencies only if needed after a dependency change or missing-dependency error.\n   Verify an actual tarball; never ship font binaries or rely on `publishConfig` to\n   rewrite exports. Do not claim checks passed unless they ran successfully.\n6. Check release readiness without reading secret values: the repository's\n   `NPM_PUBLISH_ENABLED` variable, main review\u002FCI rules, `npm-production` main-only\n   environment, presence of the `NPM_TOKEN` secret, and Actions tag\u002Frelease permissions.\n   Missing publishing setup must be reported in the PR; never enable it yourself.\n   Distinguish a confirmed npm package 404 from an authentication\u002Fnetwork failure.\n7. Commit only release-scoped changes, including the required Copilot co-author\n   trailer, push the release branch, and use `gh pr create` targeting `main`.\n   Follow the `create-pr` skill. Include version, baseline evidence\u002Flimitations,\n   changelog reconciliation, checks and results, and publishing readiness blockers.\n   Explain that merging authorizes automatic publication when enabled. Never use\n   `--admin` or bypass checks. Report the PR URL and stop; the user reviews\u002Fmerges.\n\nFor a cold-start test, perform this same PR-opening workflow. Do not stop after\ndescribing what you would do. An incorrect test PR can be closed without publishing.\nIf blocked, report the exact blocker rather than claiming the release is ready.\n","# Prepare a package release PR\n\nRead [RELEASING.md](..\u002F..\u002F..\u002Fpackages\u002Freact-components\u002FRELEASING.md) first.\nThe deliverable is an open pull request against `microsoft\u002Fcoreai-design-system:main`,\nnot a local plan. Do not merge it, create tags\u002Freleases, publish locally, or change\nrepository variables, environment protections, or credentials. Once enabled, Actions\npublishes the version-changing main commit after CI succeeds and tags it `vVERSION`.\n\n1. Check the remote, worktree, GitHub account, and existing release PRs. Follow the\n   `github-accounts` skill before using `gh`. Use `arniebradfo` for this repository.\n   Preserve unrelated edits; do not include them in the release. Start from current\n   `origin\u002Fmain` on `release\u002FvVERSION`. If unrelated work prevents a clean release,\n   use a separate worktree or ask the user rather than resetting their work.\n2. Read the manifest, root lockfile, changelog, publishing workflow, Git tags, and\n   public npm version metadata. Confirm the requested version; if unspecified,\n   propose the appropriate semver increment and ask before bumping. The first public\n   release is **0.12.0**, not the manifest's historical 0.11.1 plus a patch.\n3. Establish the last released source baseline. Review every merged PR and commit\n   since it, including first-parent merges and package source differences. Reconcile\n   user-visible changes with `[Unreleased]` and give explicit consumer migrations for\n   breaking changes. No tags exist before the first public release: document that\n   limitation and review the available history rather than inventing a baseline\u002Ftag.\n   Historical 0.11.2 includes provider circular-dependency fix `567dc9a`, merged in\n   PR #9; its exact privately published source baseline is unconfirmed.\n4. Run `npm version VERSION --workspace packages\u002Freact-components --no-git-tag-version`.\n   Update the package manifest and root lockfile together. Roll `[Unreleased]` into\n   `[VERSION] - YYYY-MM-DD`, add a fresh `[Unreleased]`, and update heading anchors.\n   For 0.12.0, retain the first-public-npm-release statement and historical fixes.\n   Do not add comparison links to tags that do not exist yet.\n5. Run the release guide's local checks with existing dependencies. Install\u002Frestore\n   dependencies only if needed after a dependency change or missing-dependency error.\n   Verify an actual tarball; never ship font binaries or rely on `publishConfig` to\n   rewrite exports. Do not claim checks passed unless they ran successfully.\n6. Check release readiness without reading secret values: the repository's\n   `NPM_PUBLISH_ENABLED` variable, main review\u002FCI rules, `npm-production` main-only\n   environment, presence of the `NPM_TOKEN` secret, and Actions tag\u002Frelease permissions.\n   Missing publishing setup must be reported in the PR; never enable it yourself.\n   Distinguish a confirmed npm package 404 from an authentication\u002Fnetwork failure.\n7. Commit only release-scoped changes, including the required Copilot co-author\n   trailer, push the release branch, and use `gh pr create` targeting `main`.\n   Follow the `create-pr` skill. Include version, baseline evidence\u002Flimitations,\n   changelog reconciliation, checks and results, and publishing readiness blockers.\n   Explain that merging authorizes automatic publication when enabled. Never use\n   `--admin` or bypass checks. Report the PR URL and stop; the user reviews\u002Fmerges.\n\nFor a cold-start test, perform this same PR-opening workflow. Do not stop after\ndescribing what you would do. An incorrect test PR can be closed without publishing.\nIf blocked, report the exact blocker rather than claiming the release is ready.\n",{"name":5,"description":7},"main","9e7876c47c30a6c44ca79915991bd5541d58764c",".github\u002Fskills\u002Frelease-package",1,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system","https:\u002F\u002Fcoreai-ds.azurewebsites.net","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-06 05:33:55",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add microsoft\u002Fcoreai-design-system --skill release-package",{"tool":46,"command":47},"bunx","bunx skills add microsoft\u002Fcoreai-design-system --skill release-package",{"tool":49,"command":50},"pnpm","pnpm dlx skills add microsoft\u002Fcoreai-design-system --skill release-package","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-package\u002FSKILL.md",true,[],[55,74,84,94,101,112],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":69,"publishedAt":25},"01M69BB0EA71EEW0TWV6DDMF5S","coreai-ds-fluentui-react","MANDATORY for @coreai-ds\u002Freact-components work. Use the CoreAI documentation MCP to discover components, props, stories, templates, and implementation patterns. If the MCP is unavailable, stop and ask the user to enable or troubleshoot it with you.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fpackages\u002Freact-components\u002Fagent\u002FSKILL.md",[61,66],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":67,"categoryName":68,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000023","Skill与智能体开发",[70,21,71,20,72,73],"coreai ds fluentui react","documentation","troubleshoot","MCP",{"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":80,"publishedAt":25},"01M69BAYVCBBZE7HY5RF871G5J","state-management","CoreAI Sandbox's simplified TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app\u002Fhooks\u002Fuse*.ts`), adding mock data in `app\u002Fdata\u002F`, or wiring a component to query state.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fapps\u002Fprototype\u002F.github\u002Fskills\u002Fstate-management\u002FSKILL.md",[],[81,82,83],"state management","component","sandbox",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":25},"01M69BAX7PT3JC7V84DVTSRWN4","start-app","Start the CoreAI Sandbox dev server and open it using available browser tools. USE WHEN: the user asks you to \"start the app\", \"run the dev server\", \"open the app\", or \"launch CoreAI Sandbox\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fapps\u002Fprototype\u002F.github\u002Fskills\u002Fstart-app\u002FSKILL.md",[],[91,83,92,93],"start app","run","launch",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":25},"01M69BAVXDBYFNKF45DQ1FPN40","routing","React Router v7 routing conventions for this SPA. USE WHEN: editing `app\u002Froutes.ts`, adding\u002Fremoving a route, or changing navigation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fapps\u002Fprototype\u002F.github\u002Fskills\u002Frouting\u002FSKILL.md",[],[96,21],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":109,"publishedAt":25},"01M69BASXQZQTQB2GH2V79FZ6Y","react-components","CoreAI Sandbox component usage: import boundaries, CoreAI MCP documentation, and local adapter inspection. USE WHEN: editing any `*.tsx` file, picking a component, or writing component imports.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fapps\u002Fprototype\u002F.github\u002Fskills\u002Freact-components\u002FSKILL.md",[107,108],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},{"categoryNo":67,"categoryName":68,"taxonomyType":64,"taxonomyTypeDesc":65},[20,21,110,71,82,83,111,73],"react components","writing",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":25},"01M69BAR4147BKNY7H41DYMPGP","new-variant","Create a new design variant or alternative for a page using the built-in feature\u002Fvariant system. USE WHEN: a designer wants to try a different layout, create an \"option B\" or \"version 2\", compare designs side by side, add an A\u002FB alternative, or explore an alternate version. Do NOT build a custom toggle solution.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreai-design-system\u002Fblob\u002Fmain\u002Fapps\u002Fprototype\u002F.github\u002Fskills\u002Fnew-variant\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000015","视觉设计",[122,123,124],"new variant","design","create"]