sfnext-state-management
Manage client-side state in Storefront Next using React context providers and feature-level Zustand stores. Use when handling basket/auth UI state, creating extension stores (for example store locator), or syncing client-visible state after server mutations. NOT for server-side data loading — see sfnext-data-fetching for loader patterns.
What this skill does
# State Management Skill
This skill covers client-side state management in Storefront Next with server-first data loading.
## Overview
Storefront Next keeps business data on the server (`loader`/`action`) and uses client state for UX continuity. In practice, app-wide state is commonly exposed through providers (for example auth/basket), while complex extension-specific state can use Zustand.
| State Type | Mechanism | Example |
| --------------------- | ------------------------------ | ------------------------------------------------------ |
| Server data | React Router `loader` | Product details, category listings |
| App-wide client state | React context providers | Session display state, basket snapshot/hydration state |
| Feature client state | Zustand store | Store locator modal/search state |
| Mutations | React Router `action` (server) | Add to cart, update profile |
## Zustand Store Pattern (Feature-Level)
```typescript
// src/extensions/store-locator/stores/store-locator-store.ts
import {createStore} from 'zustand/vanilla';
type StoreLocatorState = {
isOpen: boolean;
mode: 'input' | 'device';
selectedStoreInfo: SelectedStoreInfo | null;
};
type StoreLocatorActions = {
open: () => void;
close: () => void;
setSelectedStoreInfo: (info: SelectedStoreInfo) => void;
};
type StoreLocatorStore = StoreLocatorState & StoreLocatorActions;
export const createStoreLocatorStore = (init?: Partial<StoreLocatorState>) => {
return createStore<StoreLocatorStore>()((set) => ({
isOpen: false,
mode: 'input',
selectedStoreInfo: init?.selectedStoreInfo ?? null,
open: () => set({isOpen: true}),
close: () => set({isOpen: false}),
setSelectedStoreInfo: (selectedStoreInfo) => set({selectedStoreInfo}),
}));
};
```
## Context Integration
Expose app-level state to components via providers/hooks:
```typescript
import { useBasket, useBasketSnapshot } from '@/providers/basket';
// In components
function CartIcon() {
const basket = useBasket();
const snapshot = useBasketSnapshot();
const itemCount =
basket?.productItems?.length ??
snapshot?.uniqueProductCount ??
0;
return <Badge count={itemCount} />;
}
```
## Post-Mutation Sync Pattern
Keep mutations on the server and update request-context resources there:
```typescript
import {data} from 'react-router';
import {getBasket, updateBasketResource} from '@/middlewares/basket.server';
export async function action({request, context}: ActionFunctionArgs) {
const formData = await request.formData();
const productId = formData.get('productId') as string;
const basketResource = await getBasket(context);
const clients = createApiClients(context);
const {data: updatedBasket} = await clients.basket.addItemToBasket({
params: {path: {basketId: basketResource.current?.basketId ?? ''}},
body: {productId, quantity: 1},
});
// Sync basket resource in request context for current response/revalidation flow
updateBasketResource(context, updatedBasket);
return data({success: true, basket: updatedBasket});
}
```
## Best Practices
1. **Server-first data** — Load/mutate commerce data with `loader`/`action`
2. **Provider-first app state** — Use providers for shared basket/auth UI state
3. **Scoped Zustand usage** — Use Zustand for feature-local complexity (typically extensions)
4. **Sync in server actions** — Update server basket/auth resources inside `action` handlers
5. **Keep state minimal** — Store only what cannot be derived cheaply
## When to Use Each Mechanism
| Scenario | Use |
| ----------------------------- | -------------------------------------------------------- |
| Product data on page load | `loader` |
| Shopping cart badge count | Basket provider hooks (`useBasket`, `useBasketSnapshot`) |
| Complex extension UI workflow | Zustand store |
| Search results | `loader` |
| Add to cart | Server `action` + resource update |
## Related Skills
- `storefront-next:sfnext-data-fetching` - Server-side data loading with loaders (NOT client state)
- `storefront-next:sfnext-authentication` - Auth state management
- `storefront-next:sfnext-components` - Using store data in components
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.