[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EW01345TDV9ZRFPE8RT6VS":3,"skill-same:01M7EW01345TDV9ZRFPE8RT6VS":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},"01M7EW01345TDV9ZRFPE8RT6VS","ams-solid-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-solid-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: solid-pro\ndescription: Idiomatic SolidJS: fine-grained reactivity, signals\u002Fmemos\u002Feffects, component design, and SolidStart patterns. Use when writing, reviewing, or structuring Solid apps.\ncategory: development\n---\n\n# Solid Pro\n\n## Overview\n\nSolidJS takes fine-grained reactivity to its logical end: **no virtual DOM, no re-rendering\ncomponents** — signals update exactly the DOM nodes that depend on them. Professional Solid means\ninternalizing the reactive execution model (components run once; effects track dependencies\nautomatically), using primitives precisely (signals, memos, effects, resources), and structuring\napps so reactivity flows in one direction.\n\nThe through-line: think in dataflow graphs, not render cycles — components are setup code, JSX is\na template compiled to fine-grained updates.\n\n## When to use\n\n- Writing or reviewing SolidJS code.\n- Designing reactive state, derived values, and side effects.\n- Structuring SolidStart applications (routing, data, SSR).\n- Debugging reactivity issues (stale values, missing updates, effect loops).\n- Optimizing Solid rendering or understanding its execution model.\n\n## Core concepts\n\n- **Components execute once.** A Solid component function runs a single time to set up reactive\n  nodes — JSX expressions re-execute only where they read signals. Code outside reactive contexts\n  (effects, memos, JSX bindings) runs once; don't expect \"re-render\" semantics.\n- **Primitives with distinct jobs.** `createSignal` (read\u002Fwrite reactive value), `createMemo`\n  (cached derivation — use instead of deriving in effects or during render), `createEffect`\n  (side effects, auto-tracks dependencies), `createResource` (async data with loading\u002Ferror\n  states built in). Choosing the wrong primitive is the root of most Solid bugs.\n- **Fine-grained updates.** `\u003Cdiv>{count()}\u003C\u002Fdiv>` — only the text node updates when `count`\n  changes. This is why Solid is fast by default, and why you rarely need memoization: the\n  framework already updates minimally.\n- **Stores for nested state.** `createStore` for deep reactive objects — path-based updates\n  (`setState('user', 'name', 'Ada')`) with immutable semantics and fine-grained notifications.\n  Prefer stores over nested signals for complex state shapes.\n- **Control flow components.** `\u003CShow>`, `\u003CFor>`, `\u003CSwitch>\u002F\u003CMatch>`, `\u003CSuspense>`, `\u003CErrorBoundary>`\n  — real components (not syntax) that handle reactivity correctly. `\u003CFor>` with keyed identity\n  for lists; never `.map()` directly in JSX for dynamic lists (loses fine-grained updates).\n- **SolidStart's isomorphic model.** File-based routing, server functions for data\u002Fmutations,\n  SSR streaming — design data loading server-first like other meta-frameworks, with Solid's\n  reactivity on the client.\n\n## Practical workflow\n\n1. **Scaffold with SolidStart** (or Vite + Solid for SPAs); TypeScript; file-based routes.\n2. **Model state as signals\u002Fstores.** Component-local → signals; shared → context + stores or a\n   small external store module; server data → `createResource` \u002F server functions with\n   loading\u002Ferror states.\n3. **Derive with memos, never in effects.** `const total = createMemo(() => items().reduce(...))`\n   — cached, lazy, and correct. Effects only touch the outside world.\n4. **Write JSX as templates.** Expressions read signals where the DOM should update; control-flow\n   components for conditionals\u002Flists; avoid creating signals inside JSX expressions (runs per\n   evaluation — usually once, but confusing).\n5. **Handle resources properly.** `createResource(fetcher)` gives `loading`\u002F`error` states;\n   `refetch`\u002F`mutate` for updates; `\u003CSuspense>` boundaries placed deliberately; `\u003CErrorBoundary>`\n   for crash isolation.\n6. **Test behavior.** Vitest for logic; `@solidjs\u002Ftesting-library` for component behavior\n   (assert on DOM, interact via user events); Playwright for critical journeys.\n\nIdiomatic snippets:\n\n```tsx\n\u002F\u002F Signals + memo + resource: each primitive doing its job\nfunction OrderList() {\n  const [filter, setFilter] = createSignal(\"\");\n  const [orders] = createResource(fetchOrders); \u002F\u002F { loading, error } built in\n\n  const visible = createMemo(() =>\n    (orders() ?? []).filter(o => o.id.includes(filter()))\n  );\n  const total = createMemo(() => visible().reduce((s, o) => s + o.total, 0));\n\n  \u002F\u002F Effect ONLY for side effects\n  createEffect(() => { document.title = `Orders (${visible().length})`; });\n\n  return (\n    \u003CSuspense fallback={\u003CSkeleton \u002F>}>\n      \u003CErrorBoundary fallback={err => \u003CErrorView error={err} \u002F>}>\n        \u003CFor each={visible()}>{order => \u003COrderRow order={order} \u002F>}\u003C\u002FFor>\n      \u003C\u002FErrorBoundary>\n    \u003C\u002FSuspense>\n  );\n}\n```\n\n## Common pitfalls\n\n- **Thinking in re-renders.** Writing code that assumes the component function re-runs (like\n  React). In Solid it runs once — logic that must re-run on signal change belongs in memos,\n  effects, or JSX expressions.\n- **Deriving in effects.** `createEffect(() => setB(transform(a())))` — use `createMemo`.\n  Effects are side-effect-only; derivation-in-effect causes loops and extra runs.\n- **Destructuring signals' values.** `const { name } = user()` captures a snapshot, not\n  reactivity. Keep the signal call inside reactive contexts.\n- **`.map()` instead of `\u003CFor>`.** Direct array mapping in JSX doesn't get keyed fine-grained\n  updates — list state (focus, input values) breaks on reorder. `\u003CFor>` always for dynamic lists.\n- **Creating reactives in render paths.** `createSignal`\u002F`createEffect` inside JSX expressions or\n  event handlers that run repeatedly — leaks reactive nodes. Create in component body (runs once).\n- **Over-nesting effects.** Effects that set signals read by other effects — cascade of runs,\n  hard to reason about. Flatten: derive with memos, keep effects at the leaves touching the\n  outside world.\n- **Ignoring `\u003CSuspense>` placement.** One root Suspense for everything = whole-page spinners.\n  Place boundaries around independent data regions for progressive loading.\n","# Solid Pro\n\n## Overview\n\nSolidJS takes fine-grained reactivity to its logical end: **no virtual DOM, no re-rendering\ncomponents** — signals update exactly the DOM nodes that depend on them. Professional Solid means\ninternalizing the reactive execution model (components run once; effects track dependencies\nautomatically), using primitives precisely (signals, memos, effects, resources), and structuring\napps so reactivity flows in one direction.\n\nThe through-line: think in dataflow graphs, not render cycles — components are setup code, JSX is\na template compiled to fine-grained updates.\n\n## When to use\n\n- Writing or reviewing SolidJS code.\n- Designing reactive state, derived values, and side effects.\n- Structuring SolidStart applications (routing, data, SSR).\n- Debugging reactivity issues (stale values, missing updates, effect loops).\n- Optimizing Solid rendering or understanding its execution model.\n\n## Core concepts\n\n- **Components execute once.** A Solid component function runs a single time to set up reactive\n  nodes — JSX expressions re-execute only where they read signals. Code outside reactive contexts\n  (effects, memos, JSX bindings) runs once; don't expect \"re-render\" semantics.\n- **Primitives with distinct jobs.** `createSignal` (read\u002Fwrite reactive value), `createMemo`\n  (cached derivation — use instead of deriving in effects or during render), `createEffect`\n  (side effects, auto-tracks dependencies), `createResource` (async data with loading\u002Ferror\n  states built in). Choosing the wrong primitive is the root of most Solid bugs.\n- **Fine-grained updates.** `\u003Cdiv>{count()}\u003C\u002Fdiv>` — only the text node updates when `count`\n  changes. This is why Solid is fast by default, and why you rarely need memoization: the\n  framework already updates minimally.\n- **Stores for nested state.** `createStore` for deep reactive objects — path-based updates\n  (`setState('user', 'name', 'Ada')`) with immutable semantics and fine-grained notifications.\n  Prefer stores over nested signals for complex state shapes.\n- **Control flow components.** `\u003CShow>`, `\u003CFor>`, `\u003CSwitch>\u002F\u003CMatch>`, `\u003CSuspense>`, `\u003CErrorBoundary>`\n  — real components (not syntax) that handle reactivity correctly. `\u003CFor>` with keyed identity\n  for lists; never `.map()` directly in JSX for dynamic lists (loses fine-grained updates).\n- **SolidStart's isomorphic model.** File-based routing, server functions for data\u002Fmutations,\n  SSR streaming — design data loading server-first like other meta-frameworks, with Solid's\n  reactivity on the client.\n\n## Practical workflow\n\n1. **Scaffold with SolidStart** (or Vite + Solid for SPAs); TypeScript; file-based routes.\n2. **Model state as signals\u002Fstores.** Component-local → signals; shared → context + stores or a\n   small external store module; server data → `createResource` \u002F server functions with\n   loading\u002Ferror states.\n3. **Derive with memos, never in effects.** `const total = createMemo(() => items().reduce(...))`\n   — cached, lazy, and correct. Effects only touch the outside world.\n4. **Write JSX as templates.** Expressions read signals where the DOM should update; control-flow\n   components for conditionals\u002Flists; avoid creating signals inside JSX expressions (runs per\n   evaluation — usually once, but confusing).\n5. **Handle resources properly.** `createResource(fetcher)` gives `loading`\u002F`error` states;\n   `refetch`\u002F`mutate` for updates; `\u003CSuspense>` boundaries placed deliberately; `\u003CErrorBoundary>`\n   for crash isolation.\n6. **Test behavior.** Vitest for logic; `@solidjs\u002Ftesting-library` for component behavior\n   (assert on DOM, interact via user events); Playwright for critical journeys.\n\nIdiomatic snippets:\n\n```tsx\n\u002F\u002F Signals + memo + resource: each primitive doing its job\nfunction OrderList() {\n  const [filter, setFilter] = createSignal(\"\");\n  const [orders] = createResource(fetchOrders); \u002F\u002F { loading, error } built in\n\n  const visible = createMemo(() =>\n    (orders() ?? []).filter(o => o.id.includes(filter()))\n  );\n  const total = createMemo(() => visible().reduce((s, o) => s + o.total, 0));\n\n  \u002F\u002F Effect ONLY for side effects\n  createEffect(() => { document.title = `Orders (${visible().length})`; });\n\n  return (\n    \u003CSuspense fallback={\u003CSkeleton \u002F>}>\n      \u003CErrorBoundary fallback={err => \u003CErrorView error={err} \u002F>}>\n        \u003CFor each={visible()}>{order => \u003COrderRow order={order} \u002F>}\u003C\u002FFor>\n      \u003C\u002FErrorBoundary>\n    \u003C\u002FSuspense>\n  );\n}\n```\n\n## Common pitfalls\n\n- **Thinking in re-renders.** Writing code that assumes the component function re-runs (like\n  React). In Solid it runs once — logic that must re-run on signal change belongs in memos,\n  effects, or JSX expressions.\n- **Deriving in effects.** `createEffect(() => setB(transform(a())))` — use `createMemo`.\n  Effects are side-effect-only; derivation-in-effect causes loops and extra runs.\n- **Destructuring signals' values.** `const { name } = user()` captures a snapshot, not\n  reactivity. Keep the signal call inside reactive contexts.\n- **`.map()` instead of `\u003CFor>`.** Direct array mapping in JSX doesn't get keyed fine-grained\n  updates — list state (focus, input values) breaks on reorder. `\u003CFor>` always for dynamic lists.\n- **Creating reactives in render paths.** `createSignal`\u002F`createEffect` inside JSX expressions or\n  event handlers that run repeatedly — leaks reactive nodes. Create in component body (runs once).\n- **Over-nesting effects.** Effects that set signals read by other effects — cascade of runs,\n  hard to reason about. Flatten: derive with memos, keep effects at the leaves touching the\n  outside world.\n- **Ignoring `\u003CSuspense>` placement.** One root Suspense for everything = whole-page spinners.\n  Place boundaries around independent data regions for progressive loading.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-solid-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-solid-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-solid-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-solid-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-solid-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",[],[]]