[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F0C8YPJZ557SA6GZMSHAK":3,"skill-same:01M78F0C8YPJZ557SA6GZMSHAK":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},"01M78F0C8YPJZ557SA6GZMSHAK","state-management",null,"Choose and implement state ownership, synchronization, subscriptions and mutation recovery in frontend applications.","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\u002Fstate-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: state-management\ndescription: Choose and implement state ownership, synchronization,\n  subscriptions and mutation recovery in frontend applications.\n---\n\n# state-management\n\n## Overview\n\nChoose and implement state ownership, synchronization, subscriptions and mutation recovery in frontend applications. Match guidance to the actual task and project; this document does not implement an automatic enforcer.\n\n## When to Use\n\nA state ownership, synchronization or update problem is in scope. Respect the existing React state\u002Fdata stack rather than automatically introducing Zustand or TanStack Query.\n\n## Rules & Patterns\n\nIdentify authoritative state, derived values, URL state, transient UI state and server data. Keep each source of truth understandable and avoid unnecessary duplicate writable copies.\n\nUse the project's existing data\u002Fcache utilities where suitable. Server data can be managed by a framework, query library or another deliberate architecture; it does not universally belong in one package.\n\nSubscribe to the data actually needed and inspect rerender behavior before optimizing. Use selectors\u002Fequality APIs compatible with the installed version. A centralized key factory may help larger caches but is not required for every query.\n\nDefine invalidation, cancellation and stale-response behavior. When optimistic UI is appropriate, handle failed and overlapping mutations without restoring stale data over a newer successful change.\n\nScope caches and stores to the right user\u002Frequest boundary. Shared client or server state must not leak identity or tenant-specific data across sessions.\n\n## Code Examples\n\nFor a filterable catalog, determine which filters belong in the URL, which state is local and which results come from the server. For optimistic editing, test overlapping updates and failure recovery rather than only a successful click.\n\nSee [EXAMPLES.md](EXAMPLES.md) for scoped scenarios and evidence boundaries.\n\n## Validation Checklist\n\n- [ ] Exercise stale responses, relevant concurrency, invalidation and reset\u002Fsession boundaries.\n- [ ] Verify subscriptions and persisted effects at the appropriate layer.\n\n## Common Mistakes\n\nIntroducing a global store for a local toggle; forcing a specific library; restoring obsolete optimistic snapshots; using global server request state.\n\n## Integration Notes\n\nOptional companion guidance: react, typescript, webapp-testing. Use it only when relevant and available; the skill does not install tools or authorize external actions.\n","# state-management\n\n## Overview\n\nChoose and implement state ownership, synchronization, subscriptions and mutation recovery in frontend applications. Match guidance to the actual task and project; this document does not implement an automatic enforcer.\n\n## When to Use\n\nA state ownership, synchronization or update problem is in scope. Respect the existing React state\u002Fdata stack rather than automatically introducing Zustand or TanStack Query.\n\n## Rules & Patterns\n\nIdentify authoritative state, derived values, URL state, transient UI state and server data. Keep each source of truth understandable and avoid unnecessary duplicate writable copies.\n\nUse the project's existing data\u002Fcache utilities where suitable. Server data can be managed by a framework, query library or another deliberate architecture; it does not universally belong in one package.\n\nSubscribe to the data actually needed and inspect rerender behavior before optimizing. Use selectors\u002Fequality APIs compatible with the installed version. A centralized key factory may help larger caches but is not required for every query.\n\nDefine invalidation, cancellation and stale-response behavior. When optimistic UI is appropriate, handle failed and overlapping mutations without restoring stale data over a newer successful change.\n\nScope caches and stores to the right user\u002Frequest boundary. Shared client or server state must not leak identity or tenant-specific data across sessions.\n\n## Code Examples\n\nFor a filterable catalog, determine which filters belong in the URL, which state is local and which results come from the server. For optimistic editing, test overlapping updates and failure recovery rather than only a successful click.\n\nSee [EXAMPLES.md](EXAMPLES.md) for scoped scenarios and evidence boundaries.\n\n## Validation Checklist\n\n- [ ] Exercise stale responses, relevant concurrency, invalidation and reset\u002Fsession boundaries.\n- [ ] Verify subscriptions and persisted effects at the appropriate layer.\n\n## Common Mistakes\n\nIntroducing a global store for a local toggle; forcing a specific library; restoring obsolete optimistic snapshots; using global server request state.\n\n## Integration Notes\n\nOptional companion guidance: react, typescript, webapp-testing. 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\u002Fstate-management",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 state-management",{"tool":39,"command":40},"bunx","bunx skills add kok-o\u002Fcontextos-agents --skill state-management",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kok-o\u002Fcontextos-agents --skill state-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fstate-management\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"EXAMPLES.md","REFERENCE","参考文档",645,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fstate-management\u002FEXAMPLES.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"skill.yaml",400,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fstate-management\u002Fskill.yaml",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"TROUBLESHOOTING.md",325,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fstate-management\u002FTROUBLESHOOTING.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"VALIDATION.json",336,"https:\u002F\u002Fgithub.com\u002Fkok-o\u002Fcontextos-agents\u002Fblob\u002Fmain\u002Fcatalog\u002Fskills\u002Fstate-management\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",[],[]]