[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BWXNT7D0NMAJAD08VFP19":3,"skill-same:01M69BWXNT7D0NMAJAD08VFP19":67},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M69BWXNT7D0NMAJAD08VFP19","docs-sync",null,"Diff src\u002F and .github\u002F against docs\u002F to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths\u002Fmodules\u002Fdiagrams\u002Fsyntax\u002Fagents\u002Fskills\u002Fhooks), or before a release. Use for questions like \"is docs in sync?\", \"what changed since the last docs update?\", \"find docs drift\". Produces a structured report with proposed edits — does not modify docs\u002F directly.","microsoft\u002Flearn-ai-native-dev","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BWP5CZJYHBN950HX4GQAX",21,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdocs-sync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"docs","sync","docs sync","design","spec","github","update","code","report","release","2026-11-10 10:12:30",false,"---\nname: docs-sync\ndescription: Diff src\u002F and .github\u002F against docs\u002F to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths\u002Fmodules\u002Fdiagrams\u002Fsyntax\u002Fagents\u002Fskills\u002Fhooks), or before a release. Use for questions like \"is docs in sync?\", \"what changed since the last docs update?\", \"find docs drift\". Produces a structured report with proposed edits — does not modify docs\u002F directly.\n---\n\n# Docs Sync (skill)\n\nThis skill is the diffing playbook the\n[`@docs-auditor`](..\u002F..\u002Fagents\u002Fdocs-auditor.agent.md) agent runs. You can also\ninvoke it directly with `\u002Fdocs-sync`.\n\nIt produces a **drift report**. It does not write to `docs\u002F`. Apply changes by\ndelegating to `@author`.\n\n## Inputs\n\n- `$ARGUMENTS` (optional) — restrict the audit to one of:\n  `paths` | `tracks` | `components` | `syntax` | `harness` | `routes` | `lifecycle` | `links` | `all`. Default: `all`.\n\n## Procedure\n\n### Step 1 — Snapshot the code\n\nCollect, in this order:\n\n1. `src\u002Fdata\u002Fpaths.ts` exports.\n2. All `path.json` files under `src\u002Fcontent\u002Fcommunity\u002F*\u002F`.\n3. Frontmatter (`id`, `number`, `title`, `subtitle`) of every markdown file\n   under `src\u002Fcontent\u002F{tutorial,advanced,terminal}\u002F`.\n4. The list of files under `src\u002Fcomponents\u002Fdiagrams\u002F` (excluding `index.ts`).\n5. The list of files under `.github\u002F{instructions,prompts,skills,agents,hooks}\u002F`.\n6. The route table from `src\u002FApp.tsx`.\n\n### Step 2 — Snapshot the docs\n\nCollect:\n\n1. The track tables in `docs\u002Ftracks\u002F{foundation,agentic,terminal}.md` and\n   the contribution-shape table in `docs\u002Fcommunity-contributions.md`.\n2. The component\u002Fdiagram references in `docs\u002Fcomponents.md`.\n3. The custom-syntax table in `docs\u002Fcontent-architecture.md` (§5) and the\n   route table (§2).\n4. The harness inventory tables in `docs\u002Fharness.md`.\n5. The status table in `docs\u002Flifecycle.md`.\n6. All relative links in every `docs\u002F*.md` file.\n\n### Step 3 — Diff\n\nCompare each pair from Steps 1 and 2:\n\n- **Code item missing from docs** → `add to docs`.\n- **Doc item missing from code** → `remove from docs` (only if file is gone)\n  or `flag for human review` (if file might be renamed).\n- **Mismatched fields** (title, subtitle, status, applyTo, …) → `update doc`.\n- **Broken relative link** → `fix link`.\n\n### Step 4 — Group findings\n\nGroup by target file in `docs\u002F`. Each group becomes one section in the\nreport.\n\n### Step 5 — Emit report\n\nUse the template at `templates\u002Freport.md` (see below).\n\n## Report template\n\n```markdown\n# Docs Sync — \u003CISO date>\n\nScope: `$ARGUMENTS`\nWorkspace: \u003Cgit short SHA>\n\n## Summary\n- Files needing updates: N\n- New items to document: N\n- Items to remove: N\n- Broken links: N\n\n## docs\u002Ftracks\u002Ffoundation.md\n- ⚠️ Subtitle drift on Part 4: docs say \"Different rules per folder\", code says \"Different rules for different folders\".\n- Proposed: update row.\n\n## docs\u002Fcomponents.md\n- ❌ Diagram `NewFlowDiagram.tsx` exists in `src\u002Fcomponents\u002Fdiagrams\u002F` but is not referenced.\n- Proposed: add row to \"Diagrams\" section.\n\n…\n\n## Suggested next step\nRun `@author` and paste this report.\n```\n\n## Boundaries\n\n- Do not write to `docs\u002F`. Output only.\n- Do not change content lifecycle statuses or example tracks.\n- Do not run `npm run build` — that is the `@reviewer`'s job. You may run\n  it read-only if a link looks ambiguous.\n- Treat `.github\u002FCONTENT_LIFECYCLE.md` as the source of truth when it\n  conflicts with `docs\u002Flifecycle.md`.\n\n## Related\n\n- Agent: [`docs-auditor`](..\u002F..\u002Fagents\u002Fdocs-auditor.agent.md).\n- Spec: [`docs\u002Fharness.md`](..\u002F..\u002F..\u002Fdocs\u002Fharness.md#docs-auditor).\n","# Docs Sync (skill)\n\nThis skill is the diffing playbook the\n[`@docs-auditor`](..\u002F..\u002Fagents\u002Fdocs-auditor.agent.md) agent runs. You can also\ninvoke it directly with `\u002Fdocs-sync`.\n\nIt produces a **drift report**. It does not write to `docs\u002F`. Apply changes by\ndelegating to `@author`.\n\n## Inputs\n\n- `$ARGUMENTS` (optional) — restrict the audit to one of:\n  `paths` | `tracks` | `components` | `syntax` | `harness` | `routes` | `lifecycle` | `links` | `all`. Default: `all`.\n\n## Procedure\n\n### Step 1 — Snapshot the code\n\nCollect, in this order:\n\n1. `src\u002Fdata\u002Fpaths.ts` exports.\n2. All `path.json` files under `src\u002Fcontent\u002Fcommunity\u002F*\u002F`.\n3. Frontmatter (`id`, `number`, `title`, `subtitle`) of every markdown file\n   under `src\u002Fcontent\u002F{tutorial,advanced,terminal}\u002F`.\n4. The list of files under `src\u002Fcomponents\u002Fdiagrams\u002F` (excluding `index.ts`).\n5. The list of files under `.github\u002F{instructions,prompts,skills,agents,hooks}\u002F`.\n6. The route table from `src\u002FApp.tsx`.\n\n### Step 2 — Snapshot the docs\n\nCollect:\n\n1. The track tables in `docs\u002Ftracks\u002F{foundation,agentic,terminal}.md` and\n   the contribution-shape table in `docs\u002Fcommunity-contributions.md`.\n2. The component\u002Fdiagram references in `docs\u002Fcomponents.md`.\n3. The custom-syntax table in `docs\u002Fcontent-architecture.md` (§5) and the\n   route table (§2).\n4. The harness inventory tables in `docs\u002Fharness.md`.\n5. The status table in `docs\u002Flifecycle.md`.\n6. All relative links in every `docs\u002F*.md` file.\n\n### Step 3 — Diff\n\nCompare each pair from Steps 1 and 2:\n\n- **Code item missing from docs** → `add to docs`.\n- **Doc item missing from code** → `remove from docs` (only if file is gone)\n  or `flag for human review` (if file might be renamed).\n- **Mismatched fields** (title, subtitle, status, applyTo, …) → `update doc`.\n- **Broken relative link** → `fix link`.\n\n### Step 4 — Group findings\n\nGroup by target file in `docs\u002F`. Each group becomes one section in the\nreport.\n\n### Step 5 — Emit report\n\nUse the template at `templates\u002Freport.md` (see below).\n\n## Report template\n\n```markdown\n# Docs Sync — \u003CISO date>\n\nScope: `$ARGUMENTS`\nWorkspace: \u003Cgit short SHA>\n\n## Summary\n- Files needing updates: N\n- New items to document: N\n- Items to remove: N\n- Broken links: N\n\n## docs\u002Ftracks\u002Ffoundation.md\n- ⚠️ Subtitle drift on Part 4: docs say \"Different rules per folder\", code says \"Different rules for different folders\".\n- Proposed: update row.\n\n## docs\u002Fcomponents.md\n- ❌ Diagram `NewFlowDiagram.tsx` exists in `src\u002Fcomponents\u002Fdiagrams\u002F` but is not referenced.\n- Proposed: add row to \"Diagrams\" section.\n\n…\n\n## Suggested next step\nRun `@author` and paste this report.\n```\n\n## Boundaries\n\n- Do not write to `docs\u002F`. Output only.\n- Do not change content lifecycle statuses or example tracks.\n- Do not run `npm run build` — that is the `@reviewer`'s job. You may run\n  it read-only if a link looks ambiguous.\n- Treat `.github\u002FCONTENT_LIFECYCLE.md` as the source of truth when it\n  conflicts with `docs\u002Flifecycle.md`.\n\n## Related\n\n- Agent: [`docs-auditor`](..\u002F..\u002Fagents\u002Fdocs-auditor.agent.md).\n- Spec: [`docs\u002Fharness.md`](..\u002F..\u002F..\u002Fdocs\u002Fharness.md#docs-auditor).\n",{"name":5,"description":7},"main","d88d026d964974e431125933a0168778e2023b69",".github\u002Fskills\u002Fdocs-sync",6,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-22 06:39:53",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002Flearn-ai-native-dev --skill docs-sync",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002Flearn-ai-native-dev --skill docs-sync",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002Flearn-ai-native-dev --skill docs-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdocs-sync\u002FSKILL.md",true,[57,63],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fadvanced-usage.md","REFERENCE","参考文档",18889,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fmultimodal-blip-2\u002Freferences\u002Fadvanced-usage.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Ftroubleshooting.md",11981,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fmultimodal-blip-2\u002Freferences\u002Ftroubleshooting.md",[68,86,102,113,122,134],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":29},"01M69BX5QMCFMJCMFPEH5EE7S8","version-checker","Validate that tutorial content references current tool versions, APIs, CLI commands, and features. Use when reviewing content for outdated information, checking deprecations, verifying feature availability, auditing tool references, or updating stale version numbers. Covers GitHub Copilot (VS Code + CLI), Claude Code, VS Code settings, MCP, and Agent Skills standard.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fversion-checker\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,24,81,82,83,84,85,26],"version checker","github copilot","cli","MCP","validate","copilot",{"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":97,"publishedAt":29},"01M69BX3MH209HKSCNHEMXH47W","tutorial-content-qa","Comprehensive quality assurance for AI-Native development tutorials across all tracks (Foundation, Advanced, Terminal). Use when reviewing content for accuracy, clarity, consistency, and completeness. Use for proofreading, checking errors, auditing content, or running QA checks before publishing.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftutorial-content-qa\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[98,99,100,101],"qa","tutorial content qa","development","terminal",{"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":29},"01M69BX1Q0E649ZKXNPWMCP07G","track-generator","Generate new example tracks for the AI-Native tutorial. Use when creating new industry examples, adding a new track, building project templates, or expanding learning paths. Use for questions like \"add a track for healthcare\", \"create new example\", \"new industry template\". Produces consistent ExampleTrack data with all required fields including projectName, requirements, colorCoding, taskExamples, and verification examples matching the TypeScript interface in exampleTracks.ts.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrack-generator\u002FSKILL.md",[],[109,110,111,112],"track generator","typescript","generate","create",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":29},"01M69BWZPTT11BSHHQSC29B5M3","exercise-scaffolder","Generate consistent, high-quality coding exercises for AI-Native development tutorials. Use when creating hands-on exercises, coding challenges, practice problems, quizzes, labs, or skill-building activities. Use for questions like \"create an exercise\", \"add practice activity\", \"build a challenge for Part X\". Includes starter templates, solution patterns, hint progressions, and verification criteria.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fexercise-scaffolder\u002FSKILL.md",[119],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[121,111,112,100],"exercise scaffolder",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":29},"01M69BWVBVN45H7VECN89KFTAR","diagram-scaffolder","Generate new interactive diagram components for tutorial content. Use when adding a visual diagram, creating architectural illustrations, or building interactive flow visualizations. Use for questions like \"add a diagram\", \"create diagram component\", \"new visual for module X\". Produces a React component, registers it in the barrel export and StepCard parser, and provides the markdown reference syntax.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdiagram-scaffolder\u002FSKILL.md",[],[129,130,111,112,131,132,133],"diagram scaffolder","diagram","component","react","components",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":29},"01M69BWRX43VF0KSGZDC2AFXBX","content-track-scaffolder","Scaffold a complete new content track (like Foundation, Advanced, or Terminal) with all required files — data parser, page components, routes, markdown content, and navigation. Use when adding a new learning path, creating a new track, or expanding the tutorial with a new module series. Use for questions like \"add a new track\", \"create learning path for X\", \"scaffold track pages\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Flearn-ai-native-dev\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcontent-track-scaffolder\u002FSKILL.md",[140],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[142,101,112,143,133],"content track scaffolder","scaffold"]