zustand

vercel-labs/json-render · updated Apr 8, 2026

$npx skills add https://github.com/vercel-labs/json-render --skill zustand
0 commentsdiscussion
summary

Zustand adapter for json-render's StateStore interface. Wire a Zustand vanilla store as the state backend for json-render.

skill.md

@json-render/zustand

Zustand adapter for json-render's StateStore interface. Wire a Zustand vanilla store as the state backend for json-render.

Installation

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.

Usage

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>

With a Nested Slice

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 }),
});

API

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.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.570 reviews
  • Dhruvi Jain· Dec 28, 2024

    I recommend zustand for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Evelyn Thomas· Dec 28, 2024

    We added zustand from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hana Huang· Dec 24, 2024

    Keeps context tight: zustand is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sakura White· Dec 24, 2024

    Registry listing for zustand matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chinedu Flores· Dec 20, 2024

    zustand reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Hiroshi Yang· Dec 16, 2024

    zustand has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Liam Desai· Dec 8, 2024

    Useful defaults in zustand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ira Li· Nov 27, 2024

    zustand is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Oshnikdeep· Nov 19, 2024

    zustand fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hiroshi Liu· Nov 15, 2024

    zustand reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 70

1 / 7