tanstack-store

Manage immutable reactive state with derived values and batched updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SeanChenR/maestro-agent --skill tanstack-store-seanchenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tanstack-store
Source: https://github.com/SeanChenR/maestro-agent/tree/main/.agents/skills/tanstack-store
Command: npx skills add https://github.com/SeanChenR/maestro-agent --skill tanstack-store-seanchenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many frontend applications suffer from unpredictable state updates, excessive re-renders, and scattered state logic across components; tanstack-store provides a lightweight, immutable reactive store that centralizes state, computed values, and side effects to make state predictable and performant.

Core Features & Use Cases

  • Provides a minimal Store abstraction for immutable state, Derived for computed values, Effect for side effects, and batch for atomic updates to avoid redundant notifications.
  • Framework adapters enable seamless integration with React, Vue, Solid, Angular, and Svelte through hooks or injectables and support selector-based subscriptions and shallow equality optimizations.
  • Use case examples include building performant counters and form state, composing filter->sort->paginate derived pipelines for lists, and mounting effects for timers or external listeners with proper cleanup.

Quick Start

Create a module-level Store, mount any Derived or Effect instances, and subscribe from your UI using the adapter hook (for example useStore in React) while updating state via setState.

Frequently Asked Questions about tanstack-store

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage reactive immutable state without causing excessive re-renders in frontend applications?▼

Reactive immutable state management prevents excessive re-renders by centralizing state in a framework-agnostic store with selector-based subscriptions and shallow equality optimizations. This ensures components only update when their specific selected state slice changes.

Can I use a framework-agnostic reactive store with React, Vue, Solid, Angular, and Svelte?▼

Yes, a framework-agnostic reactive store integrates with React, Vue, Solid, Angular, and Svelte using adapter packages. These adapters provide framework-specific hooks or injectables to connect UI components directly to the central store.

What is the best way to compute derived state from a pipeline of filter, sort, and paginate operations?▼

The best way to compute derived state is using a Derived instance to map filter, sort, and paginate operations. This mounts computed values directly to the store, automatically recalculating only when upstream state dependencies change.

How do I handle side effects and external listeners with proper cleanup during state management?▼

Handle side effects and external listeners by mounting an Effect instance to the store. This manages effectful operations like timers, executing side effects on state changes and ensuring proper cleanup when the effect unmounts.

Does batching state updates help avoid redundant notifications in a reactive store?▼

Batching state updates groups multiple setState operations into atomic updates, which prevents redundant notifications. This ensures the store triggers a single predictable notification to subscribers after all state changes complete.

When should I not use a centralized reactive store for frontend state management?▼

A centralized reactive store is not suited for purely local component state or simple applications lacking complex derived computations. It adds unnecessary architectural overhead when state logic remains scattered and does not require selector subscriptions.