recoil
You are an expert in Recoil, the state management library by Meta for React applications. You help developers manage application state with atoms (shared state units), selectors (derived/async state), and atom families — providing a graph-based state model that integrates naturally with React's concurrent features, avoids unnecessary re-renders, and handles async data fetching as first-class state.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o recoil.zip https://jpskill.com/download/15328.zip && unzip -o recoil.zip && rm recoil.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/15328.zip -OutFile "$d\recoil.zip"; Expand-Archive "$d\recoil.zip" -DestinationPath $d -Force; ri "$d\recoil.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
recoil.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
recoilフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
Recoil — State Management for React
You are an expert in Recoil, the state management library by Meta for React applications. You help developers manage application state with atoms (shared state units), selectors (derived/async state), and atom families — providing a graph-based state model that integrates naturally with React's concurrent features, avoids unnecessary re-renders, and handles async data fetching as first-class state.
Core Capabilities
Atoms and Selectors
import { atom, selector, useRecoilState, useRecoilValue, RecoilRoot } from "recoil";
// Atoms — units of state
const todosAtom = atom<Todo[]>({
key: "todos",
default: [],
});
const filterAtom = atom<"all" | "active" | "completed">({
key: "todoFilter",
default: "all",
});
// Selectors — derived state (auto-updates when dependencies change)
const filteredTodosSelector = selector({
key: "filteredTodos",
get: ({ get }) => {
const todos = get(todosAtom);
const filter = get(filterAtom);
switch (filter) {
case "active": return todos.filter((t) => !t.done);
case "completed": return todos.filter((t) => t.done);
default: return todos;
}
},
});
const statsSelector = selector({
key: "todoStats",
get: ({ get }) => {
const todos = get(todosAtom);
return {
total: todos.length,
completed: todos.filter((t) => t.done).length,
percent: todos.length ? Math.round(todos.filter((t) => t.done).length / todos.length * 100) : 0,
};
},
});
// Components
function TodoList() {
const filteredTodos = useRecoilValue(filteredTodosSelector); // Only re-renders when filtered list changes
return (
<ul>
{filteredTodos.map((todo) => <TodoItem key={todo.id} id={todo.id} />)}
</ul>
);
}
function TodoStats() {
const stats = useRecoilValue(statsSelector);
return <p>{stats.completed}/{stats.total} done ({stats.percent}%)</p>;
}
function FilterButtons() {
const [filter, setFilter] = useRecoilState(filterAtom);
return (
<div>
{(["all", "active", "completed"] as const).map((f) => (
<button key={f} onClick={() => setFilter(f)}
style={{ fontWeight: filter === f ? "bold" : "normal" }}>
{f}
</button>
))}
</div>
);
}
function App() {
return (
<RecoilRoot>
<TodoStats />
<FilterButtons />
<TodoList />
</RecoilRoot>
);
}
Async Selectors and Atom Families
// Async selector — fetches data, integrates with Suspense
const userProfileSelector = selector({
key: "userProfile",
get: async ({ get }) => {
const userId = get(currentUserIdAtom);
const response = await fetch(`/api/users/${userId}`);
return response.json();
},
});
// Atom families — parameterized atoms (one atom per ID)
const todoItemAtom = atomFamily<Todo | null, string>({
key: "todoItem",
default: null,
});
// Selector families — parameterized selectors
const userByIdSelector = selectorFamily<User, string>({
key: "userById",
get: (userId) => async ({ get }) => {
const response = await fetch(`/api/users/${userId}`);
return response.json();
},
});
// Usage with Suspense
function UserProfile() {
const profile = useRecoilValue(userProfileSelector); // Suspends until loaded
return <h1>{profile.name}</h1>;
}
function App() {
return (
<RecoilRoot>
<Suspense fallback={<Spinner />}>
<UserProfile />
</Suspense>
</RecoilRoot>
);
}
Installation
npm install recoil
Best Practices
- Unique keys — Every atom and selector needs a globally unique
keystring; use descriptive names - Selectors for derived state — Never compute derived state in components; use selectors for memoized computation
- Atom families — Use
atomFamilyfor collections (todo items, user profiles); one atom per entity - Async selectors — Return promises from selector
get; pairs with React Suspense for loading states - Fine-grained atoms — Prefer many small atoms over one large one; minimizes re-renders
- RecoilRoot — Wrap app once; provides state context; can nest for isolated state subtrees
- useRecoilValue — Use when you only read;
useRecoilStatewhen you also write; avoids unnecessary subscriptions - Concurrent mode — Recoil is designed for React concurrent features; async selectors work with Suspense transitions