react-synapse
A React state management library using Preact Signals with fine-grained reactivity. Use it when you need global state without providers, minimal re-renders, or immutable updates via draft mutations. Works with React 18+.
Best use case
react-synapse is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
A React state management library using Preact Signals with fine-grained reactivity. Use it when you need global state without providers, minimal re-renders, or immutable updates via draft mutations. Works with React 18+.
Teams using react-synapse should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/react-synapse/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How react-synapse Compares
| Feature / Agent | react-synapse | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
A React state management library using Preact Signals with fine-grained reactivity. Use it when you need global state without providers, minimal re-renders, or immutable updates via draft mutations. Works with React 18+.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Overview
React-synapse provides fine-grained reactive state management for React using Preact Signals. It offers a global singleton store pattern that requires no providers, supports draft mutations via Mutative, and minimizes re-renders by tracking only accessed values.
## When to use
- Building React applications needing global state without Context/Providers
- Fine-grained reactivity where components re-render only when accessed values change
- Complex nested state updates requiring immutable patterns with mutable syntax
- Sharing state between components without prop drilling
## Core API patterns
### String key access: `[value, setter]`
Use when you need both the value and a setter function for updates.
```jsx
import { createSignalStore } from 'react-synapse';
const { useStore } = createSignalStore({ count: 0, user: null });
function Counter() {
const [count, setCount] = useStore('count');
return (
<button onClick={() => setCount(c => c + 1)}>
Count: {count}
</button>
);
}
```
### Selector for derived state: `value`
Use when you only need to read values, especially computed/derived values.
```jsx
function CartSummary() {
const total = useStore(s => s.items.reduce((sum, item) => sum + item.price, 0));
const itemCount = useStore(s => s.items.length);
return <div>{itemCount} items - ${total}</div>;
}
```
### Draft mutations for updates
Use draft mutations for nested object/array updates. Mutative handles immutability internally.
```jsx
function UserProfile() {
const [user, setUser] = useStore('user');
const updateName = (name) => {
setUser(draft => {
draft.profile.name = name;
});
};
const addTodo = (text) => {
setUser(draft => {
draft.todos.push({ id: Date.now(), text, completed: false });
});
};
return (
<input
value={user.profile.name}
onChange={e => updateName(e.target.value)}
/>
);
}
```
## Rules
### ✅ DO
- **Use string keys for local component state**
```jsx
const [count, setCount] = useStore('count');
```
- **Use selector functions for read-only/derived values**
```jsx
const total = useStore(s => s.price * s.qty);
```
- **Use draft mutations for nested updates**
```jsx
setUser(draft => { draft.name = 'Jane'; });
```
- **Create store at module level (not in components)**
```javascript
// store.js - create once at module level
export const { useStore } = createSignalStore({ ... });
```
- **Clear store between tests**
```javascript
import { globalStore } from 'react-synapse';
beforeEach(() => globalStore.clearStore());
```
### ❌ DON'T
- **Don't use React Context or Providers** - not needed with react-synapse
- **Don't destructure the store object** - loses reactivity
```jsx
const [store] = useStore('store');
const { user } = store; // ❌ Loses reactivity
```
- **Don't call useStore without arguments** - throws error
```jsx
const state = useStore(); // ❌ Error
```
- **Don't mutate state directly** - always use setters
```jsx
const [user, setUser] = useStore('user');
user.name = 'Jane'; // ❌ Direct mutation
```
- **Don't create stores inside components** - creates new store on each render
## Examples
### Example 1: Todo List with Filter
```jsx
// store.js
import { createSignalStore } from 'react-synapse';
export const { useStore } = createSignalStore({
todos: [],
filter: 'all' // 'all' | 'active' | 'completed'
});
// TodoList.jsx
import { useStore } from './store';
function TodoList() {
const [todos, setTodos] = useStore('todos');
const [filter, setFilter] = useStore('filter');
const addTodo = (text) => {
setTodos(draft => {
draft.push({ id: Date.now(), text, completed: false });
});
};
const toggleTodo = (id) => {
setTodos(draft => {
const todo = draft.find(t => t.id === id);
if (todo) todo.completed = !todo.completed;
});
};
const filtered = todos.filter(t => {
if (filter === 'active') return !t.completed;
if (filter === 'completed') return t.completed;
return true;
});
return (
<div>
<div>
{['all', 'active', 'completed'].map(f => (
<button key={f} onClick={() => setFilter(f)}>{f}</button>
))}
</div>
<ul>
{filtered.map(todo => (
<li
key={todo.id}
onClick={() => toggleTodo(todo.id)}
style={{ textDecoration: todo.completed ? 'line-through' : 'none' }}
>
{todo.text}
</li>
))}
</ul>
</div>
);
}
```
### Example 2: Shopping Cart with Derived State
```jsx
// store.js
import { createSignalStore } from 'react-synapse';
export const { store, useStore } = createSignalStore({
items: [],
coupon: null
});
// Cart.jsx
import { useStore } from './store';
function Cart() {
const [items, setItems] = useStore('items');
const [coupon, setCoupon] = useStore('coupon');
// Derived values via selectors
const subtotal = useStore(s => s.items.reduce((sum, i) => sum + i.price * i.qty, 0));
const discount = useStore(s => s.coupon ? s.subtotal * s.coupon.discount : 0);
const total = subtotal - discount;
const addItem = (item) => {
setItems(draft => {
const existing = draft.find(i => i.id === item.id);
if (existing) {
existing.qty += 1;
} else {
draft.push({ ...item, qty: 1 });
}
});
};
return (
<div>
<ul>
{items.map(item => (
<li key={item.id}>{item.name} x {item.qty} - ${item.price * item.qty}</li>
))}
</ul>
<p>Subtotal: ${subtotal.toFixed(2)}</p>
{coupon && <p>Discount: -${discount.toFixed(2)}</p>}
<p>Total: ${total.toFixed(2)}</p>
</div>
);
}
```
### Example 3: Multi-Component State Sharing
```jsx
// store.js
export const { useStore } = createSignalStore({
messages: [],
currentUser: { name: 'Guest' }
});
// ChatInput.jsx
import { useStore } from './store';
export function ChatInput() {
const [messages, setMessages] = useStore('messages');
const [currentUser] = useStore('currentUser');
const sendMessage = (text) => {
setMessages(draft => {
draft.push({ id: Date.now(), text, sender: currentUser.name });
});
};
return (
<input
placeholder="Type a message..."
onKeyDown={(e) => {
if (e.key === 'Enter' && e.target.value.trim()) {
sendMessage(e.target.value);
e.target.value = '';
}
}}
/>
);
}
// MessageList.jsx
import { useStore } from './store';
export function MessageList() {
const [messages] = useStore('messages');
const [currentUser] = useStore('currentUser');
return (
<div>
{messages.map(msg => (
<div key={msg.id} className={msg.sender === currentUser.name ? 'own' : 'other'}>
<strong>{msg.sender}:</strong> {msg.text}
</div>
))}
</div>
);
}
// App.jsx - No providers needed!
import { ChatInput } from './ChatInput';
import { MessageList } from './MessageList';
function App() {
return (
<div>
<MessageList />
<ChatInput />
</div>
);
}
```
## Quick reference
| Pattern | Returns | Use When |
|---------|---------|----------|
| `useStore('key')` | `[value, setter]` | Need to read and update state |
| `useStore(s => s.prop)` | `value` | Read-only or derived values |
| `useStore(s => [s.a, s.b])` | `[a, b]` | Multiple related reads |
| `useStore(s => ({a: s.a}))` | `{a}` | Named destructuring |
| `useStore('key', {unwrap: false})` | Signal | Fine-grained control |
| `useReactive(value)` | `[value, setter]` | Local component state |
| `useReactiveSignal($sig)` | `value` | Subscribe to existing signal |
## Module exports
```javascript
// Main - everything
import { createSignalStore, useReactive, computed, effect } from 'react-synapse';
// Store only
import { createSignalStore, globalStore } from 'react-synapse/store';
// Signals only
import { useReactive, computed, effect, signal } from 'react-synapse/signals';
// Mutative (draft mutations)
import { create } from 'react-synapse/mutative';
```Related Skills
react
Full React 19 engineering, architecture, Server Components, hooks, Zustand, TanStack Query, forms, performance, testing, production deploy.
react-ui-patterns
Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.
react-to-wx-miniprogram-migrator
Migrates a React + TailwindCSS H5 web application to a native WeChat Mini Program. Use when the user wants to convert their existing web project into a mini program, preserving structure, styling, and functionality.
react-patterns
Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.
react-observability
Logging, error messages, and debugging patterns for React. Use when adding logging, designing error messages, debugging production issues, or improving code observability. Works for both React web and React Native.
react-nextjs-development
React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.
react-native-architecture
Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...
react-guidelines
React coding guidelines and best practices. MUST follow these rules. Use when reviewing or writing React code or tasks.
react-gradual-architecture
Incremental React code organization guidelines. Start small, then extract when scanning and responsibilities start to blur. Use when creating features, organizing files, refactoring components, or deciding when to extract hooks, UI, or utils.
react-grab
Installs and configures React Grab for visual UI element selection in React/Electron apps. Use when user wants to edit UI visually, select components by hovering, or capture element context.
react-frontend
React components for Chat, Evaluation, Report, Admin with TypeScript, Tailwind, hooks