Frontend State Management

Use when the user asks about state management, where to put state, global state, Redux Toolkit, Zustand, Jotai, Pinia, NgRx, React Context, server state vs client state, or components re-rendering from store updates. Produces a state placement decision and store setup. Not for TanStack Query caching details (use frontend-data-fetching).

45 stars 6 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill frontend-state-management
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/state-management ~/.claude/skills/frontend-state-management

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frontend State Management

## Purpose
Choose and implement the correct state management pattern for each type of state. Server state, client state, local state, and URL state each have their own solution. Never put server state in a global store.

## Agent Protocol

### Trigger
Exact user phrases: "state management", "global state", "Redux", "Zustand", "Pinia", "NgRx", "React Context", "state architecture", "where to put state", "server state vs client state", "state library".

### Input Context
Before activating, verify:
- The framework is known (React, Vue, Angular).
- The type of state being discussed is identified (server data, UI state, form state, URL state).

### Output Artifact
No file output. Produces state architecture decision as text.

### Response Format
```
State: {description}
Type: {server/client/URL}
Storage: {local/global/shared}
Library: {specific library}
Location: {file path}
Rationale: {one sentence}
```

No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.

### Completion Criteria
- [ ] State type correctly classified (server vs client).
- [ ] Decision follows the decision tree below.
- [ ] Server state uses a server state library, NOT a global store.
- [ ] Global stores are split by domain (one store per feature, not one store for everything).
- [ ] Context is used for dependency injection, not state management.
- [ ] URL state is not duplicated in component state.
Read the full skill on GitHub

Details

Skill name
frontend-state-management
Path
skills/frontend/universal/state-management/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Frontend State Management skill do?

Use when the user asks about state management, where to put state, global state, Redux Toolkit, Zustand, Jotai, Pinia, NgRx, React Context, server state vs client state, or components re-rendering from store updates. Produces a state placement decision and store setup. Not for TanStack Query caching details (use frontend-data-fetching).

How do I install the Frontend State Management skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-state-management. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frontend State Management popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Frontend Svelte Architecture

45

j4flmao/agent-skills

Use when the user asks about Svelte 5, runes ($state, $derived, $effect, $props, $bindable), .svelte component structure, snippets, or migrating from Svelte 4 stores and $: syntax. Produces Svelte 5 component and state architecture. Not for SvelteKit routing, load functions or form actions (use sveltekit).

Frontend & Design

Frontend Solidjs Patterns

45

j4flmao/agent-skills

Use when the user asks about SolidJS forms, createResource and Suspense data fetching, SolidJS component composition, transitions or animation. Produces reusable Solid patterns for an existing app. Not for Solid project structure and reactivity basics (use frontend-solidjs-architecture).

Frontend & Design

Frontend Svelte Patterns

45

j4flmao/agent-skills

Use when the user asks about Svelte forms and bind:value, transitions and animate, use: actions or attachments, shared state in .svelte.ts modules or Svelte data-fetching patterns. Produces reusable Svelte 5 UI patterns. Not for SvelteKit load functions and form actions (use sveltekit) or rune basics (use frontend-svelte-architecture).

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.