[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TKZ3P2DE6RFADC8XNRFSZ":3,"skill-same:01M79TKZ3P2DE6RFADC8XNRFSZ":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TKZ3P2DE6RFADC8XNRFSZ","redux-toolkit-architect",null,"Architect-level Redux Toolkit guidance — slice boundaries and normalization, thunk\u002FRTK Query separation, selector discipline, middleware ownership, and the store-shape decisions that decide whether Redux helps or becomes a global mutable bag. Use when a React app needs a real global store.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fredux-toolkit-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: redux-toolkit-architect\ndescription: Architect-level Redux Toolkit guidance — slice boundaries and normalization, thunk\u002FRTK Query separation, selector discipline, middleware ownership, and the store-shape decisions that decide whether Redux helps or becomes a global mutable bag. Use when a React app needs a real global store.\nlicense: MIT\ncompatibility: Redux Toolkit 2.x; React 18+\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fredux-toolkit-architect\n  crusor-origin: original\n  crusor-sources: \"redux-toolkit.js.org; redux.js.org\u002Fstyle-guide\"\n  crusor-triggers: \"redux, rtk, redux toolkit, redux slice, rtk query, slices, createasyncthunk\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Redux Toolkit Architect\n\nRedux is **not** a state cache; it is a shared, inspectable event log. Adopt it\nwhen several unrelated parts of the app must agree on the same truth.\n\n## When to use\n\n- Cross-cutting state with many independent readers\u002Fwriters (auth, cart,\n  editor documents).\n- Time-travel debugging or action auditing is a requirement.\n- Server state needs a cache too — then RTK Query, not hand-written thunks.\n\n## When NOT to use\n\n- Server data only (TanStack Query \u002F RTK Query alone).\n- One or two components sharing a value (context or lift state).\n- Modal flags and hover state — that is component state.\n\n## Decision 1 — Slices are contexts, not entities\n\n- One slice per **business context** (`cart`, `checkout`, `auth`), never per\n  entity or per component.\n- State is normalized (`entities: {byId, ids}`) when lists are long or shared.\n- Slice reducers are pure and small; derived values are selectors, not state.\n- Cross-slice updates happen in middleware\u002Flisteners, not by importing another\n  slice's reducers.\n\n## Decision 2 — Server state vs client state\n\n| Concern | Tool |\n|---|---|\n| remote data, caching, refetch | RTK Query |\n| local mutations of that data | optimistic updates on the cache, not a copy in a slice |\n\nNever mirror server data into a slice — that is the classic divergence bug.\n\n## Decision 3 — Selectors\n\n- Selectors live with the slice, are typed, and take `RootState`.\n- Components subscribe to the narrowest slice; `useSelector` returning new\n  objects every call causes re-render storms — use memoised selectors.\n- Derived\u002Fcomputed lists are memoised selectors, not `useEffect` + `useState`.\n\n## Decision 4 — Side effects\n\n- Thunks for command-like flows (submit → dispatch → invalidate).\n- Listeners for reacting to actions (analytics, persistence, cross-slice rules).\n- Side effects do not live in reducers, ever.\n- Persistence is explicit (`redux-persist` allowlist), never \"the whole store\".\n\n## Decision 5 — Store shape review\n\n- Flat where possible; nesting only where it mirrors the domain.\n- No functions, class instances, or Dates-as-objects in state (serialisability\n  is what makes devtools and persistence work).\n- Devtools in dev only; production middleware minimal.\n\n## Failure modes at scale\n\n- A `ui` slice holding every modal, tab and hover — the store becomes a dump.\n- Server data copied into a slice → stale everywhere after a refetch.\n- `useSelector(s => ({a: s.a, b: s.b}))` → re-render on every action.\n- 40 slices with circular listener dependencies.\n- Redux for everything, and now nothing can be tested without a store.\n\n## Verification receipts\n\n1. Store shape diagram reviewed; each slice names its owning context.\n2. Render-count check on a hot component under unrelated actions.\n3. Persistence allowlist reviewed (no tokens beyond what is needed).\n4. Reducer purity audit: no side effects, no non-serialisable values.\n5. A page can be tested with a minimal store (not the full app store).\n","# Redux Toolkit Architect\n\nRedux is **not** a state cache; it is a shared, inspectable event log. Adopt it\nwhen several unrelated parts of the app must agree on the same truth.\n\n## When to use\n\n- Cross-cutting state with many independent readers\u002Fwriters (auth, cart,\n  editor documents).\n- Time-travel debugging or action auditing is a requirement.\n- Server state needs a cache too — then RTK Query, not hand-written thunks.\n\n## When NOT to use\n\n- Server data only (TanStack Query \u002F RTK Query alone).\n- One or two components sharing a value (context or lift state).\n- Modal flags and hover state — that is component state.\n\n## Decision 1 — Slices are contexts, not entities\n\n- One slice per **business context** (`cart`, `checkout`, `auth`), never per\n  entity or per component.\n- State is normalized (`entities: {byId, ids}`) when lists are long or shared.\n- Slice reducers are pure and small; derived values are selectors, not state.\n- Cross-slice updates happen in middleware\u002Flisteners, not by importing another\n  slice's reducers.\n\n## Decision 2 — Server state vs client state\n\n| Concern | Tool |\n|---|---|\n| remote data, caching, refetch | RTK Query |\n| local mutations of that data | optimistic updates on the cache, not a copy in a slice |\n\nNever mirror server data into a slice — that is the classic divergence bug.\n\n## Decision 3 — Selectors\n\n- Selectors live with the slice, are typed, and take `RootState`.\n- Components subscribe to the narrowest slice; `useSelector` returning new\n  objects every call causes re-render storms — use memoised selectors.\n- Derived\u002Fcomputed lists are memoised selectors, not `useEffect` + `useState`.\n\n## Decision 4 — Side effects\n\n- Thunks for command-like flows (submit → dispatch → invalidate).\n- Listeners for reacting to actions (analytics, persistence, cross-slice rules).\n- Side effects do not live in reducers, ever.\n- Persistence is explicit (`redux-persist` allowlist), never \"the whole store\".\n\n## Decision 5 — Store shape review\n\n- Flat where possible; nesting only where it mirrors the domain.\n- No functions, class instances, or Dates-as-objects in state (serialisability\n  is what makes devtools and persistence work).\n- Devtools in dev only; production middleware minimal.\n\n## Failure modes at scale\n\n- A `ui` slice holding every modal, tab and hover — the store becomes a dump.\n- Server data copied into a slice → stale everywhere after a refetch.\n- `useSelector(s => ({a: s.a, b: s.b}))` → re-render on every action.\n- 40 slices with circular listener dependencies.\n- Redux for everything, and now nothing can be tested without a store.\n\n## Verification receipts\n\n1. Store shape diagram reviewed; each slice names its owning context.\n2. Render-count check on a hot component under unrelated actions.\n3. Persistence allowlist reviewed (no tokens beyond what is needed).\n4. Reducer purity audit: no side effects, no non-serialisable values.\n5. A page can be tested with a minimal store (not the full app store).\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fredux-toolkit-architect","website-architect","original","redux-toolkit.js.org; redux.js.org\u002Fstyle-guide","redux, rtk, redux toolkit, redux slice, rtk query, slices, createasyncthunk","2026-10-30","Redux Toolkit 2.x; React 18+","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fredux-toolkit-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill redux-toolkit-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill redux-toolkit-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill redux-toolkit-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fredux-toolkit-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]