Zustand adapter for json-render's StateStore interface. Wire a Zustand vanilla store as the state backend for json-render.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionzustandExecute the skills CLI command in your project's root directory to begin installation:
Fetches zustand from vercel-labs/json-render and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate zustand. Access via /zustand in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
14.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14.0K
stars
Zustand adapter for json-render's StateStore interface. Wire a Zustand vanilla store as the state backend for json-render.
npm install @json-render/zustand @json-render/core @json-render/react zustand
Requires Zustand v5+. Zustand v4 is not supported due to breaking API changes in the vanilla store interface.
import { createStore } from "zustand/vanilla";
import { zustandStateStore } from "@json-render/zustand";
import { StateProvider } from "@json-render/react";
// 1. Create a Zustand vanilla store
const bearStore = createStore(() => ({
count: 0,
name: "Bear",
}));
// 2. Create the json-render StateStore adapter
const store = zustandStateStore({ store: bearStore });
// 3. Use it
<StateProvider store={store}>
{/* json-render reads/writes go through Zustand */}
</StateProvider>
const appStore = createStore(() => ({
ui: { count: 0 },
auth: { token: null },
}));
const store = zustandStateStore({
store: appStore,
selector: (s) => s.ui,
updater: (next, s) => s.setState({ ui: next }),
});
zustandStateStore(options)Creates a StateStore backed by a Zustand store.
| Option | Type | Required | Description |
|---|---|---|---|
store |
StoreApi<S> |
Yes | Zustand vanilla store (from createStore in zustand/vanilla) |
selector |
(state) => StateModel |
No | Select the json-render slice. Defaults to entire state. |
updater |
(nextState, store) => void |
No | Apply next state to the store. Defaults to shallow merge. Override for nested slices, or use (next, s) => s.setState(next, true) for full replacement. |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend zustand for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added zustand from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: zustand is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for zustand matched our evaluation — installs cleanly and behaves as described in the markdown.
zustand reduced setup friction for our internal harness; good balance of opinion and flexibility.
zustand has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in zustand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
zustand is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
zustand fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
zustand reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 70