add-atom

Add Jotai atoms with type definitions, registry, and Store API access.

3|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/Ariedam64/Gemini --skill add-atom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-atom
Source: https://github.com/Ariedam64/Gemini/tree/main/.claude/skills/add-atom
Command: npx skills add https://github.com/Ariedam64/Gemini --skill add-atom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of adding a new Jotai atom by generating type definitions, updating the atom registry, and exposing the atom via the Store API, reducing boilerplate and ensuring consistency across the codebase.

Core Features & Use Cases

  • Automatic type definitions: Adds TypeScript interfaces and AtomTypeMap entries for the new atom.
  • Registry integration: Registers the atom in the central lookup for easy access.
  • Store API exposure: Provides read, write, and subscribe capabilities through the Store API.
  • Guided implementation: Includes a structured workflow to define state, register, export, and import the atom across modules.

Quick Start

Create a new <AtomName> atom by defining its state, registering it in the lookup, and exposing it via the Store API.

Frequently Asked Questions about add-atom

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

FAQPage Schema
How do I add a new Jotai atom with TypeScript types and Store API access?

To add a new Jotai atom, define its state, generate TypeScript interfaces and AtomTypeMap entries, register it in the central lookup, and expose read, write, and subscribe capabilities via the Store API.

What is the best way to manage Jotai atom registration across a large codebase?

The best way to manage Jotai atom registration is using a centralized lookup registry that ensures consistent atom keys, type-safe definitions, and public access to read, write, and subscribe functionality across modules.

Do I need to manually update the atom registry when expanding my reactive state?

You do not need to manually update the atom registry when expanding reactive state. The process automates updating atom keys and the registry, ensuring type-safe atom creation and seamless Store API integration.

Can I expose Jotai read, write, and subscribe functionality through a central Store API?

You can expose Jotai read, write, and subscribe functionality through a central Store API. This integration provides public access to the reactive state while maintaining type-safe atom definitions and centralized lookup.

Why does my Jotai state system need an AtomTypeMap for new atoms?

Your Jotai state system needs an AtomTypeMap to ensure type-safe atom creation. It automatically adds TypeScript interfaces for the new atom, reducing boilerplate and ensuring consistent type definitions across the application.

When should I not use a centralized registry for Jotai state management?

You should not use a centralized registry for Jotai state management if your application requires only isolated, local component state without the need for cross-module lookup, public Store API access, or centralized read, write, and subscribe capabilities.