[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BPYBBXEJDZ841TFPP46BF":3,"skill-same:01M69BPYBBXEJDZ841TFPP46BF":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":23,"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},"01M69BPYBBXEJDZ841TFPP46BF","storage-contract-designer",null,"Design memory, database, file, object-store, or cache contracts inside Contract.","microsoft\u002FTandem","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BPCSX0M4XSS5Z9SN4S28W",9,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fstorage-contract-designer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28],"storage","contract designer","storage contract designer","design","memory","2026-11-10 10:12:30",false,"---\r\nname: storage-contract-designer\r\ndescription: \"Design memory, database, file, object-store, or cache contracts inside Contract.\"\r\nuser-invocable: false\r\n---\r\n\r\n# Storage Contract Designer\r\n\r\nUse this method when consequential state is retained in memory, a database, a file, an object\r\nstore, or a cache. Omit it for genuinely stateless work. This method contributes\r\n`contract.storageContracts`; it never creates a Data tab or an `aspects` entry.\r\n\r\nFor each independently owned store emit exactly:\r\n\r\n```text\r\nstorageContract\r\n├─ id\r\n├─ name\r\n├─ medium: memory | database | file | object-store | cache\r\n├─ ownerParticipantId\r\n├─ purpose\r\n├─ records[]\r\n│  ├─ id\r\n│  ├─ name\r\n│  ├─ description\r\n│  ├─ fields[]: { id, name, type, required, description }\r\n│  ├─ keys[]: { id, kind, fieldIds, purpose }\r\n│  └─ constraints[]: { id, statement }\r\n├─ relations[]: { id, fromRecordId, toRecordId, kind, statement }\r\n├─ guarantees[]: { id, statement }\r\n└─ lifecycleRules[]: { id, statement }\r\n```\r\n\r\n`kind` for keys is `primary`, `unique`, or `index`; relation kind is `one-to-one`,\r\n`one-to-many`, or `many-to-many`. Use stable lowercase kebab-case IDs. Reference an existing\r\nContract participant as the owner. Include only fields, keys, constraints, and relationships that\r\ndefine the storage agreement or expose a consequential design assumption.\r\n\r\nThe contract must state what acknowledged storage operations guarantee and when records are\r\ncreated, changed, expired, or deleted. Do not describe storage as a generic architecture summary:\r\nmake its persisted shape and semantics reviewable.\r\n\r\nUse familiar domain names and plain-language field descriptions. Explain keys, relationships,\r\nretention, and durability in terms of what information the product remembers and what the user can\r\nexpect, rather than assuming database knowledge.\r\n\r\nReturn Attention about storage guarantees or persisted semantics to `contract-designer` for\r\nembedding on the relevant Contract entity. Return persistence-engine Attention such as JSON\r\nversus SQLite to `stack-designer` for embedding on the relevant System layer. Do not emit the same\r\nquestion in both places.\r\n","# Storage Contract Designer\r\n\r\nUse this method when consequential state is retained in memory, a database, a file, an object\r\nstore, or a cache. Omit it for genuinely stateless work. This method contributes\r\n`contract.storageContracts`; it never creates a Data tab or an `aspects` entry.\r\n\r\nFor each independently owned store emit exactly:\r\n\r\n```text\r\nstorageContract\r\n├─ id\r\n├─ name\r\n├─ medium: memory | database | file | object-store | cache\r\n├─ ownerParticipantId\r\n├─ purpose\r\n├─ records[]\r\n│  ├─ id\r\n│  ├─ name\r\n│  ├─ description\r\n│  ├─ fields[]: { id, name, type, required, description }\r\n│  ├─ keys[]: { id, kind, fieldIds, purpose }\r\n│  └─ constraints[]: { id, statement }\r\n├─ relations[]: { id, fromRecordId, toRecordId, kind, statement }\r\n├─ guarantees[]: { id, statement }\r\n└─ lifecycleRules[]: { id, statement }\r\n```\r\n\r\n`kind` for keys is `primary`, `unique`, or `index`; relation kind is `one-to-one`,\r\n`one-to-many`, or `many-to-many`. Use stable lowercase kebab-case IDs. Reference an existing\r\nContract participant as the owner. Include only fields, keys, constraints, and relationships that\r\ndefine the storage agreement or expose a consequential design assumption.\r\n\r\nThe contract must state what acknowledged storage operations guarantee and when records are\r\ncreated, changed, expired, or deleted. Do not describe storage as a generic architecture summary:\r\nmake its persisted shape and semantics reviewable.\r\n\r\nUse familiar domain names and plain-language field descriptions. Explain keys, relationships,\r\nretention, and durability in terms of what information the product remembers and what the user can\r\nexpect, rather than assuming database knowledge.\r\n\r\nReturn Attention about storage guarantees or persisted semantics to `contract-designer` for\r\nembedding on the relevant Contract entity. Return persistence-engine Attention such as JSON\r\nversus SQLite to `stack-designer` for embedding on the relevant System layer. Do not emit the same\r\nquestion in both places.\r\n",{"name":5,"description":7,"user-invocable":30},"main","c3a12ac559c6e322fa4ee3b27784de9a119dba83",".github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fstorage-contract-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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002FTandem --skill storage-contract-designer",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002FTandem --skill storage-contract-designer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002FTandem --skill storage-contract-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Ftandem\u002Fstage2\u002Fskills\u002Fstorage-contract-designer\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcms-platform-workflows.md","REFERENCE","参考文档",3314,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-management-systems\u002Freferences\u002Fcms-platform-workflows.md",[64,91,113,121,127,135],{"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":29},"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":108,"publishedAt":29},"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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[93,109,110,111,27,112],"development","prototype","review","frontend",{"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":119,"publishedAt":29},"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",[],[120,27],"use case designer",{"skillNo":122,"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":123,"categories":124,"keywords":126,"publishedAt":29},"01M69BQDZKN17P8207KHQPZHEC","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FTandem\u002Fblob\u002Fmain\u002Fdevelopment\u002Ftandem\u002Fskills\u002Fstorage-contract-designer\u002FSKILL.md",[125],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,25,26,28,27],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":29},"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",[],[134,27],"stack designer",{"skillNo":136,"name":137,"nameZh":6,"description":138,"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":29},"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",[],[142],"module designer"]