Find the best CLAUDE.md, AGENTS.md and Claude skills

SupabaseSkill

api-types

supabase/supabase/.agents/skills/api-types/SKILL.md

Maintain Supabase API types. Use when changing generated API type declarations, OpenAPI schemas, or investigating API type deployment drift.

No other project uses it yet

SupabaseSkill

ask-the-docs

supabase/supabase/.agents/skills/ask-the-docs/SKILL.md

Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y live?", "is this approach OK for the docs app?", or before writing non-trivial changes under apps/docs/ — especially anything touching the MDX pipeline, markdown generation, content components, federated docs, or contributor-facing authoring patterns, or feature flags and experiments. Can answer architecture questions with Mermaid diagrams when helpful.

No other project uses it yet

SupabaseSkill

clickhouse-logs-queries

supabase/supabase/.agents/skills/clickhouse-logs-queries/SKILL.md

Write, review, and migrate Supabase logs queries against the ClickHouse-backed `logs` table (the `logs.all.otel` analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the `log_attributes` map, querying a log `source` (edge_logs, postgres_logs, auth_logs, etc.), translating an old BigQuery `cross join unnest(metadata)` logs query to ClickHouse, or wiring analytics log SQL in `apps/studio/data/logs` and `apps/studio/components/interfaces/Settings/Logs`. Reach for it even when the user just says "logs query", "Logs Explorer", or pastes a BigQuery logs query to convert, not only when they name ClickHouse.

No other project uses it yet

SupabaseSkill

code-review

supabase/supabase/.agents/skills/code-review/SKILL.md

Review repository changes for correctness, type boundaries, structural quality, and meaningful test coverage. Use for read-only code or PR assessments and development-task readiness checks.

Often used withclose-spec·add-new-model·compare-screenshots

SupabaseSkill

copywriting

supabase/supabase/.agents/skills/copywriting/SKILL.md

Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

Often used withpaywalls·revops·emails

SupabaseReads credentialsSkill

dev-toolbar-review

supabase/supabase/.agents/skills/dev-toolbar-review/SKILL.md

Safety rules for the dev toolbar, PostHog client, and feature flags. Use

No other project uses it yet

SupabaseSkill

edit-the-docs

supabase/supabase/.agents/skills/edit-the-docs/SKILL.md

Restructure, reorder, and improve existing Supabase docs pages under apps/docs: clarity, connective text, section grouping, and brevity. Use when asked to edit, reorganize, restructure, tighten prose, add glue between sections, or split a page edit into stacked PRs. Not for net-new feature drafts, which belong to write-the-docs, and not for PR triage or verification, which belong to review-the-docs.

No other project uses it yet

SupabaseSkill

pm-the-docs

supabase/supabase/.agents/skills/pm-the-docs/SKILL.md

Docs-PM decision support for the "Write the docs" authoring process — makes audience, stage, and cross-cutting scope calls during the Frame and Shape stages (including cross-repo product lookup via universe when accessible, else the public OSS path), and helps decide when a docs question needs to self-serve vs. escalate to a docs PM. Use when framing a new docs page or launch, deciding what product stage or audience a feature targets, judging whether a docs question needs PM sign-off, or confirming which product repos a launch spans.

SupabaseSkill

react-hook-form

supabase/supabase/.agents/skills/react-hook-form/SKILL.md

Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,

SupabaseReads credentialsSkill

review-the-docs

supabase/supabase/.agents/skills/review-the-docs/SKILL.md

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). Covers markdown pipeline, MDX content, tutorials, examples, Studio links, and docs tooling. Use when asked to review docs PRs, self-review a draft branch, check who has approved, verify build output, or evaluate supabase/supabase documentation changes.

No other project uses it yet

SupabaseSkill

safe-sql-execution

supabase/supabase/.agents/skills/safe-sql-execution/SKILL.md

Use 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 and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint that builds/returns SQL for database objects (tables, views, functions, DB triggers, indexes, RLS policies); interpolating a schema/table/column/search/route-param value into SQL text; storing, fetching, or re-running SQL that round-trips from the database (a policy's definition, a function/view definition, a snippet's saved content); and any "Run"/"Apply"/"Execute" action that sends SQL to a project's database (SQL editor run-selection, policy editor apply, snippet runner). Load this BEFORE writing such code, not only when reviewing a finished diff. Skip only for changes that never touch SQL text or execution — styling, unrelated data hooks, non-SQL form validation, or UI layout work.

No other project uses it yet

SupabaseSkill

studio-e2e-tests

supabase/supabase/.agents/skills/studio-e2e-tests/SKILL.md

Write and run Playwright E2E tests for Supabase Studio (e2e/studio).

No other project uses it yet

SupabaseSkill

studio-error-handling

supabase/supabase/.agents/skills/studio-error-handling/SKILL.md

Error display and troubleshooting pattern for Supabase Studio. Use when

SupabaseReads credentialsSkill

studio-mock-api-tests

supabase/supabase/.agents/skills/studio-mock-api-tests/SKILL.md

Component tests for Supabase Studio that mock API requests at the

SupabaseSkill

studio-queries

supabase/supabase/.agents/skills/studio-queries/SKILL.md

React Query conventions for data fetching in Supabase Studio. Use when

SupabaseSkill

studio-shortcuts

supabase/supabase/.agents/skills/studio-shortcuts/SKILL.md

Keyboard shortcut conventions for Supabase Studio. Use when adding a

No other project uses it yet

SupabaseSkill

studio-testing

supabase/supabase/.agents/skills/studio-testing/SKILL.md

Testing strategy for Supabase Studio. Use when selecting, writing,

SupabaseSkill

studio-ui-patterns

supabase/supabase/.agents/skills/studio-ui-patterns/SKILL.md

Design system UI patterns for Supabase Studio. Use when building or updating

No other project uses it yet

SupabaseSkill

telemetry-standards

supabase/supabase/.agents/skills/telemetry-standards/SKILL.md

PostHog event tracking standards for Supabase Studio. Use when adding

No other project uses it yet

SupabaseSkill

test-the-docs

supabase/supabase/.agents/skills/test-the-docs/SKILL.md

Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via `supabase start`). Use after Draft or during Self-review when asked to test the docs, fact-check CLI/SQL/code samples, or produce a verification report for a docs PR. Complements review-the-docs build and review checks; does not replace them.

No other project uses it yet