> nanostores
You are an expert in Nanostores, the tiny (< 1KB) state manager for framework-agnostic JavaScript. You help developers manage application state with atoms, maps, computed stores, and async data fetching — working identically across React, Vue, Svelte, Solid, Angular, and vanilla JS with lazy subscriptions that only activate when the store is actually used in a component.
curl "https://skillshub.wtf/TerminalSkills/skills/nanostores?format=md"Nanostores — Tiny State Manager
You are an expert in Nanostores, the tiny (< 1KB) state manager for framework-agnostic JavaScript. You help developers manage application state with atoms, maps, computed stores, and async data fetching — working identically across React, Vue, Svelte, Solid, Angular, and vanilla JS with lazy subscriptions that only activate when the store is actually used in a component.
Core Capabilities
Atoms and Maps
// stores/auth.ts — Framework-agnostic stores
import { atom, map, computed, onMount } from "nanostores";
// Atom: single value
export const $isAuthenticated = atom(false);
export const $theme = atom<"light" | "dark">("light");
// Map: object with per-key subscriptions
export const $user = map<{ name: string; email: string; plan: "free" | "pro" }>({
name: "",
email: "",
plan: "free",
});
// Computed: derived state
export const $isPro = computed($user, (user) => user.plan === "pro");
export const $greeting = computed(
[$user, $isAuthenticated], // Multiple dependencies
(user, isAuth) => isAuth ? `Welcome, ${user.name}!` : "Please sign in",
);
// Lifecycle: runs when first subscriber appears, cleanup when last unsubscribes
onMount($user, () => {
const unsubscribe = authService.onAuthChange((userData) => {
if (userData) {
$user.set(userData);
$isAuthenticated.set(true);
} else {
$user.set({ name: "", email: "", plan: "free" });
$isAuthenticated.set(false);
}
});
return unsubscribe; // Cleanup function
});
// Update
$user.setKey("plan", "pro"); // Per-key update (triggers only plan subscribers)
$theme.set("dark");
React Integration
import { useStore } from "@nanostores/react";
import { $user, $isPro, $greeting } from "../stores/auth";
function UserProfile() {
const user = useStore($user);
const isPro = useStore($isPro);
const greeting = useStore($greeting);
return (
<div>
<h1>{greeting}</h1>
<p>{user.email}</p>
{isPro && <span className="badge">PRO</span>}
<button onClick={() => $user.setKey("plan", "pro")}>Upgrade</button>
</div>
);
}
Async Data (with @nanostores/query)
// stores/api.ts — Data fetching with caching
import { nanoquery } from "@nanostores/query";
const [createFetcherStore, createMutatorStore] = nanoquery({
fetcher: (url: string) => fetch(url).then((r) => r.json()),
});
export const $projects = createFetcherStore<Project[]>(["/api/projects"]);
export const $currentProject = createFetcherStore<Project>(
["/api/projects/", $projectId], // Reactive key — refetches when $projectId changes
);
export const $createProject = createMutatorStore<Project>(
async ({ data }) => {
const res = await fetch("/api/projects", {
method: "POST",
body: JSON.stringify(data),
});
return res.json();
},
{ invalidates: ["/api/projects"] }, // Auto-invalidate projects list
);
// React component using async stores
import { useStore } from "@nanostores/react";
import { $projects, $createProject } from "../stores/api";
function ProjectList() {
const { data: projects, loading, error } = useStore($projects);
if (loading) return <Spinner />;
if (error) return <Error message={error.message} />;
return (
<ul>
{projects?.map((p) => <li key={p.id}>{p.name}</li>)}
<button onClick={() => $createProject.mutate({ data: { name: "New Project" } })}>
Add Project
</button>
</ul>
);
}
Installation
npm install nanostores
npm install @nanostores/react # React binding
# Or: @nanostores/vue | @nanostores/svelte | @nanostores/solid | @nanostores/angular
npm install @nanostores/query # Async data fetching (optional)
Best Practices
- Framework-agnostic — Define stores once; use in React, Vue, Svelte, or any framework simultaneously
- Lazy subscriptions — Stores only compute/fetch when subscribed; zero cost for unused stores
- $ prefix convention — Name stores with
$prefix ($user,$theme); distinguishes stores from regular variables - Map per-key updates — Use
setKey()for map stores; only subscribers of that key re-render - Computed for derived state — Use
computed()instead of manual subscriptions; auto-tracks dependencies - onMount lifecycle — Initialize data/subscriptions in
onMount; auto-cleanup when no subscribers remain - Tiny bundle — Core is 298 bytes; keeps your app fast, especially for micro-frontends
- @nanostores/query — Use for server data; built-in caching, invalidation, and reactive refetching
> related_skills --same-repo
> zustand
You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.
> zoho
Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.
> zod
You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.
> zipkin
Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.