Do these skills only matter if I am contributing to Supabase Studio?

For most of them, yes. Eleven of the fifteen skills carry conventions specific to Supabase's own dashboard app, Studio, covering things like its React Query data layer, its Playwright end to end tests, and its error handling pattern, and they will not fire on unrelated code. Four skills, copywriting, docs-content, react-hook-form, and vercel-composition-patterns, are not Studio-specific.

What can the supabase MCP server actually do?

It is Supabase's own hosted MCP server, configured in the repository as an HTTP endpoint at mcp.supabase.com. Per Supabase's own documentation it lets an AI assistant run SQL against a project, inspect and generate types from the schema, manage edge functions and storage, and search Supabase's documentation, all through natural language rather than the dashboard UI. It is useful to anyone with a Supabase project, not only people working on this repository.

Why does a Vercel-authored React skill show up inside a Supabase repository?

vercel-composition-patterns is a general purpose skill about React composition: compound components, render props, and context providers. Its own file metadata lists an MIT license and an author of vercel rather than the Supabase team. It sits in the same skill folder as the Studio-specific skills but is not scoped to any Supabase-specific directory, so it reads as a borrowed reference rather than an in-house convention.

supabase/supabase in Claude Code: what is actually inside

By Flowy · Updated 2026-08-28

supabase/supabase is the open source Supabase platform's monorepo. Flowy indexes only its Claude Code components: 15 skills, most of them conventions for building Supabase's own Studio dashboard, plus one hosted MCP server that lets an AI assistant query a real Supabase project's database, schema, and edge functions directly.

What Flowy actually indexes here

supabase/supabase is the open source monorepo behind the Supabase platform: a hosted Postgres database, authentication, and auto-generated REST and GraphQL APIs, among the rest of the stack the project builds as an open source alternative to Firebase. It carries 108,522 GitHub stars, which makes it one of the largest repositories Flowy has crawled.

Flowy does not index that whole codebase. It indexes the narrow slice of it written for Claude Code: 15 skills and one MCP server, 16 components in total. These live in two separate skill folders inside the monorepo, one at the repository root and a second nested inside the Studio app, plus one MCP config at the repository root. Flowy's crawler found all of them.

The Studio-specific skills

Most of what is here exists to keep contributions to Supabase's own dashboard app, Studio, consistent. Eleven of the fifteen skills fall into this group: studio-queries (React Query conventions for the app's data fetching layer), studio-ui-patterns (layout and component choice against the design system), studio-testing, studio-e2e-tests, and studio-mock-api-tests (which kind of test to write, and how to write Playwright and mocked-API tests for the app), studio-error-handling (how a failed request gets shown to a user, including wiring the AI assistant debug button), explorer (the notebook, chat, and SQL-snippet surfaces inside Studio), telemetry-standards (PostHog event naming for the app), dev-toolbar-review (safety rules for the app's dev toolbar and feature flags), clickhouse-logs-queries (writing and migrating the Logs Explorer's ClickHouse SQL), and safe-sql-execution (the security model that lets Studio run a user's own SQL against their own database without allowing attacker-influenced SQL to execute).

None of these fire on a codebase that is not Studio. They are conventions enforcement, not general purpose advice.

The four that are not Studio-specific

copywriting and docs-content cover UI text and the documentation site, and both are scoped to the wider monorepo rather than to Studio alone. react-hook-form documents correct React Hook Form usage anywhere in the codebase. vercel-composition-patterns is the odd one out: its own file metadata lists an MIT license and an author of vercel, and it covers general React composition, compound components, render props, context providers, rather than a Supabase-authored convention. It sits in the same skill folder as the Studio-specific skills but is not scoped to any Supabase-specific directory.

The one live connection: the supabase MCP server

Everything above is a written convention, text an agent reads. The supabase MCP server is different. It is a hosted remote server, wired into the repository as:

{
  "mcpServers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

This connects an agent directly to a real Supabase project instead of to a convention: running SQL, inspecting and generating types from the schema, managing edge functions and storage, and searching Supabase's own documentation, through natural language requests instead of the dashboard UI. It is the one component here that is useful to anyone with a Supabase project, independent of whether they ever open the supabase/supabase codebase itself.

Who this is actually useful for

If you are contributing to Studio, the eleven Studio skills are the reason to have this plugin installed at all: they carry conventions a reviewer would otherwise have to explain in a PR comment. If you are not, the practical value narrows to the MCP server, plus whatever you can borrow by reading react-hook-form or vercel-composition-patterns as reference material for your own React codebase.

How do I install it

Install from the listing page linked at the top of this guide. Flowy indexes what supabase/supabase ships here. It does not own, bundle, or modify it: the skills and the MCP server stay on their author's releases in the source repository, and install from there.

Common questions

Is supabase/supabase a small Claude Code plugin, or the whole Supabase codebase?: It is the real, full open source monorepo behind the Supabase platform, with 108,522 GitHub stars. Flowy only indexes the narrow slice of it written for Claude Code: 15 skills and one MCP server, 16 components in total. The database, auth, and API code that make up the rest of the platform are not part of what an agent reads.
Do these skills only matter if I am contributing to Supabase Studio?: For most of them, yes. Eleven of the fifteen skills carry conventions specific to Supabase's own dashboard app, Studio, covering things like its React Query data layer, its Playwright end to end tests, and its error handling pattern, and they will not fire on unrelated code. Four skills, copywriting, docs-content, react-hook-form, and vercel-composition-patterns, are not Studio-specific.
What can the supabase MCP server actually do?: It is Supabase's own hosted MCP server, configured in the repository as an HTTP endpoint at mcp.supabase.com. Per Supabase's own documentation it lets an AI assistant run SQL against a project, inspect and generate types from the schema, manage edge functions and storage, and search Supabase's documentation, all through natural language rather than the dashboard UI. It is useful to anyone with a Supabase project, not only people working on this repository.
Why does a Vercel-authored React skill show up inside a Supabase repository?: vercel-composition-patterns is a general purpose skill about React composition: compound components, render props, and context providers. Its own file metadata lists an MIT license and an author of vercel rather than the Supabase team. It sits in the same skill folder as the Studio-specific skills but is not scoped to any Supabase-specific directory, so it reads as a borrowed reference rather than an in-house convention.

See the listing and install it Browse every plugin