[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AGG8TNHWNXX8302FJHM2R":3,"skill-same:01M69AGG8TNHWNXX8302FJHM2R":104},{"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":28,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M69AGG8TNHWNXX8302FJHM2R","building-ui-ux",null,"Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration","microsoft\u002FFluidFramework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AG0BQKNGBJQ5YNG09HXXW",4949,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbuilding-ui-ux\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"building ui ux","ux","ui","ui ux","frontend","design","setup","integration","user","use","exploration","iteration","guides","implementing","when","design variations","2026-11-10 10:12:30",false,"---\nname: building-ui-ux\ndescription: Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration\n---\n\n\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n1. Ask user if they want to experiment with multiple UI variations or see a single design\n2. If user wants multiple variations, ask what kinds of variations to try\n3. If building a web frontend and it's not running, start the dev server and note the localhost URL\n4. Implement the UI\u002FUX design(s)\n5. Ask user for feedback on the design\n6. Iterate based on feedback\n7. Ensure the new UI is properly wired up and integrated\n\u003C\u002Frequired>\n\n# Building UI\u002FUX\n\n## Overview\n\nThis skill guides you through implementing user interfaces and experiences with an emphasis on exploration, feedback, and proper integration.\n\n**Core principle:** Explore variations, iterate with feedback, ensure proper integration.\n\n**Announce at start:** \"I'm using the Nori Building UI\u002FUX skill to implement your interface.\"\n\n## The Process\n\n### Phase 1: Scope & Variation Planning\n\n**Ask the user:**\n\n\"Would you like to:\n- See multiple UI variations to choose from?\n- Go with a single design approach?\"\n\n**If multiple variations:**\n- Ask what kinds of variations they want (e.g., minimalist vs rich, card-based vs list-based, light vs dark)\n- Aim for 2-4 distinct approaches\n- Plan to implement all variations in a way that allows easy comparison\n\n### Phase 2: Frontend Environment Setup\n\n**For web projects:**\n\nCheck if the dev server is running:\n- If not, identify the start command (e.g., `npm run dev`, `npm start`)\n- Start the dev server\n- Note the localhost URL (typically `http:\u002F\u002Flocalhost:3000` or similar)\n- Inform user: \"Starting dev server at [URL]\"\n\n**For other UI types:**\n- Identify appropriate preview\u002Ftesting mechanism\n- Set up accordingly\n\n### Phase 3: Implementation\n\n**When implementing multiple variations:**\n\nStack variations in a way that makes comparison easy. For web UIs, this typically means:\n- Render all variations on a single page, stacked vertically\n- Add clear section dividers\u002Fheadings for each variation\n- Use consistent spacing between variations\n- Ensure each variation is self-contained and functional\n\n**Example for React:**\n```tsx\nexport default function UIExploration() {\n  return (\n    \u003Cdiv className=\"ui-exploration\">\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 1: Minimalist\u003C\u002Fh2>\n        \u003CMinimalistLogin \u002F>\n      \u003C\u002Fsection>\n\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 2: Modern Gradient\u003C\u002Fh2>\n        \u003CModernLogin \u002F>\n      \u003C\u002Fsection>\n\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 3: Classic Corporate\u003C\u002Fh2>\n        \u003CClassicLogin \u002F>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n**When implementing a single design:**\n- Focus on clean, production-ready implementation\n- Follow project conventions and style guides\n- Ensure responsive design if applicable\n\n### Phase 4: Feedback & Iteration\n\n**Present to user:**\n- Share the localhost URL or preview mechanism\n- Briefly describe each variation (if multiple)\n- Ask: \"What do you think? Any changes you'd like to see?\"\n\n**Iterate based on feedback:**\n- Make requested changes\n- Continue asking for feedback until satisfied\n- Be ready to combine elements from different variations\n\n### Phase 5: Integration & Wiring\n\n**Ensure proper integration:**\n\n- Remove exploration scaffolding (if used)\n- Wire up to actual data sources\u002FAPIs\n- Connect to routing\u002Fnavigation\n- Add proper state management\n- Implement error handling\n- Add loading states if applicable\n- Test all interactive elements\n- Verify accessibility basics\n\n**Common integration points to check:**\n- Form submissions → backend endpoints\n- Navigation → routing system\n- Authentication → auth context\u002Fstore\n- Data fetching → API layer\n- Error boundaries → error handling\n- Responsive behavior → breakpoints\n","\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n1. Ask user if they want to experiment with multiple UI variations or see a single design\n2. If user wants multiple variations, ask what kinds of variations to try\n3. If building a web frontend and it's not running, start the dev server and note the localhost URL\n4. Implement the UI\u002FUX design(s)\n5. Ask user for feedback on the design\n6. Iterate based on feedback\n7. Ensure the new UI is properly wired up and integrated\n\u003C\u002Frequired>\n\n# Building UI\u002FUX\n\n## Overview\n\nThis skill guides you through implementing user interfaces and experiences with an emphasis on exploration, feedback, and proper integration.\n\n**Core principle:** Explore variations, iterate with feedback, ensure proper integration.\n\n**Announce at start:** \"I'm using the Nori Building UI\u002FUX skill to implement your interface.\"\n\n## The Process\n\n### Phase 1: Scope & Variation Planning\n\n**Ask the user:**\n\n\"Would you like to:\n- See multiple UI variations to choose from?\n- Go with a single design approach?\"\n\n**If multiple variations:**\n- Ask what kinds of variations they want (e.g., minimalist vs rich, card-based vs list-based, light vs dark)\n- Aim for 2-4 distinct approaches\n- Plan to implement all variations in a way that allows easy comparison\n\n### Phase 2: Frontend Environment Setup\n\n**For web projects:**\n\nCheck if the dev server is running:\n- If not, identify the start command (e.g., `npm run dev`, `npm start`)\n- Start the dev server\n- Note the localhost URL (typically `http:\u002F\u002Flocalhost:3000` or similar)\n- Inform user: \"Starting dev server at [URL]\"\n\n**For other UI types:**\n- Identify appropriate preview\u002Ftesting mechanism\n- Set up accordingly\n\n### Phase 3: Implementation\n\n**When implementing multiple variations:**\n\nStack variations in a way that makes comparison easy. For web UIs, this typically means:\n- Render all variations on a single page, stacked vertically\n- Add clear section dividers\u002Fheadings for each variation\n- Use consistent spacing between variations\n- Ensure each variation is self-contained and functional\n\n**Example for React:**\n```tsx\nexport default function UIExploration() {\n  return (\n    \u003Cdiv className=\"ui-exploration\">\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 1: Minimalist\u003C\u002Fh2>\n        \u003CMinimalistLogin \u002F>\n      \u003C\u002Fsection>\n\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 2: Modern Gradient\u003C\u002Fh2>\n        \u003CModernLogin \u002F>\n      \u003C\u002Fsection>\n\n      \u003Csection className=\"variation\">\n        \u003Ch2>Variation 3: Classic Corporate\u003C\u002Fh2>\n        \u003CClassicLogin \u002F>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n**When implementing a single design:**\n- Focus on clean, production-ready implementation\n- Follow project conventions and style guides\n- Ensure responsive design if applicable\n\n### Phase 4: Feedback & Iteration\n\n**Present to user:**\n- Share the localhost URL or preview mechanism\n- Briefly describe each variation (if multiple)\n- Ask: \"What do you think? Any changes you'd like to see?\"\n\n**Iterate based on feedback:**\n- Make requested changes\n- Continue asking for feedback until satisfied\n- Be ready to combine elements from different variations\n\n### Phase 5: Integration & Wiring\n\n**Ensure proper integration:**\n\n- Remove exploration scaffolding (if used)\n- Wire up to actual data sources\u002FAPIs\n- Connect to routing\u002Fnavigation\n- Add proper state management\n- Implement error handling\n- Add loading states if applicable\n- Test all interactive elements\n- Verify accessibility basics\n\n**Common integration points to check:**\n- Form submissions → backend endpoints\n- Navigation → routing system\n- Authentication → auth context\u002Fstore\n- Data fetching → API layer\n- Error boundaries → error handling\n- Responsive behavior → breakpoints\n",{"name":5,"description":7},"main","5e94cbfa27965a98428f7d26b69dd5b0a8abeb0d",".agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbuilding-ui-ux",590,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework","https:\u002F\u002Ffluidframework.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:12:05",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002FFluidFramework --skill building-ui-ux",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002FFluidFramework --skill building-ui-ux",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill building-ui-ux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbuilding-ui-ux\u002FSKILL.md",true,[74,80,84,90,94,98],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fpanelist-return-schema.json","ASSET","资产文件",2201,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fassets\u002Fpanelist-return-schema.json",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fsubagent-prompt-template.md",2905,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fassets\u002Fsubagent-prompt-template.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fcontent-evals.json","REFERENCE","参考文档",3176,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fevals\u002Fcontent-evals.json",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002FREADME.md",1158,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fevals\u002FREADME.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Ftrigger-evals.json",2352,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fevals\u002Ftrigger-evals.json",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fscan-cross-corpus-drift.sh","SCRIPT","脚本",3195,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fapm\u002Fblob\u002Fmain\u002F.apm\u002Fskills\u002Fdocs-corpus-audit\u002Fscripts\u002Fscan-cross-corpus-drift.sh",[105,125,159,183,201,224],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":45},"01M6PJ5SAHYFZFWDG5Y4RW56EP","trigger-pipelines-for-copilot-pr","Trigger ADO pipelines for a Copilot-created PR by posting \u002Fazp run comments. Use when the user asks to trigger CI pipelines for a specific PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrigger-pipelines-for-copilot-pr\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,121,38,122,123,124,37,43],"pr","trigger pipelines for copilot pr","for","trigger","copilot","pipelines","ado","posting","run","ci","number","URL","comments",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":140,"publishedAt":45},"01M6PJ5M4ZG7E78C4GM4041HEP","review","Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview\u002FSKILL.md",[131,134,137],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":138,"categoryName":139,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[127,141,142,143,34,144,145,146,147,148,149,150,151,152,153,154,155,156,114,157,158],"branch","regression","code review","ask","analysis","code","commit","api","change","artifact","request","pull","tree","as","do","diff","assess","ambiguous",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":45},"01M6PJ5E3PCBDS319FFMHPFACN","review-pr-local","The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview-pr-local\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,127,112,170,171,172,141,173,174,175,176,177,178,179,123,180,144,148,181,182],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","you","cli","worktree",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":45},"01M6PJ5AVZAS0AEBPCYJZ9ZMMD","policy-check","This skill should be used when the user asks to \"run policy check\", \"check policy\", \"policy-check\", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpolicy-check\u002FSKILL.md",[],[190,191,192,193,194,114,120,195,196,197,198,37,199,43,200],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","running","entire",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":45},"01M6PJ54H068MZF2WD2JDKCVDC","pipeline-test-triage","Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build\u002Fpipeline URL or build ID and wants failures analyzed, when they ask \"why did this pipeline fail\", \"summarize the test failures\", \"is this test flaky or a real bug\", \"compare these runs\", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpipeline-test-triage\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[211,212,213,214,215,216,217,218,179,123,144,120,219,220,221,222,118,154,223,114,43],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","bug","but","framework","bugs",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":230,"publishedAt":45},"01M6PJ4ZJASDV2CGQTG1JWKBFE","fluid-release","Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on \"release\", \"do the release\", \"release status\", version bump, release notes, changelog, release branch, or release engineering.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffluid-release\u002FSKILL.md",[],[231,232,233,172,141,234,235,236,237,238,177,239,240,241,242,243,244,245,246,247],"release","fluid release","fluid","bump","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]