Official agent skill

Studio UI Patterns

Design system UI patterns for Supabase Studio. An agent skill from supabase/supabase.

OfficialApache-2.0Auto-check passedFrontend & Design

Install Studio UI Patterns

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .claude/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .claude/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .agents/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .agents/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .cursor/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .cursor/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/supabase/supabase.git --path .agents/skills/studio-ui-patterns

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .gemini/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .gemini/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .github/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .github/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add supabase/supabase --skill studio-ui-patterns -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-ui-patterns --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/studio-ui-patterns .opencode/skills/studio-ui-patterns && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "studio-ui-patterns" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-ui-patterns into .opencode/skills/studio-ui-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-ui-patterns", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: studio-ui-patterns
GitHub stars: 111k
Token cost: ~1.7k tokens
SKILL.md length: 557 words
Files: 1
Skills in repo: 22
Repo updated: Oct 9, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Design system UI patterns for Supabase Studio. An agent skill from supabase/supabase.

Side panels (sheets)
SKILL.md covers Layout, Forms, Tables and Charts, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Tasks that involve Design systems

What it does

Studio UI Patterns is an agent skill from supabase/supabase, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems. It works with Supabase. The repository describes itself as: The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications. The licence is Apache-2.0.

When your agent uses it

Side panels (sheets)
Tasks that involve Design systems

Example prompts

“/studio-ui-patterns”

What it can do on your machine

Read from SKILL.md and the folder at commit 0b85e0d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Studio UI Patterns loads about 1.7k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from supabase/supabase at commit 0b85e0d, republished under its Apache-2.0 licence (© supabase). 557 words, ~1,660 tokens.

Download SKILL.mdSave it as .claude/skills/studio-ui-patterns/SKILL.md (or your agent's skills folder).

name: studio-ui-patterns
description: 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.

Studio UI Patterns

The Design System docs and demos are the source of truth. Always check the relevant demo file before composing new UI.

Layout

Docs: apps/design-system/content/docs/ui-patterns/layout.mdx

Build pages with PageContainer, PageHeader, and PageSection.

Content type	`size`
Settings / config	`"default"`
Lists / tables	`"large"`
Full-screen views	`"full"`

If filters/search exist on a list page, align table actions with the filters (don't use PageHeaderAside/PageSectionAside for those actions)
If no filters, actions can go in PageHeaderAside or PageSectionAside

Demos: page-layout-settings.tsx, page-layout-list.tsx, page-layout-list-simple.tsx, page-layout-detail.tsx (all in apps/design-system/registry/default/example/)

Forms

Docs: apps/design-system/content/docs/ui-patterns/forms.mdx

Use react-hook-form + zod
Use FormItemLayout instead of manually composing FormItem/FormLabel/FormMessage/FormDescription
Wrap inputs with FormControl; import primitives from ui

Layout selection:

Context	Layout	Container
Page (settings/config)	`FormItemLayout layout="flex-row-reverse"`	`Card` (`CardContent` per field; `CardFooter` for actions)
Side panel — wide	`FormItemLayout layout="horizontal"`	`SheetSection`
Side panel — narrow (`size="sm"` or below)	`FormItemLayout layout="vertical"`	`SheetSection`

Dirty state / submit:

Use isDirty to show Cancel and disable Save. Destructure it from form.formState only in the component that owns useForm; anywhere else subscribe with useFormState({ control }) (see the react-hook-form skill)
Show loading on submit button via loading prop
If submit button is outside <form>, set a stable formId and use form prop on the button

Demos: form-patterns-pagelayout.tsx, form-patterns-sidepanel.tsx

Tables

Docs: apps/design-system/content/docs/ui-patterns/tables.mdx

Pattern	Use when
`Table`	Simple, static, semantic display
Data Table	TanStack-powered; sorting, filtering, pagination; composed per use-case
Data Grid	Virtualization, column resizing, or complex cell editing

Actions: above the table, aligned right
Search/filters: above the table, aligned left
If table is primary content with no filters, actions can live in the page's primary/secondary actions area

Demos: table-demo.tsx, data-table-demo.tsx, data-grid-demo.tsx

Charts

Docs: apps/design-system/content/docs/ui-patterns/charts.mdx

Use provided chart building blocks; avoid passing raw Recharts components to ChartContent
Use useChart context flags for loading/disabled states
Keep composition straightforward — avoid over-abstraction

Demos (in apps/design-system/registry/default/block/): chart-composed-demo.tsx, chart-composed-basic.tsx, chart-composed-states.tsx, chart-composed-metrics.tsx, chart-composed-actions.tsx, chart-composed-table.tsx

Empty States

Docs: apps/design-system/content/docs/ui-patterns/empty-states.mdx

Scenario	Pattern
Initial / onboarding	Presentational empty state with value prop + clear next action
Data-heavy lists	Informational empty state matching the list/table layout
Zero results from search	Keep layout consistent with data state to avoid jarring transitions
Missing route	Centered `Admonition`

Demos: 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

Show full SKILL.md (214 more words)Show less

Docs: apps/design-system/content/docs/ui-patterns/navigation.mdx

Use NavMenu for a horizontal list of related views within a consistent page layout
Activating an item must trigger a URL change — no local-only tab state

Cards

Group related information in cards
CardContent for sections, CardFooter for actions
Only use CardHeader/CardTitle when context isn't already provided by surrounding content
Use headers/titles when multiple cards represent distinct groups (e.g. multiple settings sections)

Alerts

Use Admonition to call out important actions, restrictions, or critical context
Place at the top of a page's content (below page title) or top of the relevant section (below section title)
Use sparingly

Sheets (Side Panels)

Use 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).

Structure:

SheetContent with size="lg" for forms needing horizontal layout
Use SheetHeader, SheetTitle, SheetSection, SheetFooter
Submit/cancel actions go in SheetFooter

Forms in sheets:

layout="horizontal" for wider sheets
layout="vertical" for narrow sheets (size="sm" or below)
When the sheet contains a form, wire dirty dismissal with useConfirmOnClose + DiscardChangesConfirmationDialog (Cancel, Escape, and backdrop). Source of truth: apps/design-system/content/docs/ui-patterns/modality.mdx (Dirty form dismissal). Also see the react-hook-form skill for isDirty destructuring.

Copy

Source of truth: apps/design-system/content/docs/copywriting.mdx — sentence case, title case, proper nouns, voice and tone.

When changing visible copy, grep e2e/studio/ for the old string.

Files

Just SKILL.md in .agents/skills/studio-ui-patterns of supabase/supabase.

Open the folder on GitHubat commit 0b85e0d

Compare with similar skills

Studio UI Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Studio UI Patterns compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Studio UI Patterns this skillsupabase/supabase	111k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Designlang TokensManavarya09/design-extract	4.2k	—	~205	Automated safety check: Pass	MIT	today
Docs LookupProgrammerAnthony/Expert-Coding-Harness	235	—	~640	Automated safety check: Pass	MIT	5 mo ago
Impeccablebestofjs/bestofjs	3.1k	27 repos	~2.6k	Automated safety check: Pass	MIT	4 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Designlang Tokens
Manavarya09/design-extract
A skill your agent uses when styling UI for supabase.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
4.2k GitHub stars~205 tokensUpdated today
Frontend & DesignAuto-check passed
Docs Lookup
ProgrammerAnthony/Expert-Coding-Harness
通过 Context7 MCP 获取库和框架的实时最新文档，而非依赖训练数据，防止 API 幻觉。适用于查询任何库或框架的用法、配置、示例代码。触发词：怎么用、怎么配置、API参考、文档、示例代码、用法、接口、库文档、框架文档、documentation、docs、how to use、API…
235 GitHub stars~640 tokensUpdated 5 mo ago
Frontend & DesignAuto-check passed
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 27 repos~2.6k tokens
Frontend & DesignAuto-check passed
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
795 GitHub starsUsed in 13 repos~2.5k tokens
Frontend & DesignAuto-check passed

More from supabase/supabase

All 22 skills in this repo

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
Auto-check passed
Clickhouse Logs Queries
supabase/supabase
Official
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
111k GitHub stars~2.4k tokensUpdated today
Auto-check passed
Review The Docs
supabase/supabase
Official
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
111k GitHub stars~4.6k tokensUpdated today
Auto-check passed
Vitest
supabase/supabase
Official
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
111k GitHub starsUsed in 12 repos~1.1k tokens
Auto-check passed
Safe SQL Execution
supabase/supabase
Official
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
111k GitHub stars~4.2k tokensUpdated today
Auto-check passed
Studio E2E Tests
supabase/supabase
Official
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
111k GitHub stars~2.8k tokensUpdated today
Auto-check passed

Works with

Supabase

Questions about Studio UI Patterns

What does Studio UI Patterns do?

Design system UI patterns for Supabase Studio. An agent skill from supabase/supabase. Studio UI Patterns is an agent skill from supabase/supabase, published by the product's own GitHub organization. Design system UI patterns for Supabase Studio.

When should I use Studio UI Patterns?

Studio UI Patterns fits situations like: side panels (sheets); tasks that involve Design systems.

How do I install Studio UI Patterns in Claude Code?

Run `npx skills add supabase/supabase --skill studio-ui-patterns -a claude-code`. Or copy the skill folder (.agents/skills/studio-ui-patterns in supabase/supabase) into .claude/skills/studio-ui-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Studio UI Patterns in Codex?

Run `npx skills add supabase/supabase --skill studio-ui-patterns -a codex`. Or copy the skill folder (.agents/skills/studio-ui-patterns in supabase/supabase) into .agents/skills/studio-ui-patterns in your project. Codex loads it when a task matches its description.

Can I use Studio UI Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add supabase/supabase --skill studio-ui-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/studio-ui-patterns, .gemini/skills/studio-ui-patterns, .github/skills/studio-ui-patterns and .opencode/skills/studio-ui-patterns in your project.

What does Studio UI Patterns need to run?

SKILL.md names no scripts, command-line tools or credentials: Studio UI Patterns is instructions for the agent only.

Does Studio UI Patterns access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Studio UI Patterns safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Studio UI Patterns use?

Studio UI Patterns is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Studio UI Patterns use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Studio UI Patterns?

Skills that share tags, products or a category with Studio UI Patterns: Designlang Tokens (Manavarya09/design-extract, 4.2k stars), Docs Lookup (ProgrammerAnthony/Expert-Coding-Harness, 235 stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Studio UI Patterns?

supabase (a GitHub organization, an official publisher) maintains it in supabase/supabase, which has 111,256 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 9, 2026.

Source: supabase/supabase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Studio UI Patterns

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Studio UI Patterns

Layout

Forms

Tables

Charts

Empty States

Navigation

Cards

Alerts

Sheets (Side Panels)

Copy

Files

Compare with similar skills

Similar skills

More from supabase/supabase

Related

Questions about Studio UI Patterns