[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F0KE5BCXT1DEX5DMPA2HV":3,"skill-same:01M78F0KE5BCXT1DEX5DMPA2HV":65},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78F0KE5BCXT1DEX5DMPA2HV","system-design",null,"Make proportionate architecture decisions using actual requirements, boundaries, workloads and operational constraints.","kok-o\u002Fcontextos-agents","kok-o","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F173567992?v=4","01M78EV59TFZZ32P2FNN27BHW5","Nurkhan Esenbek","01M78EV5AFG9E8PEC10N3W7JNH",10,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: system-design\ndescription: Make proportionate architecture decisions using actual\n  requirements, boundaries, workloads and operational constraints.\n---\n\n# system-design\n\n## Overview\n\nMake proportionate architecture decisions using actual requirements, boundaries, workloads and operational constraints. Match guidance to the actual task and project; this document does not implement an automatic enforcer.\n\n## When to Use\n\nA consequential architecture choice, scaling issue or system boundary is in scope. A routine backend edit does not require a distributed-systems checklist.\n\n## Rules & Patterns\n\nStart with the actual product requirements, existing architecture, data lifecycle, workload and failure tolerance. Label estimates and unknowns rather than inventing scale or latency targets.\n\nChoose the simplest design that meets those constraints. Monoliths, modules, queues, caches, service splits and partitions each have operational and consistency costs; none is a default badge of quality.\n\nIdentify identity\u002Fauthorization boundaries, consistency invariants, failure paths and ownership. Discuss CAP in the context of network partitions and the actual consistency\u002Favailability requirements, not as a universal instruction to pick any two labels.\n\nFor serverless or long-lived processes, inspect connection, cold-start and resource lifecycle behavior. Safe client\u002Fpool reuse may belong at process scope; request-specific state does not. Verify provider and framework limits before prescribing a runtime or connection strategy.\n\nRecord meaningful tradeoffs and verification plans. Introduce extra layers, ADRs or diagrams where they clarify the change, rather than requiring them before any line of code.\n\n## Code Examples\n\nFor a slow small backend, inspect the query and request path before proposing sharding or microservices. For a real service split, define data ownership, contracts, failure recovery and operational responsibility.\n\nSee [EXAMPLES.md](EXAMPLES.md) for scoped scenarios and evidence boundaries.\n\n## Validation Checklist\n\n- [ ] Trace requirements to the proposed behavior and relevant failure scenarios.\n- [ ] Separate source inspection, capacity estimates and measured production evidence.\n\n## Common Mistakes\n\nDesigning for invented scale; mandatory Redis\u002Fmicroservices; blanket bans on safe module-scope clients; declaring a diagram a deployed system.\n\n## Integration Notes\n\nOptional companion guidance: decisions, database, api-design. Use it only when relevant and available; the skill does not install tools or authorize external actions.\n","# system-design\n\n## Overview\n\nMake proportionate architecture decisions using actual requirements, boundaries, workloads and operational constraints. Match guidance to the actual task and project; this document does not implement an automatic enforcer.\n\n## When to Use\n\nA consequential architecture choice, scaling issue or system boundary is in scope. A routine backend edit does not require a distributed-systems checklist.\n\n## Rules & Patterns\n\nStart with the actual product requirements, existing architecture, data lifecycle, workload and failure tolerance. Label estimates and unknowns rather than inventing scale or latency targets.\n\nChoose the simplest design that meets those constraints. Monoliths, modules, queues, caches, service splits and partitions each have operational and consistency costs; none is a default badge of quality.\n\nIdentify identity\u002Fauthorization boundaries, consistency invariants, failure paths and ownership. Discuss CAP in the context of network partitions and the actual consistency\u002Favailability requirements, not as a universal instruction to pick any two labels.\n\nFor serverless or long-lived processes, inspect connection, cold-start and resource lifecycle behavior. Safe client\u002Fpool reuse may belong at process scope; request-specific state does not. Verify provider and framework limits before prescribing a runtime or connection strategy.\n\nRecord meaningful tradeoffs and verification plans. Introduce extra layers, ADRs or diagrams where they clarify the change, rather than requiring them before any line of code.\n\n## Code Examples\n\nFor a slow small backend, inspect the query and request path before proposing sharding or microservices. For a real service split, define data ownership, contracts, failure recovery and operational responsibility.\n\nSee [EXAMPLES.md](EXAMPLES.md) for scoped scenarios and evidence boundaries.\n\n## Validation Checklist\n\n- [ ] Trace requirements to the proposed behavior and relevant failure scenarios.\n- [ ] Separate source inspection, capacity estimates and measured production evidence.\n\n## Common Mistakes\n\nDesigning for invented scale; mandatory Redis\u002Fmicroservices; blanket bans on safe module-scope clients; declaring a diagram a deployed system.\n\n## Integration Notes\n\nOptional companion guidance: decisions, database, api-design. Use it only when relevant and available; the skill does not install tools or authorize external actions.\n",{"name":5,"description":7},"main","7fb8666fa73d9b8f9707a47505553f0f1af474ea","catalog\u002Fskills\u002Fsystem-design",1,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents","https:\u002F\u002Fgithub.com\u002Fkok-o","nurkhan.space","Software engineer focused on AI tooling and ML infrastructure. \r\n\r\n","2026-11-11 02:56:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add kok-o\u002Fcontextos-agents --skill system-design",{"tool":39,"command":40},"bunx","bunx skills add kok-o\u002Fcontextos-agents --skill system-design",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kok-o\u002Fcontextos-agents --skill system-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"EXAMPLES.md","REFERENCE","参考文档",616,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002FEXAMPLES.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"skill.yaml",399,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002Fskill.yaml",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"TROUBLESHOOTING.md",322,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002FTROUBLESHOOTING.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"VALIDATION.json",198,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fsystem-design\u002FVALIDATION.json",[66,73,80,87,94,100],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78F25RVZVK4KYXZZKW42DZH","scoped-frontend","Frontend component design and React guidelines","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fadapter-contracts\u002F.agents\u002Fcore\u002Fskills\u002Fscoped-frontend\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78F23169Y0R4CB819166JZP","scoped-backend","Backend service architecture and API endpoints","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fadapter-contracts\u002F.agents\u002Fcore\u002Fskills\u002Fscoped-backend\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78F1ZSMZAMY7S2ECNB065QR","engineering-workflow","Core software engineering lifecycle workflow","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fadapter-contracts\u002F.agents\u002Fcore\u002Fskills\u002Fengineering-workflow\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78F1WWD36GB27TAS4TSM3MJ","team-auth","ContextOS skill for team-auth","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fscripts\u002Freadme-gif\u002Fevidence\u002Fexports\u002Fcodex\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M78F1TEZPGE4NCTPZRC7Q1KK","claude","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fscripts\u002Freadme-gif\u002Fevidence\u002Fexports\u002Fclaude\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M78F1Q8JG229RWD6ESVKT9R9","team-order","Team conventions for createOrder and item name normalization in src\u002Forder.ts.","https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fexamples\u002Freadme-demo\u002Fteam-order\u002FSKILL.md",[],[]]