Frontend state data flow
Skill jukrap/ai-agent-playbook/skills/frontend/frontend-state-data-flow
Use when changing frontend state ownership, server/client cache behavior, data fetching, optimistic updates, URL state, loading/error/empty states, or stale UI bugs.From its SKILL.md
npx -y skills add jukrap/ai-agent-playbook --skill frontend-state-data-flowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.0 KB, 170 tokens by cl100k_base, as published. Nobody here has run it
Frontend State Data Flow
Use this as the primary frontend skill for state ownership and data consistency changes.
Workflow
- Identify the source of truth, derived state, server cache, local UI state, URL state, and mutation boundary.
- Trace loading, empty, error, retry, cancellation, race, stale-data, and optimistic-update paths before editing.
- Prefer the repository's existing state/data primitives over adding another cache or global store.
- Verify the user workflow across first load, refresh, mutation success/failure, navigation, and back/forward behavior.
Reference
Read references/state-ownership.md for local, derived, shared, and URL state decisions.
Read references/server-client-cache-boundaries.md for server cache, client cache, invalidation, optimistic updates, and stale data review.
What ships with it: 2 files
3.8 KB alongside SKILL.md