Individual skill

jotai-pro

Manage atomic React state with Jotai: atoms, derived atoms, async atoms, and scoped providers. Use for granular, bottom-up state in React.

skills/jotai-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Jotai Pro

A practical guide to Jotai: atomic state management for React — tiny atoms composed bottom-up, derived atoms, async atoms, and the patterns that make global state feel local.

## Overview

Jotai inverts the store model: instead of one big store you slice, you define **atoms** — minimal units of state — and compose them. Components subscribe to exactly the atoms they use, so re-renders are surgically precise. State can live colocated with features yet be shared globally. It's "React state, but shareable": `useState`-like ergonomics with global reach.

## When to use

- Granular state where different components need different pieces (avoids over-rendering).
- Bottom-up state: start local, lift to shared only when needed.
- Derived state (computed from other atoms) without selector boilerplate.
- Async state (data fetching) as atoms with Suspense integration.