[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BPWD6VCX6EPGQJ9V1EJS1":3,"skill-same:01M69BPWD6VCX6EPGQJ9V1EJS1":63},{"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},"01M69BPWD6VCX6EPGQJ9V1EJS1","stack-designer",null,"Design the layered technology stack shown in the System tab.","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\u002Fstack-designer\u002FSKILL.md",[],[19,20],"stack designer","design","2026-11-10 10:12:30",false,"---\r\nname: stack-designer\r\ndescription: \"Design the layered technology stack shown in the System tab.\"\r\nuser-invocable: false\r\n---\r\n\r\n# Stack Designer\r\n\r\nUse this method only when technologies, frameworks, or protocols materially shape the design or\r\nrequire user review. Omit it when implementation-agnostic or already determined.\r\n\r\nEmit exactly one `systemStacks[0]` with two to six ordered layers. Each layer contains:\r\n\r\n- a stable ID and short name;\r\n- one responsibility;\r\n- one to four concrete technologies, each with a short role.\r\n\r\nOrder layers from the user-facing surface down toward runtime and persistence. Include only\r\ntechnologies selected or directly implied by the design; do not invent a broad dependency\r\ninventory. Explain consequential alternatives through embedded Attention rather than listing\r\ncompeting choices in the layer. Produce one concise `system` aspect. Do not create a Stack tab,\r\ncomponent graph, connections, coordinates, or styling.\r\n\r\nTechnical names may remain where they are consequential, but every layer responsibility and\r\ntechnology role must explain its product purpose in plain language. A non-experienced reviewer\r\nshould be able to understand why each layer exists without knowing the framework or infrastructure\r\nbeforehand.\r\n\r\nAttach zero to three Attention items directly to the relevant System layer for consequential\r\ntechnology, runtime, deployment, module-boundary, or persistence-engine choices. Each item has\r\n`id`, `impact`, `question`, `whyItMatters`, and two or three `{ option, implication }`\r\nalternatives. JSON versus SQLite belongs here.\r\n\r\nAfter incorporating any Module or Deployment method output, persist\r\n`{ systemStacks }` through `submit_system_block`. For initial design, an omitted method submits an\r\nempty `systemStacks` array. On revision, use the inherited block, including embedded Attention, as\r\nthe baseline and submit only when this perspective changes.\r\n","# Stack Designer\r\n\r\nUse this method only when technologies, frameworks, or protocols materially shape the design or\r\nrequire user review. Omit it when implementation-agnostic or already determined.\r\n\r\nEmit exactly one `systemStacks[0]` with two to six ordered layers. Each layer contains:\r\n\r\n- a stable ID and short name;\r\n- one responsibility;\r\n- one to four concrete technologies, each with a short role.\r\n\r\nOrder layers from the user-facing surface down toward runtime and persistence. Include only\r\ntechnologies selected or directly implied by the design; do not invent a broad dependency\r\ninventory. Explain consequential alternatives through embedded Attention rather than listing\r\ncompeting choices in the layer. Produce one concise `system` aspect. Do not create a Stack tab,\r\ncomponent graph, connections, coordinates, or styling.\r\n\r\nTechnical names may remain where they are consequential, but every layer responsibility and\r\ntechnology role must explain its product purpose in plain language. A non-experienced reviewer\r\nshould be able to understand why each layer exists without knowing the framework or infrastructure\r\nbeforehand.\r\n\r\nAttach zero to three Attention items directly to the relevant System layer for consequential\r\ntechnology, runtime, deployment, module-boundary, or persistence-engine choices. Each item has\r\n`id`, `impact`, `question`, `whyItMatters`, and two or three `{ option, implication }`\r\nalternatives. JSON versus SQLite belongs here.\r\n\r\nAfter incorporating any Module or Deployment method output, persist\r\n`{ systemStacks }` through `submit_system_block`. For initial design, an omitted method submits an\r\nempty `systemStacks` array. On revision, use the inherited block, including embedded Attention, as\r\nthe baseline and submit only when this perspective changes.\r\n",{"name":5,"description":7,"user-invocable":22},"main","c3a12ac559c6e322fa4ee3b27784de9a119dba83",".github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fstack-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 stack-designer",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002FTandem --skill stack-designer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002FTandem --skill stack-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fstack-designer\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fflows.md","REFERENCE","参考文档",9846,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fagents-crewai\u002Freferences\u002Fflows.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Ftools.md",10283,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fagents-crewai\u002Freferences\u002Ftools.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ftroubleshooting.md",8933,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fagents-crewai\u002Freferences\u002Ftroubleshooting.md",[64,91,115,123,137,142],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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",[],[71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"brainstorm whiteboard","brainstorm","diagrams","explain","show","annotate","chat","self","human","drawing","ideas","as","type","compare","keep","never","use","feedback","explore","brainstorming",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":110,"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",[97,102,105],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[93,111,112,113,20,114],"development","prototype","review","frontend",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":21},"01M69BQFXM4VQG92TDS894XZN0","use-case-designer","Design the PM-level Use case tab and selectable user journeys.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fuse-case-designer\u002FSKILL.md",[],[122,20],"use case designer",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000037","律师与法务",[133,134,135,136,20],"storage","contract designer","storage contract designer","memory",{"skillNo":138,"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":139,"categories":140,"keywords":141,"publishedAt":21},"01M69BQCCTZVRHW4DAHK0YDEV1","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fstack-designer\u002FSKILL.md",[],[19,20],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"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",[],[149],"module designer"]