[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVQERXTT25XT5QCT080PWW":3,"skill-same:01M7EVQERXTT25XT5QCT080PWW":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},"01M7EVQERXTT25XT5QCT080PWW","ams-remix-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-remix-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: remix-pro\ndescription: Idiomatic Remix: loaders\u002Factions, progressive enhancement, nested routing, and web-standard patterns. Use when writing, reviewing, or structuring Remix applications.\ncategory: development\n---\n\n# Remix Pro\n\n## Overview\n\nRemix's philosophy — **embrace web standards: forms, HTTP semantics, and progressive enhancement** —\nproduces apps that work without JavaScript and get faster *with* it. Professional Remix means\ndesigning around loaders (data in) and actions (mutations), using nested routes for parallel data\nloading and persistent UI, and treating the network tab as the source of truth.\n\nThe through-line: the web platform already solved most of this — Remix just gets out of its way.\n\n## When to use\n\n- Writing or reviewing Remix (React Router v7) applications.\n- Designing loaders, actions, and form-based mutations.\n- Structuring nested routes and shared layouts.\n- Debugging data loading, revalidation, or fetcher issues.\n- Choosing between Remix patterns and client-side state.\n\n## Core concepts\n\n- **Loaders: data in.** Route `loader` functions run server-side, return data to the component via\n  `useLoaderData`. Parallel across matched routes (no waterfalls by default), revalidate on\n  navigation and action completion. Throw `Response` objects (404\u002F403) for HTTP-correct errors —\n  `ErrorBoundary` + status codes, not client-side error states.\n- **Actions: mutations.** Route `action` functions handle form submissions and mutations —\n  validate, mutate, then redirect (PRG pattern) or return validation errors. `\u003CForm>` works\n  without JS (real POST) and enhances with JS (no full reload). This is the core interaction model.\n- **Nested routing.** Parent routes render layouts + load shared data; child routes load in\n  parallel and render in `\u003COutlet>`. Persistent navigation\u002Fsidebars that don't refetch, granular\n  error boundaries per segment, and parallel data loading fall out of the route tree design.\n- **Fetchers for non-navigation mutations.** `useFetcher` for like buttons, inline edits, and\n  optimistic UI without changing the URL. `fetcher.Form` + `useFetchers` for global pending states.\n- **Optimistic UI, deliberately.** `useNavigation().formData` \u002F fetcher submission state for\n  instant feedback; roll back on action error. Optimistic updates only where the failure path is\n  well-defined.\n- **Web standards as features.** Real `\u003Cform>`s (accessible, no-JS baseline), HTTP status codes\n  and redirects, cache headers on loader responses, and URL as state (search params for filters —\n  shareable, bookmarkable, back-button-correct).\n\n## Practical workflow\n\n1. **Scaffold with the standard template.** React Router v7 (Remix's evolution) with TypeScript;\n   routes in `app\u002Froutes\u002F`; strict mode; type-safe loader\u002Faction data.\n2. **Design the route tree first.** URLs → nested routes → which data each segment loads. Shared\n   layout data (current user, nav) in parent loaders; page-specific in leaves.\n3. **Write loaders that return what's rendered.** Validate params, authorize, fetch in parallel\n   (`Promise.all` for independent queries), throw Responses for 404\u002F403. Type the return; consume\n   with `useLoaderData\u003Ctypeof loader>`.\n4. **Write actions as transactions.** Parse + validate form data (zod) → authorize → mutate →\n   redirect on success \u002F return field errors with 400 on validation failure. `useActionData` renders\n   errors next to fields.\n5. **Enhance progressively.** Every mutation works as a plain form POST first; then add\n   optimistic UI and pending states. Test with JS disabled — the app should still function.\n6. **Observe and tune.** Monitor loader performance (they're your API now), set cache headers on\n   CDN-cacheable loaders, and watch action error rates — failed mutations are UX failures.\n\nLoader\u002Faction sketch:\n\n```tsx\n\u002F\u002F app\u002Froutes\u002Forders.$id.tsx\nexport async function loader({ params }: LoaderFunctionArgs) {\n  const order = await db.order.findUnique({ where: { id: params.id } });\n  if (!order) throw new Response(\"Not found\", { status: 404 });\n  return { order }; \u002F\u002F typed via useLoaderData\u003Ctypeof loader>\n}\n\nexport async function action({ request, params }: ActionFunctionArgs) {\n  const form = await request.formData();\n  const result = CancelSchema.safeParse(Object.fromEntries(form));\n  if (!result.success) return { errors: result.error.flatten() }; \u002F\u002F 400-ish, rendered inline\n  await cancelOrder(params.id!, result.data);\n  return redirect(`\u002Forders\u002F${params.id}`); \u002F\u002F PRG: no resubmit on refresh\n}\n```\n\n## Common pitfalls\n\n- **Client-side fetching for route data.** `useEffect(fetch(...))` in components for what a\n  loader should provide — loses parallel loading, SSR, and revalidation. Loaders are the data layer.\n- **Actions without validation.** Trusting `formData` directly. Parse + validate (zod) and\n  authorize — actions run server-side with full privileges.\n- **Skipping the redirect after mutation.** Returning data instead of redirecting causes\n  resubmission on refresh. PRG (Post\u002FRedirect\u002FGet) is the default for a reason.\n- **useState for URL-statable things.** Filters, tabs, pagination in component state — unshareable,\n  lost on refresh. Search params via `useSearchParams` — the URL is the state manager.\n- **Fetcher misuse.** Using fetchers for navigation-changing operations (use `\u003CForm>`\u002Fnavigation),\n  or ignoring fetcher error states in optimistic UI (stuck \"saved\" indicators on failure).\n- **No-JS baseline broken.** JavaScript-dependent interactions with no form fallback — defeats\n  Remix's core value. Build the form first, enhance second.\n- **Loader waterfalls by design.** Parent loader awaiting child data it shouldn't own, or\n  sequential awaits for independent queries. Keep loaders parallel and segment-scoped.\n","# Remix Pro\n\n## Overview\n\nRemix's philosophy — **embrace web standards: forms, HTTP semantics, and progressive enhancement** —\nproduces apps that work without JavaScript and get faster *with* it. Professional Remix means\ndesigning around loaders (data in) and actions (mutations), using nested routes for parallel data\nloading and persistent UI, and treating the network tab as the source of truth.\n\nThe through-line: the web platform already solved most of this — Remix just gets out of its way.\n\n## When to use\n\n- Writing or reviewing Remix (React Router v7) applications.\n- Designing loaders, actions, and form-based mutations.\n- Structuring nested routes and shared layouts.\n- Debugging data loading, revalidation, or fetcher issues.\n- Choosing between Remix patterns and client-side state.\n\n## Core concepts\n\n- **Loaders: data in.** Route `loader` functions run server-side, return data to the component via\n  `useLoaderData`. Parallel across matched routes (no waterfalls by default), revalidate on\n  navigation and action completion. Throw `Response` objects (404\u002F403) for HTTP-correct errors —\n  `ErrorBoundary` + status codes, not client-side error states.\n- **Actions: mutations.** Route `action` functions handle form submissions and mutations —\n  validate, mutate, then redirect (PRG pattern) or return validation errors. `\u003CForm>` works\n  without JS (real POST) and enhances with JS (no full reload). This is the core interaction model.\n- **Nested routing.** Parent routes render layouts + load shared data; child routes load in\n  parallel and render in `\u003COutlet>`. Persistent navigation\u002Fsidebars that don't refetch, granular\n  error boundaries per segment, and parallel data loading fall out of the route tree design.\n- **Fetchers for non-navigation mutations.** `useFetcher` for like buttons, inline edits, and\n  optimistic UI without changing the URL. `fetcher.Form` + `useFetchers` for global pending states.\n- **Optimistic UI, deliberately.** `useNavigation().formData` \u002F fetcher submission state for\n  instant feedback; roll back on action error. Optimistic updates only where the failure path is\n  well-defined.\n- **Web standards as features.** Real `\u003Cform>`s (accessible, no-JS baseline), HTTP status codes\n  and redirects, cache headers on loader responses, and URL as state (search params for filters —\n  shareable, bookmarkable, back-button-correct).\n\n## Practical workflow\n\n1. **Scaffold with the standard template.** React Router v7 (Remix's evolution) with TypeScript;\n   routes in `app\u002Froutes\u002F`; strict mode; type-safe loader\u002Faction data.\n2. **Design the route tree first.** URLs → nested routes → which data each segment loads. Shared\n   layout data (current user, nav) in parent loaders; page-specific in leaves.\n3. **Write loaders that return what's rendered.** Validate params, authorize, fetch in parallel\n   (`Promise.all` for independent queries), throw Responses for 404\u002F403. Type the return; consume\n   with `useLoaderData\u003Ctypeof loader>`.\n4. **Write actions as transactions.** Parse + validate form data (zod) → authorize → mutate →\n   redirect on success \u002F return field errors with 400 on validation failure. `useActionData` renders\n   errors next to fields.\n5. **Enhance progressively.** Every mutation works as a plain form POST first; then add\n   optimistic UI and pending states. Test with JS disabled — the app should still function.\n6. **Observe and tune.** Monitor loader performance (they're your API now), set cache headers on\n   CDN-cacheable loaders, and watch action error rates — failed mutations are UX failures.\n\nLoader\u002Faction sketch:\n\n```tsx\n\u002F\u002F app\u002Froutes\u002Forders.$id.tsx\nexport async function loader({ params }: LoaderFunctionArgs) {\n  const order = await db.order.findUnique({ where: { id: params.id } });\n  if (!order) throw new Response(\"Not found\", { status: 404 });\n  return { order }; \u002F\u002F typed via useLoaderData\u003Ctypeof loader>\n}\n\nexport async function action({ request, params }: ActionFunctionArgs) {\n  const form = await request.formData();\n  const result = CancelSchema.safeParse(Object.fromEntries(form));\n  if (!result.success) return { errors: result.error.flatten() }; \u002F\u002F 400-ish, rendered inline\n  await cancelOrder(params.id!, result.data);\n  return redirect(`\u002Forders\u002F${params.id}`); \u002F\u002F PRG: no resubmit on refresh\n}\n```\n\n## Common pitfalls\n\n- **Client-side fetching for route data.** `useEffect(fetch(...))` in components for what a\n  loader should provide — loses parallel loading, SSR, and revalidation. Loaders are the data layer.\n- **Actions without validation.** Trusting `formData` directly. Parse + validate (zod) and\n  authorize — actions run server-side with full privileges.\n- **Skipping the redirect after mutation.** Returning data instead of redirecting causes\n  resubmission on refresh. PRG (Post\u002FRedirect\u002FGet) is the default for a reason.\n- **useState for URL-statable things.** Filters, tabs, pagination in component state — unshareable,\n  lost on refresh. Search params via `useSearchParams` — the URL is the state manager.\n- **Fetcher misuse.** Using fetchers for navigation-changing operations (use `\u003CForm>`\u002Fnavigation),\n  or ignoring fetcher error states in optimistic UI (stuck \"saved\" indicators on failure).\n- **No-JS baseline broken.** JavaScript-dependent interactions with no form fallback — defeats\n  Remix's core value. Build the form first, enhance second.\n- **Loader waterfalls by design.** Parent loader awaiting child data it shouldn't own, or\n  sequential awaits for independent queries. Keep loaders parallel and segment-scoped.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-remix-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-remix-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-remix-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-remix-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-remix-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",[],[]]