[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVP2FFVG6PWCT6Q6T29WH0":3,"skill-same:01M7EVP2FFVG6PWCT6Q6T29WH0":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVP2FFVG6PWCT6Q6T29WH0","ams-recoil-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-recoil-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: recoil-pro\ndescription: Manage React state with Recoil: atoms, selectors, async selectors, and atom families\u002Feffects. Use when maintaining Recoil codebases or needing its data-flow graph.\ncategory: development\n---\n\n# Recoil Pro\n\nA practical guide to Recoil: Facebook's experimental-but-widely-used atomic state library — atoms, selectors (sync\u002Fasync), atom families, and effects. Particularly useful for maintaining existing Recoil codebases and understanding its data-flow graph model.\n\n## Overview\n\nRecoil models state as a **data-flow graph**: **atoms** (units of state, identified by unique string keys) and **selectors** (pure functions deriving from atoms\u002Fother selectors, cached per dependency set). Components subscribe via hooks and re-render only when their subscribed values change. Async selectors integrate with Suspense. Note: Recoil's development has slowed (maintenance mode); for new projects, Jotai or Zustand are usually better choices — but large production codebases run on Recoil, and its concepts transfer.\n\n## When to use\n\n- Maintaining an existing Recoil codebase.\n- Understanding selector-based derived data (concepts apply to Jotai\u002Fothers).\n- Apps needing the data-flow graph mental model (explicit deps, cached derivations).\n- Evaluating migration off Recoil (to Jotai\u002FZustand).\n\n## Core concepts\n\n- **Atoms.** `const nameState = atom({ key: 'nameState', default: '' })`. Keys must be globally unique — collisions are silent and nasty.\n- **Selectors.** `selector({ key: 'upperName', get: ({ get }) => get(nameState).toUpperCase() })` — derived, memoized, recompute only when deps change. `set` for writable selectors.\n- **Async selectors.** `get` can be async → Suspense integration. `useRecoilValueLoadable` for manual loading\u002Ferror states without Suspense.\n- **Atom families.** `atomFamily({ key: 'todoState', default: id => fetchTodo(id) })` — parameterized atoms, `todoState(id)` per instance.\n- **Effects (`effects_UNSTABLE`).** Per-atom effects: persistence to localStorage, logging, syncing with external stores. The escape hatch for side effects.\n- **`useRecoilState` \u002F `useRecoilValue` \u002F `useSetRecoilState` \u002F `useResetRecoilState`.** Split read\u002Fwrite subscriptions like Jotai's hooks.\n- **`waitForAll` \u002F `waitForNone`.** Concurrent async selector helpers: `waitForAll([selA, selB])` parallelizes; `waitForNone` gives loadables for partial rendering.\n\n## Practical workflow\n\n**1. Define state with unique keys.**\n```ts\nimport { atom, selector } from 'recoil';\n\nexport const todosState = atom\u003CTodo[]>({ key: 'todosState', default: [] });\nexport const filterState = atom\u003CFilter>({ key: 'filterState', default: 'all' });\n\nexport const visibleTodosState = selector({\n  key: 'visibleTodosState',\n  get: ({ get }) => {\n    const todos = get(todosState);\n    const filter = get(filterState);\n    return filter === 'all' ? todos : todos.filter(t => !t.done);\n  },\n});\n```\n\n**2. Consume.**\n```tsx\nconst visible = useRecoilValue(visibleTodosState);\nconst setTodos = useSetRecoilState(todosState);\n```\n\n**3. Async with loadables.**\n```ts\nconst userQuery = selector({\n  key: 'userQuery',\n  get: async ({ get }) => api.getUser(get(userIdState)),\n});\n\u002F\u002F component: const loadable = useRecoilValueLoadable(userQuery);\n\u002F\u002F switch (loadable.state) { case 'loading': ...; case 'hasValue': ...; case 'hasError': ... }\n```\n\n**4. Persist via effects.**\n```ts\nconst localStorageEffect = (key) => ({ setSelf, onSet }) => {\n  const saved = localStorage.getItem(key);\n  if (saved) setSelf(JSON.parse(saved));\n  onSet((v) => localStorage.setItem(key, JSON.stringify(v)));\n};\n```\n\n**5. Debug.** Recoil DevTools \u002F React DevTools: inspect atom values; use snapshots (`useRecoilSnapshot`) in tests to assert state transitions.\n\n## Common pitfalls\n\n- **Duplicate keys.** Two atoms with the same `key` silently share\u002Fcollide. Namespace keys by feature (`'cart\u002FitemsState'`); consider a lint or helper enforcing prefixes.\n- **Selector side effects.** `get` must be pure. Fetching is fine (async get), but writing atoms or mutating external state inside `get` corrupts the graph.\n- **Async selector waterfalls.** Sequential dependent selectors suspend one after another. Use `waitForAll` for parallel fetches.\n- **Suspense-everywhere.** Async selectors suspend by default; missing boundaries crash. Prefer `useRecoilValueLoadable` at leaves for granular loading UI.\n- **Atom family memory.** Families retain every parameterized instance; unbounded params (per-message IDs) leak. Prune or avoid families for unbounded sets.\n- **Effects_UNSTABLE instability.** The API is literally marked unstable; behavior changed across versions. Pin the Recoil version and wrap effects in your own helpers.\n- **Over-selectoring.** Trivial derivations as selectors add indirection; inline simple computations in components.\n- **Migration planning.** If moving to Jotai: atoms map nearly 1:1 (drop keys), selectors map to derived atoms, families to atomFamily. Migrate feature by feature behind the same component APIs.\n","# Recoil Pro\n\nA practical guide to Recoil: Facebook's experimental-but-widely-used atomic state library — atoms, selectors (sync\u002Fasync), atom families, and effects. Particularly useful for maintaining existing Recoil codebases and understanding its data-flow graph model.\n\n## Overview\n\nRecoil models state as a **data-flow graph**: **atoms** (units of state, identified by unique string keys) and **selectors** (pure functions deriving from atoms\u002Fother selectors, cached per dependency set). Components subscribe via hooks and re-render only when their subscribed values change. Async selectors integrate with Suspense. Note: Recoil's development has slowed (maintenance mode); for new projects, Jotai or Zustand are usually better choices — but large production codebases run on Recoil, and its concepts transfer.\n\n## When to use\n\n- Maintaining an existing Recoil codebase.\n- Understanding selector-based derived data (concepts apply to Jotai\u002Fothers).\n- Apps needing the data-flow graph mental model (explicit deps, cached derivations).\n- Evaluating migration off Recoil (to Jotai\u002FZustand).\n\n## Core concepts\n\n- **Atoms.** `const nameState = atom({ key: 'nameState', default: '' })`. Keys must be globally unique — collisions are silent and nasty.\n- **Selectors.** `selector({ key: 'upperName', get: ({ get }) => get(nameState).toUpperCase() })` — derived, memoized, recompute only when deps change. `set` for writable selectors.\n- **Async selectors.** `get` can be async → Suspense integration. `useRecoilValueLoadable` for manual loading\u002Ferror states without Suspense.\n- **Atom families.** `atomFamily({ key: 'todoState', default: id => fetchTodo(id) })` — parameterized atoms, `todoState(id)` per instance.\n- **Effects (`effects_UNSTABLE`).** Per-atom effects: persistence to localStorage, logging, syncing with external stores. The escape hatch for side effects.\n- **`useRecoilState` \u002F `useRecoilValue` \u002F `useSetRecoilState` \u002F `useResetRecoilState`.** Split read\u002Fwrite subscriptions like Jotai's hooks.\n- **`waitForAll` \u002F `waitForNone`.** Concurrent async selector helpers: `waitForAll([selA, selB])` parallelizes; `waitForNone` gives loadables for partial rendering.\n\n## Practical workflow\n\n**1. Define state with unique keys.**\n```ts\nimport { atom, selector } from 'recoil';\n\nexport const todosState = atom\u003CTodo[]>({ key: 'todosState', default: [] });\nexport const filterState = atom\u003CFilter>({ key: 'filterState', default: 'all' });\n\nexport const visibleTodosState = selector({\n  key: 'visibleTodosState',\n  get: ({ get }) => {\n    const todos = get(todosState);\n    const filter = get(filterState);\n    return filter === 'all' ? todos : todos.filter(t => !t.done);\n  },\n});\n```\n\n**2. Consume.**\n```tsx\nconst visible = useRecoilValue(visibleTodosState);\nconst setTodos = useSetRecoilState(todosState);\n```\n\n**3. Async with loadables.**\n```ts\nconst userQuery = selector({\n  key: 'userQuery',\n  get: async ({ get }) => api.getUser(get(userIdState)),\n});\n\u002F\u002F component: const loadable = useRecoilValueLoadable(userQuery);\n\u002F\u002F switch (loadable.state) { case 'loading': ...; case 'hasValue': ...; case 'hasError': ... }\n```\n\n**4. Persist via effects.**\n```ts\nconst localStorageEffect = (key) => ({ setSelf, onSet }) => {\n  const saved = localStorage.getItem(key);\n  if (saved) setSelf(JSON.parse(saved));\n  onSet((v) => localStorage.setItem(key, JSON.stringify(v)));\n};\n```\n\n**5. Debug.** Recoil DevTools \u002F React DevTools: inspect atom values; use snapshots (`useRecoilSnapshot`) in tests to assert state transitions.\n\n## Common pitfalls\n\n- **Duplicate keys.** Two atoms with the same `key` silently share\u002Fcollide. Namespace keys by feature (`'cart\u002FitemsState'`); consider a lint or helper enforcing prefixes.\n- **Selector side effects.** `get` must be pure. Fetching is fine (async get), but writing atoms or mutating external state inside `get` corrupts the graph.\n- **Async selector waterfalls.** Sequential dependent selectors suspend one after another. Use `waitForAll` for parallel fetches.\n- **Suspense-everywhere.** Async selectors suspend by default; missing boundaries crash. Prefer `useRecoilValueLoadable` at leaves for granular loading UI.\n- **Atom family memory.** Families retain every parameterized instance; unbounded params (per-message IDs) leak. Prune or avoid families for unbounded sets.\n- **Effects_UNSTABLE instability.** The API is literally marked unstable; behavior changed across versions. Pin the Recoil version and wrap effects in your own helpers.\n- **Over-selectoring.** Trivial derivations as selectors add indirection; inline simple computations in components.\n- **Migration planning.** If moving to Jotai: atoms map nearly 1:1 (drop keys), selectors map to derived atoms, families to atomFamily. Migrate feature by feature behind the same component APIs.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-recoil-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-recoil-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-recoil-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-recoil-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-recoil-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]