[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B318ES31NWXT3TTRYP1RTP":3,"skill-same:01M7B318ES31NWXT3TTRYP1RTP":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B318ES31NWXT3TTRYP1RTP","hamster-react",null,"Hamster-specific React and Next.js patterns. Use when creating pages, components, forms, server actions, or data fetching in apps\u002Fweb. Complements the react-best-practices skill.","gethamster\u002Fskills","gethamster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215697643?v=4","01M7B2R6PGB3SDZZ71E0WE2S74","Hamster","01M7B2R6Q21HWJRXZZWB78BNDG",4,"MIT","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hamster-react\ndescription: \"Hamster-specific React and Next.js patterns. Use when creating pages, components, forms, server actions, or data fetching in apps\u002Fweb. Complements the react-best-practices skill.\"\nversion: \"1.1.0\"\n---\n\n# Hamster React Patterns\n\n## Overview\n\nReact and Next.js conventions specific to the Hamster Studio monorepo. Covers page creation, server actions, data fetching, forms, and UI components. For general React performance patterns, see the `react-best-practices` skill.\n\n## When to Apply\n\n- Creating new pages or layouts in apps\u002Fweb\n- Writing server actions or route handlers\n- Building forms with validation\n- Fetching data in server or client components\n- Using @kit\u002Fui components\n\n## Quick Reference\n\n| Task | Pattern | Reference |\n| --- | --- | --- |\n| Create page | `withI18n`, `generateMetadata`, `PageBody` | `references\u002Frules\u002Fpage-creation.md` |\n| Server action | `enhanceAction` with schema, `'use server'` | `references\u002Frules\u002Fserver-actions.md` |\n| Fetch data | Server: direct Supabase, Client: React Query | `references\u002Frules\u002Fdata-fetching.md` |\n| Build form | react-hook-form + Zod + server action | `references\u002Frules\u002Fforms.md` |\n| UI components | Import from `@kit\u002Fui\u002F*` | `references\u002Frules\u002Fui-components.md` |\n\n## Architecture Overview\n\n```\napp\u002Fhome\u002F\n├── (user)\u002F           # Personal account context\n│   ├── _components\u002F  # Route-specific components\n│   ├── _lib\u002Fserver\u002F  # Loaders, actions\n│   └── page.tsx\n└── [account]\u002F        # Team account context (slug, not UUID)\n    ├── _components\u002F\n    ├── _lib\u002Fserver\u002F\n    └── page.tsx\n```\n\n## Key Patterns\n\n### Page Structure\n\n```tsx\nimport { PageBody } from '@kit\u002Fui\u002Fpage';\nimport { Trans } from '@kit\u002Fui\u002Ftrans';\nimport { withI18n } from '~\u002Flib\u002Fi18n\u002Fwith-i18n';\n\nexport const generateMetadata = async () => {\n  const i18n = await createI18nServerInstance();\n  return { title: i18n.t('feature:pageTitle') };\n};\n\nfunction FeaturePage() {\n  return (\n    \u003C>\n      \u003CFeatureHeader title={\u003CTrans i18nKey=\"common:routes.feature\" \u002F>} \u002F>\n      \u003CPageBody>{\u002F* Content *\u002F}\u003C\u002FPageBody>\n    \u003C\u002F>\n  );\n}\n\nexport default withI18n(FeaturePage);\n```\n\n### Server Action Pattern\n\n```tsx\n'use server';\n\nimport { enhanceAction } from '@kit\u002Fnext\u002Factions';\nimport { CreateItemSchema } from '..\u002Fschema\u002Fcreate-item.schema';\n\nexport const createItemAction = enhanceAction(\n  async (data, user) => {\n    \u002F\u002F data validated, user authenticated\n    const client = getSupabaseServerClient();\n    const { data: item } = await client.from('items').insert(data).select().single();\n    return { success: true, item };\n  },\n  { auth: true, schema: CreateItemSchema }\n);\n```\n\n### Data Fetching Decision\n\n| Context | Use | Example |\n| --- | --- | --- |\n| Server Component | Direct Supabase | `await client.from('items').select()` |\n| Client Component | React Query + `useSupabase` | `useQuery({ queryFn: ... })` |\n| Admin bypass | `getSupabaseServerAdminClient` | Rare, requires manual auth |\n\n### Form Pattern\n\n```tsx\n'use client';\n\nimport { useForm } from 'react-hook-form';\nimport { zodResolver } from '@hookform\u002Fresolvers\u002Fzod';\nimport { Form, FormField, FormItem, FormControl, FormMessage } from '@kit\u002Fui\u002Fform';\nimport { toast } from '@kit\u002Fui\u002Fsonner';\n\nfunction MyForm() {\n  const form = useForm({ resolver: zodResolver(Schema) });\n\n  const onSubmit = (data) => {\n    startTransition(async () => {\n      await toast.promise(myAction(data), {\n        loading: t('creating'),\n        success: t('created'),\n        error: t('error')\n      });\n    });\n  };\n\n  return (\n    \u003CForm {...form}>\n      \u003Cform onSubmit={form.handleSubmit(onSubmit)}>\n        {\u002F* FormFields *\u002F}\n      \u003C\u002Fform>\n    \u003C\u002FForm>\n  );\n}\n```\n\n## useEffect Rules (CRITICAL)\n\n**MUST** follow [You Might Not Need an Effect](https:\u002F\u002Freact.dev\u002Flearn\u002Fyou-might-not-need-an-effect). Before writing any `useEffect`, ask: _\"Is this synchronizing with an external system?\"_ If not, you probably don't need it.\n\n### When useEffect is WRONG\n\n#### 1. Derived state — compute during render instead\n\n```tsx\n\u002F\u002F 🔴 WRONG: redundant state + unnecessary Effect\nconst [fullName, setFullName] = useState('');\nuseEffect(() => {\n  setFullName(firstName + ' ' + lastName);\n}, [firstName, lastName]);\n\n\u002F\u002F ✅ CORRECT: calculate during render\nconst fullName = firstName + ' ' + lastName;\n\n\u002F\u002F ✅ CORRECT: memoize if expensive\nconst filtered = useMemo(() => getFilteredTodos(todos, filter), [todos, filter]);\n```\n\n#### 2. State reset on prop change — use `key` or render-time adjustment\n\n```tsx\n\u002F\u002F 🔴 WRONG: resetting state in an Effect\nuseEffect(() => {\n  setComment('');\n}, [userId]);\n\n\u002F\u002F ✅ BEST: use key to reset entire component\n\u003CProfile userId={userId} key={userId} \u002F>\n\n\u002F\u002F ✅ OK: render-time adjustment when only partial reset needed\nconst [prevItems, setPrevItems] = useState(items);\nif (items !== prevItems) {\n  setPrevItems(items);\n  setSelection(null);\n}\n\n\u002F\u002F ✅ BEST: derive instead of resetting\nconst selection = items.find(item => item.id === selectedId) ?? null;\n```\n\n#### 3. Event-specific logic — put it in the event handler\n\n```tsx\n\u002F\u002F 🔴 WRONG: event logic in an Effect\nuseEffect(() => {\n  if (product.isInCart) {\n    showNotification(`Added ${product.name}!`);\n  }\n}, [product]);\n\n\u002F\u002F ✅ CORRECT: call from the event handler\nfunction handleBuyClick() {\n  addToCart(product);\n  showNotification(`Added ${product.name}!`);\n}\n```\n\n#### 4. Notifying parent about state changes — call in the event handler\n\n```tsx\n\u002F\u002F 🔴 WRONG: notifying parent via Effect\nuseEffect(() => {\n  onChange(isOn);\n}, [isOn, onChange]);\n\n\u002F\u002F ✅ CORRECT: notify during the event that caused the change\nfunction updateToggle(nextIsOn) {\n  setIsOn(nextIsOn);\n  onChange(nextIsOn);\n}\n```\n\n#### 5. Passing data to parent — lift the fetch up instead\n\n```tsx\n\u002F\u002F 🔴 WRONG: child fetches, passes to parent via Effect\nfunction Child({ onFetched }) {\n  const data = useSomeAPI();\n  useEffect(() => {\n    if (data) onFetched(data);\n  }, [data, onFetched]);\n}\n\n\u002F\u002F ✅ CORRECT: parent fetches, passes down\nfunction Parent() {\n  const data = useSomeAPI();\n  return \u003CChild data={data} \u002F>;\n}\n```\n\n#### 6. Effect chains — compute in render, update in event handlers\n\n```tsx\n\u002F\u002F 🔴 WRONG: chain of Effects triggering each other\nuseEffect(() => { if (card?.gold) setGoldCount(c => c + 1); }, [card]);\nuseEffect(() => { if (goldCount > 3) { setRound(r => r + 1); setGoldCount(0); } }, [goldCount]);\nuseEffect(() => { if (round > 5) setGameOver(true); }, [round]);\n\n\u002F\u002F ✅ CORRECT: derive what you can, update in event handler\nconst isGameOver = round > 5;\nfunction handlePlaceCard(nextCard) {\n  setCard(nextCard);\n  if (nextCard.gold) {\n    if (goldCount \u003C 3) setGoldCount(goldCount + 1);\n    else { setGoldCount(0); setRound(round + 1); }\n  }\n}\n```\n\n### When useEffect IS correct\n\n| Pattern | Why it's correct |\n| --- | --- |\n| Subscriptions with cleanup | Synchronizing with external system (realtime channels, WebSocket, event listeners) |\n| Data fetching with cleanup | Synchronizing with network (add `ignore` flag for race conditions) |\n| DOM manipulation via refs | Synchronizing with browser DOM (focus, scroll, ResizeObserver) |\n| Analytics on mount | Side effect because component was _displayed_ |\n| Ref syncs for stale closures | Keeping refs current for callbacks used in subscriptions |\n| External store mutations | Synchronizing React state with Zustand\u002Fexternal stores |\n\n### Key principle\n\n> **\"If this logic is caused by a particular interaction, keep it in the event handler. If it's caused by the user _seeing_ the component on the screen, keep it in the Effect.\"**\n\n### Lint enforcement\n\nThe codebase enforces these patterns via:\n\n- `react-hooks\u002Fset-state-in-effect` — flags synchronous setState inside effects (use `useEffectEvent` wrapper for legitimate cases like hydration detection)\n- `react-hooks\u002Frefs` — flags ref access during render (keep ref syncs in `useEffect`, not render body)\n- Consider a community “you might not need an effect” lint plugin for broader detection of redundant effects\n\n## Component Guidelines\n\n### Server vs Client Components\n\n| Use Server Components | Use Client Components |\n| --- | --- |\n| Data fetching | Interactivity (onClick, onChange) |\n| Authenticated queries | Browser APIs |\n| Static rendering | React hooks (useState, useEffect) |\n| No hooks needed | Real-time listeners |\n\n### Workspace Contexts\n\n```tsx\n\u002F\u002F Personal account\nimport { useUserWorkspace } from '@kit\u002Faccounts\u002Fhooks\u002Fuse-user-workspace';\nconst { user, account } = useUserWorkspace();\n\n\u002F\u002F Team account\nimport { useTeamAccountWorkspace } from '@kit\u002Fteam-accounts\u002Fhooks\u002Fuse-team-account-workspace';\nconst { account, user, accounts } = useTeamAccountWorkspace();\n```\n\n### JSX Patterns\n\n```tsx\n\u002F\u002F Class merging\nimport { cn } from '@kit\u002Fui\u002Futils';\n\u003Cdiv className={cn('base', { 'active': isActive }, className)} \u002F>\n\n\u002F\u002F Conditional rendering\nimport { If } from '@kit\u002Fui\u002Fif';\n\u003CIf condition={isLoading} fallback={\u003CContent \u002F>}>\n  \u003CSpinner \u002F>\n\u003C\u002FIf>\n\n\u002F\u002F Translations (no hardcoded strings)\nimport { Trans } from '@kit\u002Fui\u002Ftrans';\n\u003CTrans i18nKey=\"feature:message\" values={{ name }} \u002F>\n```\n\n## File Organization\n\n| File | Purpose |\n| --- | --- |\n| `page.tsx` | Route page component |\n| `layout.tsx` | Shared layout |\n| `loading.tsx` | Loading state |\n| `error.tsx` | Error boundary |\n| `_components\u002F` | Route-specific components |\n| `_lib\u002Fserver\u002F` | Loaders, actions, queries |\n| `_lib\u002Fschema\u002F` | Zod validation schemas |\n\n## References\n\n- `references\u002Frules\u002Fpage-creation.md` - Creating pages and layouts\n- `references\u002Frules\u002Fserver-actions.md` - Server action patterns\n- `references\u002Frules\u002Fdata-fetching.md` - Data fetching strategies\n- `references\u002Frules\u002Fforms.md` - Form implementation\n- `references\u002Frules\u002Fui-components.md` - UI component usage\n- `references\u002Frules\u002Freact-patterns.md` - React component patterns\n- `references\u002Frules\u002Ftranslations.md` - i18n implementation\n","# Hamster React Patterns\n\n## Overview\n\nReact and Next.js conventions specific to the Hamster Studio monorepo. Covers page creation, server actions, data fetching, forms, and UI components. For general React performance patterns, see the `react-best-practices` skill.\n\n## When to Apply\n\n- Creating new pages or layouts in apps\u002Fweb\n- Writing server actions or route handlers\n- Building forms with validation\n- Fetching data in server or client components\n- Using @kit\u002Fui components\n\n## Quick Reference\n\n| Task | Pattern | Reference |\n| --- | --- | --- |\n| Create page | `withI18n`, `generateMetadata`, `PageBody` | `references\u002Frules\u002Fpage-creation.md` |\n| Server action | `enhanceAction` with schema, `'use server'` | `references\u002Frules\u002Fserver-actions.md` |\n| Fetch data | Server: direct Supabase, Client: React Query | `references\u002Frules\u002Fdata-fetching.md` |\n| Build form | react-hook-form + Zod + server action | `references\u002Frules\u002Fforms.md` |\n| UI components | Import from `@kit\u002Fui\u002F*` | `references\u002Frules\u002Fui-components.md` |\n\n## Architecture Overview\n\n```\napp\u002Fhome\u002F\n├── (user)\u002F           # Personal account context\n│   ├── _components\u002F  # Route-specific components\n│   ├── _lib\u002Fserver\u002F  # Loaders, actions\n│   └── page.tsx\n└── [account]\u002F        # Team account context (slug, not UUID)\n    ├── _components\u002F\n    ├── _lib\u002Fserver\u002F\n    └── page.tsx\n```\n\n## Key Patterns\n\n### Page Structure\n\n```tsx\nimport { PageBody } from '@kit\u002Fui\u002Fpage';\nimport { Trans } from '@kit\u002Fui\u002Ftrans';\nimport { withI18n } from '~\u002Flib\u002Fi18n\u002Fwith-i18n';\n\nexport const generateMetadata = async () => {\n  const i18n = await createI18nServerInstance();\n  return { title: i18n.t('feature:pageTitle') };\n};\n\nfunction FeaturePage() {\n  return (\n    \u003C>\n      \u003CFeatureHeader title={\u003CTrans i18nKey=\"common:routes.feature\" \u002F>} \u002F>\n      \u003CPageBody>{\u002F* Content *\u002F}\u003C\u002FPageBody>\n    \u003C\u002F>\n  );\n}\n\nexport default withI18n(FeaturePage);\n```\n\n### Server Action Pattern\n\n```tsx\n'use server';\n\nimport { enhanceAction } from '@kit\u002Fnext\u002Factions';\nimport { CreateItemSchema } from '..\u002Fschema\u002Fcreate-item.schema';\n\nexport const createItemAction = enhanceAction(\n  async (data, user) => {\n    \u002F\u002F data validated, user authenticated\n    const client = getSupabaseServerClient();\n    const { data: item } = await client.from('items').insert(data).select().single();\n    return { success: true, item };\n  },\n  { auth: true, schema: CreateItemSchema }\n);\n```\n\n### Data Fetching Decision\n\n| Context | Use | Example |\n| --- | --- | --- |\n| Server Component | Direct Supabase | `await client.from('items').select()` |\n| Client Component | React Query + `useSupabase` | `useQuery({ queryFn: ... })` |\n| Admin bypass | `getSupabaseServerAdminClient` | Rare, requires manual auth |\n\n### Form Pattern\n\n```tsx\n'use client';\n\nimport { useForm } from 'react-hook-form';\nimport { zodResolver } from '@hookform\u002Fresolvers\u002Fzod';\nimport { Form, FormField, FormItem, FormControl, FormMessage } from '@kit\u002Fui\u002Fform';\nimport { toast } from '@kit\u002Fui\u002Fsonner';\n\nfunction MyForm() {\n  const form = useForm({ resolver: zodResolver(Schema) });\n\n  const onSubmit = (data) => {\n    startTransition(async () => {\n      await toast.promise(myAction(data), {\n        loading: t('creating'),\n        success: t('created'),\n        error: t('error')\n      });\n    });\n  };\n\n  return (\n    \u003CForm {...form}>\n      \u003Cform onSubmit={form.handleSubmit(onSubmit)}>\n        {\u002F* FormFields *\u002F}\n      \u003C\u002Fform>\n    \u003C\u002FForm>\n  );\n}\n```\n\n## useEffect Rules (CRITICAL)\n\n**MUST** follow [You Might Not Need an Effect](https:\u002F\u002Freact.dev\u002Flearn\u002Fyou-might-not-need-an-effect). Before writing any `useEffect`, ask: _\"Is this synchronizing with an external system?\"_ If not, you probably don't need it.\n\n### When useEffect is WRONG\n\n#### 1. Derived state — compute during render instead\n\n```tsx\n\u002F\u002F 🔴 WRONG: redundant state + unnecessary Effect\nconst [fullName, setFullName] = useState('');\nuseEffect(() => {\n  setFullName(firstName + ' ' + lastName);\n}, [firstName, lastName]);\n\n\u002F\u002F ✅ CORRECT: calculate during render\nconst fullName = firstName + ' ' + lastName;\n\n\u002F\u002F ✅ CORRECT: memoize if expensive\nconst filtered = useMemo(() => getFilteredTodos(todos, filter), [todos, filter]);\n```\n\n#### 2. State reset on prop change — use `key` or render-time adjustment\n\n```tsx\n\u002F\u002F 🔴 WRONG: resetting state in an Effect\nuseEffect(() => {\n  setComment('');\n}, [userId]);\n\n\u002F\u002F ✅ BEST: use key to reset entire component\n\u003CProfile userId={userId} key={userId} \u002F>\n\n\u002F\u002F ✅ OK: render-time adjustment when only partial reset needed\nconst [prevItems, setPrevItems] = useState(items);\nif (items !== prevItems) {\n  setPrevItems(items);\n  setSelection(null);\n}\n\n\u002F\u002F ✅ BEST: derive instead of resetting\nconst selection = items.find(item => item.id === selectedId) ?? null;\n```\n\n#### 3. Event-specific logic — put it in the event handler\n\n```tsx\n\u002F\u002F 🔴 WRONG: event logic in an Effect\nuseEffect(() => {\n  if (product.isInCart) {\n    showNotification(`Added ${product.name}!`);\n  }\n}, [product]);\n\n\u002F\u002F ✅ CORRECT: call from the event handler\nfunction handleBuyClick() {\n  addToCart(product);\n  showNotification(`Added ${product.name}!`);\n}\n```\n\n#### 4. Notifying parent about state changes — call in the event handler\n\n```tsx\n\u002F\u002F 🔴 WRONG: notifying parent via Effect\nuseEffect(() => {\n  onChange(isOn);\n}, [isOn, onChange]);\n\n\u002F\u002F ✅ CORRECT: notify during the event that caused the change\nfunction updateToggle(nextIsOn) {\n  setIsOn(nextIsOn);\n  onChange(nextIsOn);\n}\n```\n\n#### 5. Passing data to parent — lift the fetch up instead\n\n```tsx\n\u002F\u002F 🔴 WRONG: child fetches, passes to parent via Effect\nfunction Child({ onFetched }) {\n  const data = useSomeAPI();\n  useEffect(() => {\n    if (data) onFetched(data);\n  }, [data, onFetched]);\n}\n\n\u002F\u002F ✅ CORRECT: parent fetches, passes down\nfunction Parent() {\n  const data = useSomeAPI();\n  return \u003CChild data={data} \u002F>;\n}\n```\n\n#### 6. Effect chains — compute in render, update in event handlers\n\n```tsx\n\u002F\u002F 🔴 WRONG: chain of Effects triggering each other\nuseEffect(() => { if (card?.gold) setGoldCount(c => c + 1); }, [card]);\nuseEffect(() => { if (goldCount > 3) { setRound(r => r + 1); setGoldCount(0); } }, [goldCount]);\nuseEffect(() => { if (round > 5) setGameOver(true); }, [round]);\n\n\u002F\u002F ✅ CORRECT: derive what you can, update in event handler\nconst isGameOver = round > 5;\nfunction handlePlaceCard(nextCard) {\n  setCard(nextCard);\n  if (nextCard.gold) {\n    if (goldCount \u003C 3) setGoldCount(goldCount + 1);\n    else { setGoldCount(0); setRound(round + 1); }\n  }\n}\n```\n\n### When useEffect IS correct\n\n| Pattern | Why it's correct |\n| --- | --- |\n| Subscriptions with cleanup | Synchronizing with external system (realtime channels, WebSocket, event listeners) |\n| Data fetching with cleanup | Synchronizing with network (add `ignore` flag for race conditions) |\n| DOM manipulation via refs | Synchronizing with browser DOM (focus, scroll, ResizeObserver) |\n| Analytics on mount | Side effect because component was _displayed_ |\n| Ref syncs for stale closures | Keeping refs current for callbacks used in subscriptions |\n| External store mutations | Synchronizing React state with Zustand\u002Fexternal stores |\n\n### Key principle\n\n> **\"If this logic is caused by a particular interaction, keep it in the event handler. If it's caused by the user _seeing_ the component on the screen, keep it in the Effect.\"**\n\n### Lint enforcement\n\nThe codebase enforces these patterns via:\n\n- `react-hooks\u002Fset-state-in-effect` — flags synchronous setState inside effects (use `useEffectEvent` wrapper for legitimate cases like hydration detection)\n- `react-hooks\u002Frefs` — flags ref access during render (keep ref syncs in `useEffect`, not render body)\n- Consider a community “you might not need an effect” lint plugin for broader detection of redundant effects\n\n## Component Guidelines\n\n### Server vs Client Components\n\n| Use Server Components | Use Client Components |\n| --- | --- |\n| Data fetching | Interactivity (onClick, onChange) |\n| Authenticated queries | Browser APIs |\n| Static rendering | React hooks (useState, useEffect) |\n| No hooks needed | Real-time listeners |\n\n### Workspace Contexts\n\n```tsx\n\u002F\u002F Personal account\nimport { useUserWorkspace } from '@kit\u002Faccounts\u002Fhooks\u002Fuse-user-workspace';\nconst { user, account } = useUserWorkspace();\n\n\u002F\u002F Team account\nimport { useTeamAccountWorkspace } from '@kit\u002Fteam-accounts\u002Fhooks\u002Fuse-team-account-workspace';\nconst { account, user, accounts } = useTeamAccountWorkspace();\n```\n\n### JSX Patterns\n\n```tsx\n\u002F\u002F Class merging\nimport { cn } from '@kit\u002Fui\u002Futils';\n\u003Cdiv className={cn('base', { 'active': isActive }, className)} \u002F>\n\n\u002F\u002F Conditional rendering\nimport { If } from '@kit\u002Fui\u002Fif';\n\u003CIf condition={isLoading} fallback={\u003CContent \u002F>}>\n  \u003CSpinner \u002F>\n\u003C\u002FIf>\n\n\u002F\u002F Translations (no hardcoded strings)\nimport { Trans } from '@kit\u002Fui\u002Ftrans';\n\u003CTrans i18nKey=\"feature:message\" values={{ name }} \u002F>\n```\n\n## File Organization\n\n| File | Purpose |\n| --- | --- |\n| `page.tsx` | Route page component |\n| `layout.tsx` | Shared layout |\n| `loading.tsx` | Loading state |\n| `error.tsx` | Error boundary |\n| `_components\u002F` | Route-specific components |\n| `_lib\u002Fserver\u002F` | Loaders, actions, queries |\n| `_lib\u002Fschema\u002F` | Zod validation schemas |\n\n## References\n\n- `references\u002Frules\u002Fpage-creation.md` - Creating pages and layouts\n- `references\u002Frules\u002Fserver-actions.md` - Server action patterns\n- `references\u002Frules\u002Fdata-fetching.md` - Data fetching strategies\n- `references\u002Frules\u002Fforms.md` - Form implementation\n- `references\u002Frules\u002Fui-components.md` - UI component usage\n- `references\u002Frules\u002Freact-patterns.md` - React component patterns\n- `references\u002Frules\u002Ftranslations.md` - i18n implementation\n",{"name":5,"version":24,"description":7},"1.1.0","main","fe3bb1476c3ec23d8a366eac0fa8cd9f0852360a","skills\u002F.experimental\u002Fhamster-react",0,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgethamster","https:\u002F\u002Ftryhamster.com","We're building the AI-native future of work, unlocking the promised acceleration for your whole team, from idea to impact.","2026-11-05 11:33:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add gethamster\u002Fskills --skill hamster-react",{"tool":40,"command":41},"bunx","bunx skills add gethamster\u002Fskills --skill hamster-react",{"tool":43,"command":44},"pnpm","pnpm dlx skills add gethamster\u002Fskills --skill hamster-react","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002FSKILL.md",true,[48,54,58,62,66,70,74,78],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Frules\u002Fcross-browser-events.md","REFERENCE","参考文档",3341,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fcross-browser-events.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Frules\u002Fdata-fetching.md",4605,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fdata-fetching.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Frules\u002Fforms.md",6199,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fforms.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Frules\u002Fpage-creation.md",4701,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fpage-creation.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Frules\u002Freact-patterns.md",5083,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Freact-patterns.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Frules\u002Fserver-actions.md",3889,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fserver-actions.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Frules\u002Ftranslations.md",3662,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Ftranslations.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Frules\u002Fui-components.md",5040,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-react\u002Freferences\u002Frules\u002Fui-components.md",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7B5MWYW0KE251276S56KQDZ","writing-waterfall-requirements-documents","Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-waterfall-requirements-documents\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7B5MRCXWWPKREPB1CHQ7H90","writing-vision-and-values-statements","Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-vision-and-values-statements\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7B5MKH2CH22YZAHQW3080VQ","writing-system-prompts-for-claude","Write Claude prompts and CLAUDE.md files that supply exact inputs, scope the task, and define done so the first attempt can be checked.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-system-prompts-for-claude\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7B5ME1Y3X9RNRKP5HKHKACZ","writing-page-specific-website-copy","Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-page-specific-website-copy\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7B5M8MQNM8MN8PYH6BVWJ2B","writing-internal-press-releases","How to write an internal press release: the one-page working backwards press release that opens a PR\u002FFAQ document before anything is built.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-internal-press-releases\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7B5M3P3YH1XF37R8PWXXSBK","writing-email-sequences-that-sell","Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-email-sequences-that-sell\u002FSKILL.md",[],[]]