[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74AS6F0MX4X60KMVDSQDFAC":3,"skill-same:01M74AS6F0MX4X60KMVDSQDFAC":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M74AS6F0MX4X60KMVDSQDFAC","studio-best-practices",null,"React and TypeScript best practices for Supabase Studio. Use when writing or reviewing Studio components — covers boolean naming, component structure, loading\u002Ferror states, state management, custom hooks, event handlers, conditional rendering, performance, and TypeScript conventions.","aicreator350\u002FaurionOFFICIELLE","aicreator350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217751428?v=4","01M731QVHB22WCM6PDX5VFN1RV","01M731QVJ0TAD058M1SW9MY548",0,"MIT","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002F_archive\u002Fskills-batch2\u002Fstudio-best-practices_agents\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: studio-best-practices\ndescription: React and TypeScript best practices for Supabase Studio. Use when writing\n  or reviewing Studio components — covers boolean naming, component structure, loading\u002Ferror\n  states, state management, custom hooks, event handlers, conditional rendering,\n  performance, and TypeScript conventions.\n---\n\n# Studio Best Practices\n\nApplies to `apps\u002Fstudio\u002F**\u002F*.{ts,tsx}`.\n\n## Boolean Naming\n\nUse descriptive prefixes — derive from existing state rather than storing separately:\n\n- `is` — state\u002Fidentity: `isLoading`, `isPaused`, `isNewRecord`\n- `has` — possession: `hasPermission`, `hasData`\n- `can` — capability: `canUpdateColumns`, `canDelete`\n- `should` — conditional behavior: `shouldFetch`, `shouldRender`\n\nExtract complex conditions into named variables:\n\n```tsx\n\u002F\u002F ❌ inline multi-condition\n{\n  !isSchemaLocked && isTableLike(selectedTable) && canUpdateColumns && !isLoading && \u003CButton \u002F>\n}\n\n\u002F\u002F ✅ named variable\nconst canShowAddButton =\n  !isSchemaLocked && isTableLike(selectedTable) && canUpdateColumns && !isLoading\n{\n  canShowAddButton && \u003CButton \u002F>\n}\n```\n\nDerive booleans — don't store them:\n\n```tsx\n\u002F\u002F ❌ stored derived state\nconst [isFormValid, setIsFormValid] = useState(false)\nuseEffect(() => {\n  setIsFormValid(name.length > 0 && email.includes('@'))\n}, [name, email])\n\n\u002F\u002F ✅ derived\nconst isFormValid = name.length > 0 && email.includes('@')\n```\n\n## Component Structure\n\nSee `vercel-composition-patterns` skill for compound component and composition patterns.\n\nKeep components under 200–300 lines. Split when you see:\n\n- Multiple distinct UI sections\n- Complex conditional rendering\n- Multiple unrelated `useState` calls\n- Hard to understand at a glance\n\nCo-locate sub-components in the same directory as the parent. Avoid barrel re-export files.\n\nExtract repeated JSX patterns into small components.\n\n## Data Fetching\n\nAll data fetching uses TanStack Query (React Query). See `studio-queries` skill for query\u002Fmutation patterns and `studio-error-handling` skill for error display conventions.\n\n### Loading \u002F Error \u002F Success Pattern\n\nTop level:\n\n```tsx\nconst { data, error, isLoading, isError, isSuccess } = useQuery(...)\n\nif (isLoading) return \u003CGenericSkeletonLoader \u002F>\nif (isError) return \u003CAlertError error={error} subject=\"Failed to load data\" \u002F>\nif (isSuccess && data.length === 0) return \u003CEmptyState \u002F>\nreturn \u003CDataDisplay data={data} \u002F>\n```\n\nUse early returns — avoid deeply nested conditionals.\n\nInline:\n\n```tsx\n\u003Cdiv>\n  {isLoading && \u003CInlineLoader \u002F>}\n  {isError && \u003CInlineError error={error} \u002F>}\n  {isSuccess && data.length === 0 && \u003CEmptyState \u002F>}\n  {isSuccess && data.length > 0 && \u003CDataDisplay data={data} \u002F>}\n\u003C\u002Fdiv>\n```\n\n## State Management\n\nKeep state as local as possible; lift only when needed.\n\nGroup related form state with `react-hook-form` rather than multiple `useState` calls. See `studio-ui-patterns` skill for form layout and component conventions.\n\n```tsx\n\u002F\u002F ❌ multiple related useState\nconst [name, setName] = useState('')\nconst [email, setEmail] = useState('')\n\n\u002F\u002F ✅ grouped with react-hook-form\nconst form = useForm\u003CFormValues>({ defaultValues: { name: '', email: '' } })\n```\n\n## Custom Hooks\n\nExtract complex or reusable logic into hooks. Return objects, not arrays:\n\n```tsx\n\u002F\u002F ❌ array return (hard to extend)\nreturn [value, toggle]\n\n\u002F\u002F ✅ object return\nreturn { value, toggle, setTrue, setFalse }\n```\n\n## Event Handlers\n\n- Prop callbacks: `on` prefix (`onClose`, `onSave`)\n- Internal handlers: `handle` prefix (`handleSubmit`, `handleCancel`)\n\nUse `useCallback` for handlers passed to memoized children; avoid unnecessary inline arrow functions.\n\n## Conditional Rendering\n\n```tsx\n\u002F\u002F Simple show\u002Fhide\n\u003C>{isVisible && \u003CComponent \u002F>}\u003C\u002F>\n\n\u002F\u002F Binary choice\n\u003C>{isLoading ? \u003CSpinner \u002F> : \u003CContent \u002F>}\u003C\u002F>\n\n\u002F\u002F Multiple conditions — use early returns, not nested ternaries\nif (isLoading) return \u003CSpinner \u002F>\nif (isError) return \u003CError \u002F>\nreturn \u003CContent \u002F>\n```\n\n## Performance\n\n`useMemo` for genuinely expensive computations (measured, not assumed). Don't wrap everything — only optimize when you have a measured problem or are passing values to memoized children.\n\n## TypeScript\n\nDefine prop interfaces explicitly. Use discriminated unions for complex state:\n\n```tsx\ntype AsyncState\u003CT> =\n  | { status: 'idle' }\n  | { status: 'loading' }\n  | { status: 'success'; data: T }\n  | { status: 'error'; error: Error }\n```\n\nAvoid `as any` \u002F `as Type` casts. Validate at boundaries with zod:\n\n```tsx\n\u002F\u002F ❌ type cast\nconst user = apiResponse as User\n\n\u002F\u002F ✅ zod parse\nconst user = userSchema.parse(apiResponse)\n\u002F\u002F or safe:\nconst result = userSchema.safeParse(apiResponse)\n```\n\n## Testing\n\nExtract logic into `.utils.ts` pure functions and test exhaustively. See the `studio-testing` skill for the full testing strategy and decision tree.\n","# Studio Best Practices\n\nApplies to `apps\u002Fstudio\u002F**\u002F*.{ts,tsx}`.\n\n## Boolean Naming\n\nUse descriptive prefixes — derive from existing state rather than storing separately:\n\n- `is` — state\u002Fidentity: `isLoading`, `isPaused`, `isNewRecord`\n- `has` — possession: `hasPermission`, `hasData`\n- `can` — capability: `canUpdateColumns`, `canDelete`\n- `should` — conditional behavior: `shouldFetch`, `shouldRender`\n\nExtract complex conditions into named variables:\n\n```tsx\n\u002F\u002F ❌ inline multi-condition\n{\n  !isSchemaLocked && isTableLike(selectedTable) && canUpdateColumns && !isLoading && \u003CButton \u002F>\n}\n\n\u002F\u002F ✅ named variable\nconst canShowAddButton =\n  !isSchemaLocked && isTableLike(selectedTable) && canUpdateColumns && !isLoading\n{\n  canShowAddButton && \u003CButton \u002F>\n}\n```\n\nDerive booleans — don't store them:\n\n```tsx\n\u002F\u002F ❌ stored derived state\nconst [isFormValid, setIsFormValid] = useState(false)\nuseEffect(() => {\n  setIsFormValid(name.length > 0 && email.includes('@'))\n}, [name, email])\n\n\u002F\u002F ✅ derived\nconst isFormValid = name.length > 0 && email.includes('@')\n```\n\n## Component Structure\n\nSee `vercel-composition-patterns` skill for compound component and composition patterns.\n\nKeep components under 200–300 lines. Split when you see:\n\n- Multiple distinct UI sections\n- Complex conditional rendering\n- Multiple unrelated `useState` calls\n- Hard to understand at a glance\n\nCo-locate sub-components in the same directory as the parent. Avoid barrel re-export files.\n\nExtract repeated JSX patterns into small components.\n\n## Data Fetching\n\nAll data fetching uses TanStack Query (React Query). See `studio-queries` skill for query\u002Fmutation patterns and `studio-error-handling` skill for error display conventions.\n\n### Loading \u002F Error \u002F Success Pattern\n\nTop level:\n\n```tsx\nconst { data, error, isLoading, isError, isSuccess } = useQuery(...)\n\nif (isLoading) return \u003CGenericSkeletonLoader \u002F>\nif (isError) return \u003CAlertError error={error} subject=\"Failed to load data\" \u002F>\nif (isSuccess && data.length === 0) return \u003CEmptyState \u002F>\nreturn \u003CDataDisplay data={data} \u002F>\n```\n\nUse early returns — avoid deeply nested conditionals.\n\nInline:\n\n```tsx\n\u003Cdiv>\n  {isLoading && \u003CInlineLoader \u002F>}\n  {isError && \u003CInlineError error={error} \u002F>}\n  {isSuccess && data.length === 0 && \u003CEmptyState \u002F>}\n  {isSuccess && data.length > 0 && \u003CDataDisplay data={data} \u002F>}\n\u003C\u002Fdiv>\n```\n\n## State Management\n\nKeep state as local as possible; lift only when needed.\n\nGroup related form state with `react-hook-form` rather than multiple `useState` calls. See `studio-ui-patterns` skill for form layout and component conventions.\n\n```tsx\n\u002F\u002F ❌ multiple related useState\nconst [name, setName] = useState('')\nconst [email, setEmail] = useState('')\n\n\u002F\u002F ✅ grouped with react-hook-form\nconst form = useForm\u003CFormValues>({ defaultValues: { name: '', email: '' } })\n```\n\n## Custom Hooks\n\nExtract complex or reusable logic into hooks. Return objects, not arrays:\n\n```tsx\n\u002F\u002F ❌ array return (hard to extend)\nreturn [value, toggle]\n\n\u002F\u002F ✅ object return\nreturn { value, toggle, setTrue, setFalse }\n```\n\n## Event Handlers\n\n- Prop callbacks: `on` prefix (`onClose`, `onSave`)\n- Internal handlers: `handle` prefix (`handleSubmit`, `handleCancel`)\n\nUse `useCallback` for handlers passed to memoized children; avoid unnecessary inline arrow functions.\n\n## Conditional Rendering\n\n```tsx\n\u002F\u002F Simple show\u002Fhide\n\u003C>{isVisible && \u003CComponent \u002F>}\u003C\u002F>\n\n\u002F\u002F Binary choice\n\u003C>{isLoading ? \u003CSpinner \u002F> : \u003CContent \u002F>}\u003C\u002F>\n\n\u002F\u002F Multiple conditions — use early returns, not nested ternaries\nif (isLoading) return \u003CSpinner \u002F>\nif (isError) return \u003CError \u002F>\nreturn \u003CContent \u002F>\n```\n\n## Performance\n\n`useMemo` for genuinely expensive computations (measured, not assumed). Don't wrap everything — only optimize when you have a measured problem or are passing values to memoized children.\n\n## TypeScript\n\nDefine prop interfaces explicitly. Use discriminated unions for complex state:\n\n```tsx\ntype AsyncState\u003CT> =\n  | { status: 'idle' }\n  | { status: 'loading' }\n  | { status: 'success'; data: T }\n  | { status: 'error'; error: Error }\n```\n\nAvoid `as any` \u002F `as Type` casts. Validate at boundaries with zod:\n\n```tsx\n\u002F\u002F ❌ type cast\nconst user = apiResponse as User\n\n\u002F\u002F ✅ zod parse\nconst user = userSchema.parse(apiResponse)\n\u002F\u002F or safe:\nconst result = userSchema.safeParse(apiResponse)\n```\n\n## Testing\n\nExtract logic into `.utils.ts` pure functions and test exhaustively. See the `studio-testing` skill for the full testing strategy and decision tree.\n",{"name":5,"description":7},"main","5593cf3c72898ea9fc67225d452fe38f866ba6dd",".claude\u002F_archive\u002Fskills-batch2\u002Fstudio-best-practices_agents","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE","https:\u002F\u002Fgithub.com\u002Faicreator350","2026-05-18 03:39:30",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add aicreator350\u002FaurionOFFICIELLE --skill studio-best-practices",{"tool":35,"command":36},"bunx","bunx skills add aicreator350\u002FaurionOFFICIELLE --skill studio-best-practices",{"tool":38,"command":39},"pnpm","pnpm dlx skills add aicreator350\u002FaurionOFFICIELLE --skill studio-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002F_archive\u002Fskills-batch2\u002Fstudio-best-practices_agents\u002FSKILL.md",true,[],[44,53,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":48,"licenseFileUrl":49,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M74CAJWR9WB6DX1HF2V461Y0","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M74CAFWC2H75GJ81B39C9RSW","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M74CA9N2HTGCKJ93AE9NQMHA","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M74CA364D4EVDXZZQRVK1Z73","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M74C9YQZX1GVS18V0AYCYPZE","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M74C9SEYD6F764Q1JACZX3A6","vercel-cli-with-tokens","Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[]]