[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ASSN54TCG7P12M5V69JM3":3,"skill-same:01M74ASSN54TCG7P12M5V69JM3":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},"01M74ASSN54TCG7P12M5V69JM3","studio-ui-patterns",null,"Design system UI patterns for Supabase Studio. Use when building or updating pages, forms, tables, charts, empty states, navigation, cards, alerts, or side panels (sheets). Covers layout selection, component choice, and placement 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-ui-patterns_agents\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: studio-ui-patterns\ndescription: Design system UI patterns for Supabase Studio. Use when building or updating\n  pages, forms, tables, charts, empty states, navigation, cards, alerts, or side panels\n  (sheets). Covers layout selection, component choice, and placement conventions.\n---\n\n# Studio UI Patterns\n\nThe Design System docs and demos are the source of truth. Always check the relevant\ndemo file before composing new UI.\n\n## Layout\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Flayout.mdx`\n\nBuild pages with `PageContainer`, `PageHeader`, and `PageSection`.\n\n| Content type      | `size`      |\n| ----------------- | ----------- |\n| Settings \u002F config | `\"default\"` |\n| Lists \u002F tables    | `\"large\"`   |\n| Full-screen views | `\"full\"`    |\n\n- If filters\u002Fsearch exist on a list page, align table actions with the filters (don't use `PageHeaderAside`\u002F`PageSectionAside` for those actions)\n- If no filters, actions can go in `PageHeaderAside` or `PageSectionAside`\n\nDemos: `page-layout-settings.tsx`, `page-layout-list.tsx`, `page-layout-list-simple.tsx`, `page-layout-detail.tsx`\n(all in `apps\u002Fdesign-system\u002Fregistry\u002Fdefault\u002Fexample\u002F`)\n\n## Forms\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fforms.mdx`\n\n- Use `react-hook-form` + `zod`\n- Use `FormItemLayout` instead of manually composing `FormItem`\u002F`FormLabel`\u002F`FormMessage`\u002F`FormDescription`\n- Wrap inputs with `FormControl_Shadcn_`; use `_Shadcn_` imports from `ui` for primitives\n\nLayout selection:\n\n| Context                                    | Layout                                     | Container                                                  |\n| ------------------------------------------ | ------------------------------------------ | ---------------------------------------------------------- |\n| Page (settings\u002Fconfig)                     | `FormItemLayout layout=\"flex-row-reverse\"` | `Card` (`CardContent` per field; `CardFooter` for actions) |\n| Side panel — wide                          | `FormItemLayout layout=\"horizontal\"`       | `SheetSection`                                             |\n| Side panel — narrow (`size=\"sm\"` or below) | `FormItemLayout layout=\"vertical\"`         | `SheetSection`                                             |\n\nDirty state \u002F submit:\n\n- Destructure `isDirty` from `form.formState` to show Cancel and disable Save\n- Show loading on submit button via `loading` prop\n- If submit button is outside `\u003Cform>`, set a stable `formId` and use `form` prop on the button\n\nDemos: `form-patterns-pagelayout.tsx`, `form-patterns-sidepanel.tsx`\n\n## Tables\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Ftables.mdx`\n\n| Pattern    | Use when                                                                |\n| ---------- | ----------------------------------------------------------------------- |\n| `Table`    | Simple, static, semantic display                                        |\n| Data Table | TanStack-powered; sorting, filtering, pagination; composed per use-case |\n| Data Grid  | Virtualization, column resizing, or complex cell editing                |\n\n- Actions: above the table, aligned right\n- Search\u002Ffilters: above the table, aligned left\n- If table is primary content with no filters, actions can live in the page's primary\u002Fsecondary actions area\n\nDemos: `table-demo.tsx`, `data-table-demo.tsx`, `data-grid-demo.tsx`\n\n## Charts\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fcharts.mdx`\n\n- Use provided chart building blocks; avoid passing raw Recharts components to `ChartContent`\n- Use `useChart` context flags for loading\u002Fdisabled states\n- Keep composition straightforward — avoid over-abstraction\n\nDemos (in `apps\u002Fdesign-system\u002F__registry__\u002Fdefault\u002Fblock\u002F`): `chart-composed-demo.tsx`, `chart-composed-basic.tsx`, `chart-composed-states.tsx`, `chart-composed-metrics.tsx`, `chart-composed-actions.tsx`, `chart-composed-table.tsx`\n\n## Empty States\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fempty-states.mdx`\n\n| Scenario                 | Pattern                                                             |\n| ------------------------ | ------------------------------------------------------------------- |\n| Initial \u002F onboarding     | Presentational empty state with value prop + clear next action      |\n| Data-heavy lists         | Informational empty state matching the list\u002Ftable layout            |\n| Zero results from search | Keep layout consistent with data state to avoid jarring transitions |\n| Missing route            | Centered `Admonition`                                               |\n\nDemos: `empty-state-presentational-icon.tsx`, `empty-state-initial-state-informational.tsx`, `empty-state-zero-items-table.tsx`, `data-grid-empty-state.tsx`, `empty-state-missing-route.tsx`\n\n## Navigation\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fnavigation.mdx`\n\n- Use `NavMenu` for a horizontal list of related views within a consistent page layout\n- Activating an item must trigger a **URL change** — no local-only tab state\n\n## Cards\n\n- Group related information in cards\n- `CardContent` for sections, `CardFooter` for actions\n- Only use `CardHeader`\u002F`CardTitle` when context isn't already provided by surrounding content\n- Use headers\u002Ftitles when multiple cards represent distinct groups (e.g. multiple settings sections)\n\n## Alerts\n\n- Use `Admonition` to call out important actions, restrictions, or critical context\n- Place at the **top of a page's content** (below page title) or **top of the relevant section** (below section title)\n- Use sparingly\n\n## Sheets (Side Panels)\n\nUse a `Sheet` when switching pages would be disruptive and the user needs to maintain context (e.g. selecting a row from a list to edit).\n\nStructure:\n\n- `SheetContent` with `size=\"lg\"` for forms needing horizontal layout\n- Use `SheetHeader`, `SheetTitle`, `SheetSection`, `SheetFooter`\n- Submit\u002Fcancel actions go in `SheetFooter`\n\nForms in sheets:\n\n- `layout=\"horizontal\"` for wider sheets\n- `layout=\"vertical\"` for narrow sheets (`size=\"sm\"` or below)\n","# Studio UI Patterns\n\nThe Design System docs and demos are the source of truth. Always check the relevant\ndemo file before composing new UI.\n\n## Layout\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Flayout.mdx`\n\nBuild pages with `PageContainer`, `PageHeader`, and `PageSection`.\n\n| Content type      | `size`      |\n| ----------------- | ----------- |\n| Settings \u002F config | `\"default\"` |\n| Lists \u002F tables    | `\"large\"`   |\n| Full-screen views | `\"full\"`    |\n\n- If filters\u002Fsearch exist on a list page, align table actions with the filters (don't use `PageHeaderAside`\u002F`PageSectionAside` for those actions)\n- If no filters, actions can go in `PageHeaderAside` or `PageSectionAside`\n\nDemos: `page-layout-settings.tsx`, `page-layout-list.tsx`, `page-layout-list-simple.tsx`, `page-layout-detail.tsx`\n(all in `apps\u002Fdesign-system\u002Fregistry\u002Fdefault\u002Fexample\u002F`)\n\n## Forms\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fforms.mdx`\n\n- Use `react-hook-form` + `zod`\n- Use `FormItemLayout` instead of manually composing `FormItem`\u002F`FormLabel`\u002F`FormMessage`\u002F`FormDescription`\n- Wrap inputs with `FormControl_Shadcn_`; use `_Shadcn_` imports from `ui` for primitives\n\nLayout selection:\n\n| Context                                    | Layout                                     | Container                                                  |\n| ------------------------------------------ | ------------------------------------------ | ---------------------------------------------------------- |\n| Page (settings\u002Fconfig)                     | `FormItemLayout layout=\"flex-row-reverse\"` | `Card` (`CardContent` per field; `CardFooter` for actions) |\n| Side panel — wide                          | `FormItemLayout layout=\"horizontal\"`       | `SheetSection`                                             |\n| Side panel — narrow (`size=\"sm\"` or below) | `FormItemLayout layout=\"vertical\"`         | `SheetSection`                                             |\n\nDirty state \u002F submit:\n\n- Destructure `isDirty` from `form.formState` to show Cancel and disable Save\n- Show loading on submit button via `loading` prop\n- If submit button is outside `\u003Cform>`, set a stable `formId` and use `form` prop on the button\n\nDemos: `form-patterns-pagelayout.tsx`, `form-patterns-sidepanel.tsx`\n\n## Tables\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Ftables.mdx`\n\n| Pattern    | Use when                                                                |\n| ---------- | ----------------------------------------------------------------------- |\n| `Table`    | Simple, static, semantic display                                        |\n| Data Table | TanStack-powered; sorting, filtering, pagination; composed per use-case |\n| Data Grid  | Virtualization, column resizing, or complex cell editing                |\n\n- Actions: above the table, aligned right\n- Search\u002Ffilters: above the table, aligned left\n- If table is primary content with no filters, actions can live in the page's primary\u002Fsecondary actions area\n\nDemos: `table-demo.tsx`, `data-table-demo.tsx`, `data-grid-demo.tsx`\n\n## Charts\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fcharts.mdx`\n\n- Use provided chart building blocks; avoid passing raw Recharts components to `ChartContent`\n- Use `useChart` context flags for loading\u002Fdisabled states\n- Keep composition straightforward — avoid over-abstraction\n\nDemos (in `apps\u002Fdesign-system\u002F__registry__\u002Fdefault\u002Fblock\u002F`): `chart-composed-demo.tsx`, `chart-composed-basic.tsx`, `chart-composed-states.tsx`, `chart-composed-metrics.tsx`, `chart-composed-actions.tsx`, `chart-composed-table.tsx`\n\n## Empty States\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fempty-states.mdx`\n\n| Scenario                 | Pattern                                                             |\n| ------------------------ | ------------------------------------------------------------------- |\n| Initial \u002F onboarding     | Presentational empty state with value prop + clear next action      |\n| Data-heavy lists         | Informational empty state matching the list\u002Ftable layout            |\n| Zero results from search | Keep layout consistent with data state to avoid jarring transitions |\n| Missing route            | Centered `Admonition`                                               |\n\nDemos: `empty-state-presentational-icon.tsx`, `empty-state-initial-state-informational.tsx`, `empty-state-zero-items-table.tsx`, `data-grid-empty-state.tsx`, `empty-state-missing-route.tsx`\n\n## Navigation\n\nDocs: `apps\u002Fdesign-system\u002Fcontent\u002Fdocs\u002Fui-patterns\u002Fnavigation.mdx`\n\n- Use `NavMenu` for a horizontal list of related views within a consistent page layout\n- Activating an item must trigger a **URL change** — no local-only tab state\n\n## Cards\n\n- Group related information in cards\n- `CardContent` for sections, `CardFooter` for actions\n- Only use `CardHeader`\u002F`CardTitle` when context isn't already provided by surrounding content\n- Use headers\u002Ftitles when multiple cards represent distinct groups (e.g. multiple settings sections)\n\n## Alerts\n\n- Use `Admonition` to call out important actions, restrictions, or critical context\n- Place at the **top of a page's content** (below page title) or **top of the relevant section** (below section title)\n- Use sparingly\n\n## Sheets (Side Panels)\n\nUse a `Sheet` when switching pages would be disruptive and the user needs to maintain context (e.g. selecting a row from a list to edit).\n\nStructure:\n\n- `SheetContent` with `size=\"lg\"` for forms needing horizontal layout\n- Use `SheetHeader`, `SheetTitle`, `SheetSection`, `SheetFooter`\n- Submit\u002Fcancel actions go in `SheetFooter`\n\nForms in sheets:\n\n- `layout=\"horizontal\"` for wider sheets\n- `layout=\"vertical\"` for narrow sheets (`size=\"sm\"` or below)\n",{"name":5,"description":7},"main","5593cf3c72898ea9fc67225d452fe38f866ba6dd",".claude\u002F_archive\u002Fskills-batch2\u002Fstudio-ui-patterns_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-ui-patterns",{"tool":35,"command":36},"bunx","bunx skills add aicreator350\u002FaurionOFFICIELLE --skill studio-ui-patterns",{"tool":38,"command":39},"pnpm","pnpm dlx skills add aicreator350\u002FaurionOFFICIELLE --skill studio-ui-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.claude\u002F_archive\u002Fskills-batch2\u002Fstudio-ui-patterns_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",[],[]]