Find guidance for shaping data in Zustand stores, including list and detail types, ID-keyed maps, reducers, and shared type sources. It also points to conventions for replica-backed domain data and clarifies that the zustand skill is the automatic entry for store work.
Explicit compatibility entry for Zustand data-shape guidance.
Run score Not tested
See how to installThis skill points to guidance for deciding how data should be structured in Zustand stores. For list and detail types, ID-keyed maps, reducers, and shared type sources, it directs you to the related zustand data structures guide. It also describes a convention for domains whose reads go through local-replica: use ID-keyed <domain>Map views, add a <domain>Replica field to track the replicated state of each view, and keep resources in a neighboring projection.ts file.
Use it when considering how to represent list and detail data in a Zustand store, or when checking the structure of a domain that uses replicated data. For store work, the zustand skill is the automatic entry point; this skill is an explicit guide to the data-structure details.
For details, see ../zustand/references/data-structures.md and the zustand skill section on “replica-backed server data.”
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Read Zustand data structures for
list/detail types, maps, reducers and shared type sources. The zustand skill
is the automatic entry for store work.
A domain whose reads go through local-replica keeps its data in the same
id-keyed <domain>Map views, plus one <domain>Replica bookkeeping field per
view; its resources live in a sibling projection.ts. See
replica-backed server data.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use this skill to verify a delivery by exercising the real product through a suitable surface such as a CLI, web app, desktop app, or iOS Simulator. It helps create or find a verification plan, capture evidence, and publish an acceptance report.
Use this skill to add an AI model provider to LobeHub across runtime integration, model cards, settings, branding, documentation, and acceptance checks. It also covers provider documentation updates and distinguishes new providers from models added to an existing provider.
Use this skill to add a server-side environment variable that sets a default for a user setting. It walks through validation, server configuration and store merging, plus updating the example environment file and self-hosting documentation.
Provides guidance for registering hooks around an agent’s execution steps, tool calls, human approvals, context compression, and sub-agent calls. Hooks can observe events, supply local mock tool results, or use webhooks to allow or deny tool results under configured policies.
Build event-driven background workflows for agents by defining sources, interpreting them as signals, and running actions through policies. It also guides asynchronous handoffs, deduplication, scoped execution, completion receipts, and observability.
Use this skill to run end-to-end acceptance checks for bot channels in real desktop chat apps. It drives apps such as Discord, Slack, Telegram, WeChat, Lark, and QQ to send a message, wait for a response, and capture the result.