react-hook-form
supabase/supabase/.agents/skills/react-hook-form/SKILL.md
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
supabase/supabase/.agents/skills/react-hook-form/SKILL.md
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
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.
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.
supabase/supabase/.agents/skills/studio-e2e-tests/SKILL.md
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
supabase/supabase/.agents/skills/studio-error-handling/SKILL.md
Error display and troubleshooting pattern for Supabase Studio. Use when
supabase/supabase/.agents/skills/studio-mock-api-tests/SKILL.md
Component tests for Supabase Studio that mock API requests at the
supabase/supabase/.agents/skills/studio-queries/SKILL.md
React Query conventions for data fetching in Supabase Studio. Use when
supabase/supabase/.agents/skills/studio-shortcuts/SKILL.md
Keyboard shortcut conventions for Supabase Studio. Use when adding a
supabase/supabase/.agents/skills/studio-testing/SKILL.md
Testing strategy for Supabase Studio. Use when writing tests, deciding
supabase/supabase/.agents/skills/studio-ui-patterns/SKILL.md
Design system UI patterns for Supabase Studio. Use when building or updating
supabase/supabase/.agents/skills/telemetry-standards/SKILL.md
PostHog event tracking standards for Supabase Studio. Use when adding
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.
supabase/supabase/.agents/skills/vercel-composition-patterns/SKILL.md
React composition patterns that scale. Use when refactoring components with
supabase/supabase/.agents/skills/vitest/SKILL.md
Vitest API and config reference (Jest-compatible) — mocking with vi.*, spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering. Use for Vitest API and configuration questions anywhere in the monorepo; for Studio-specific test strategy and component-test setup, start with studio-testing and studio-mock-api-tests.
supabase/supabase/.agents/skills/write-the-docs/SKILL.md
Draft new or updated Supabase docs content for a feature or launch, grounded in product intent (Linear when available), a read of the actual code, and the docs style guide. Use when asked to write docs for a new feature, a product launch, or a Linear ticket that needs net-new content rather than a bug fix. Not for implementing existing docs bug reports — use work-linear-issue for that. Not for restructuring existing pages — use edit-the-docs for that.
supabase/supabase/apps/studio/.claude/skills/explorer/SKILL.md
Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.
JuliusBrussee/caveman/skills/cavecrew/SKILL.md
When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.
JuliusBrussee/caveman/skills/caveman-commit/SKILL.md
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
JuliusBrussee/caveman/skills/caveman-compress/SKILL.md
Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Trigger: /caveman-compress.
JuliusBrussee/caveman/skills/caveman-discover/SKILL.md
Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.