[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BQ0CYV95X84G4F8E3YNXD":3,"skill-same:01M69BQ0CYV95X84G4F8E3YNXD":49},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M69BQ0CYV95X84G4F8E3YNXD","use-case-designer",null,"Design the PM-level Use case tab and selectable user journeys.","microsoft\u002FTandem","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BPCSX0M4XSS5Z9SN4S28W",8,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fuse-case-designer\u002FSKILL.md",[],[19,20],"use case designer","design","2026-11-10 10:12:30",false,"---\r\nname: use-case-designer\r\ndescription: \"Design the PM-level Use case tab and selectable user journeys.\"\r\nuser-invocable: false\r\n---\r\n\r\n# Use-Case Designer\r\n\r\nDesign the PM-level product overview before considering internal architecture.\r\n\r\nIdentify two to seven major use cases that together cover the core product experience. A use case\r\nis a user goal with an observable outcome—not an API endpoint, screen, command, or internal\r\noperation. Do not enumerate minor edge cases.\r\n\r\nFor each use case provide:\r\n\r\n- a stable ID and short goal-oriented title;\r\n- the user or external actor;\r\n- the observable outcome;\r\n- a representative journey of one to six steps.\r\n\r\nEach step follows:\r\n\r\n```text\r\n{ id, userAction, systemResponse, interactionId }\r\n```\r\n\r\nImplementation state belongs only to the containing Use case. Do not put `implementationState`\r\non journey steps; they remain fine-grained design and Attention anchors while the host initializes\r\nand preserves coarse Use case progress.\r\n\r\nUse the user's language and assume the reviewer has no software-development background. Titles,\r\nactions, and responses must describe recognizable goals and visible behavior without API,\r\nframework, or architecture jargon. A reviewer should understand the complete experience map by\r\nreading only its visible labels. `interactionId` must exactly match a stable `contract-set\u002Fv1`\r\ninteraction ID, not its display name. Together the use cases form an experience map; selecting one\r\nreveals its journey. Keep the primary experience clear while leaving detailed error branches to\r\nthe Contract or Flow subviews.\r\n\r\nAttach zero to three Attention items directly to the relevant Use case or journey step, only for\r\nconsequential ambiguity in a user goal or observable outcome. Each item has `id`, `impact`,\r\n`question`, `whyItMatters`, and two or three `{ option, implication }` alternatives.\r\n\r\nPersist `{ useCases }` through `submit_use_case_block`. On revision, use the inherited block,\r\nincluding its embedded Attention, as the baseline and submit only when this perspective changes.\r\n","# Use-Case Designer\r\n\r\nDesign the PM-level product overview before considering internal architecture.\r\n\r\nIdentify two to seven major use cases that together cover the core product experience. A use case\r\nis a user goal with an observable outcome—not an API endpoint, screen, command, or internal\r\noperation. Do not enumerate minor edge cases.\r\n\r\nFor each use case provide:\r\n\r\n- a stable ID and short goal-oriented title;\r\n- the user or external actor;\r\n- the observable outcome;\r\n- a representative journey of one to six steps.\r\n\r\nEach step follows:\r\n\r\n```text\r\n{ id, userAction, systemResponse, interactionId }\r\n```\r\n\r\nImplementation state belongs only to the containing Use case. Do not put `implementationState`\r\non journey steps; they remain fine-grained design and Attention anchors while the host initializes\r\nand preserves coarse Use case progress.\r\n\r\nUse the user's language and assume the reviewer has no software-development background. Titles,\r\nactions, and responses must describe recognizable goals and visible behavior without API,\r\nframework, or architecture jargon. A reviewer should understand the complete experience map by\r\nreading only its visible labels. `interactionId` must exactly match a stable `contract-set\u002Fv1`\r\ninteraction ID, not its display name. Together the use cases form an experience map; selecting one\r\nreveals its journey. Keep the primary experience clear while leaving detailed error branches to\r\nthe Contract or Flow subviews.\r\n\r\nAttach zero to three Attention items directly to the relevant Use case or journey step, only for\r\nconsequential ambiguity in a user goal or observable outcome. Each item has `id`, `impact`,\r\n`question`, `whyItMatters`, and two or three `{ option, implication }` alternatives.\r\n\r\nPersist `{ useCases }` through `submit_use_case_block`. On revision, use the inherited block,\r\nincluding its embedded Attention, as the baseline and submit only when this perspective changes.\r\n",{"name":5,"description":7,"user-invocable":22},"main","c3a12ac559c6e322fa4ee3b27784de9a119dba83",".github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fuse-case-designer",1,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-02 18:26:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002FTandem --skill use-case-designer",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002FTandem --skill use-case-designer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002FTandem --skill use-case-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fuse-case-designer\u002FSKILL.md",true,[],[50,77,101,106,120,128],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":21},"01M6EWXWQXH5TEKHW5GK37TT8N","brainstorm-whiteboard","An Excalidraw-powered, two-way brainstorming whiteboard that both the agent and the human can edit, annotate and seal as peers. Use it when a user can show an idea or feedback more easily than type it, or when a sketch helps the agent explain, explore or compare ideas. Read and interpret human sketches as well as creating your own; proactively use shapes, diagrams and annotations without waiting for a drawing request. Keep chat self-contained so viewing the board is never required to understand the response.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fskills\u002Fbrainstorm-whiteboard\u002FSKILL.md",[],[57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76],"brainstorm whiteboard","brainstorm","diagrams","explain","show","annotate","chat","self","human","drawing","ideas","as","type","compare","keep","never","use","feedback","explore","brainstorming",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":96,"publishedAt":21},"01M69BQJBH2TQX1F69VH1P662Z","tandem","Optional Q&A and prototype discovery, or direct native Development for Design, implementation and Review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fskills\u002Ftandem\u002FSKILL.md",[83,88,91],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[79,97,98,99,20,100],"development","prototype","review","frontend",{"skillNo":102,"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":103,"categories":104,"keywords":105,"publishedAt":21},"01M69BQFXM4VQG92TDS894XZN0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fuse-case-designer\u002FSKILL.md",[],[19,20],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":115,"publishedAt":21},"01M69BQDZKN17P8207KHQPZHEC","storage-contract-designer","Design memory, database, file, object-store, or cache contracts inside Contract.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fstorage-contract-designer\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000037","律师与法务",[116,117,118,119,20],"storage","contract designer","storage contract designer","memory",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":21},"01M69BQCCTZVRHW4DAHK0YDEV1","stack-designer","Design the layered technology stack shown in the System tab.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fstack-designer\u002FSKILL.md",[],[127,20],"stack designer",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":21},"01M69BQB0EBWW8W9WZ60KRVP55","module-designer","Refine responsibilities in the layered System technology stack.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fmodule-designer\u002FSKILL.md",[],[135],"module designer"]