Global State Ownership Map

Write down which store owns each piece of shared state so nothing lives in two places.

moderate Developer Experience

What it adds

A written map of every shared state domain in the app and the single store, cache, or provider that owns it.

What your agent is told to do

1
Inventory the shared state the app already holds — the signed-in user, the active workspace, the theme, the cart, the open record, the notification count — and name the one place each is read from.
2
Split the map into two columns: state that mirrors something the server owns, and state that only exists in the browser. The first is a cache with a refresh and an invalidation story; the second is genuinely local and needs a reset story instead.
3
For every server-derived entry, record what invalidates it and what clears it on sign-out or workspace switch. An entry with no documented invalidation is a bug waiting for a stale price or a stale permission.
4
Where the same value is currently held in more than one place, pick the owner, and make the other places read from it rather than keep their own copy. Deleting the duplicate is the point of the exercise.
5
Do not treat this as a rewrite. The deliverable is the map plus the removal of duplicated ownership, not a migration to a different state library — swapping the library leaves the same value in three places under new names.

Edge cases it handles

A value held in two stores will drift, and the drift shows up as a price, a permission, or an unread count that disagrees with itself between two panels on the same screen. Every domain needs exactly one owner named in the map.
Server cache and client state have different lifetimes and must not share a container. A cached list can be thrown away and refetched at any moment; a half-typed filter panel cannot, and putting them together means one policy is wrong for one of them.
Every entry needs both an invalidation rule and a reset rule, and they are not the same thing. Invalidation says when the cached copy is no longer trustworthy; reset says what happens on sign-out, workspace switch, or an impersonation session ending.
Lazily loaded parts of the app must be able to join the map without a circular import back to the code that loads them. If a store can only be reached from the root bundle, code splitting quietly pulls the whole thing back in.
State restored from storage on boot must be validated against the current shape before it is trusted, or a stale entry from an older release will be handed to code that no longer understands it.
Two tabs open on the same account share persisted state but not in-memory state, and the map must say which entries are expected to converge across tabs and which are deliberately per-tab.
Anything holding a token, a session, or personal data must be marked in the map so it is obvious what has to be cleared on sign-out.

Definition of done

Every shared state domain in the app appears in the map with exactly one named owner.
Server-derived caches and browser-only state are listed separately and stored separately.
Each cached domain documents what invalidates it and what clears it on sign-out or workspace switch.
No value is held authoritatively in two stores; duplicated copies have been removed rather than kept in sync.
Lazily loaded areas register their state without forcing their code into the initial bundle.
Entries holding credentials or personal data are marked, and all of them are cleared on sign-out.
The feature matches the existing design system.
No existing functionality is broken.

Related features

AI Cost Budgets

Multi-Model Routing

SEO Setup

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.