SupabaseSkillstudio-testing
supabase/supabase/.agents/skills/studio-testing/SKILL.md
Testing strategy for Supabase Studio. Use when writing tests, deciding
Find the best CLAUDE.md, AGENTS.md and Claude skills
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Most stars first · from page 25Worked for most · soon
SupabaseSkillSupabaseSkillstudio-ui-patterns
supabase/supabase/.agents/skills/studio-ui-patterns/SKILL.md
Design system UI patterns for Supabase Studio. Use when building or updating
SupabaseSkilltelemetry-standards
supabase/supabase/.agents/skills/telemetry-standards/SKILL.md
PostHog event tracking standards for Supabase Studio. Use when adding
SupabaseSkilltest-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.
SupabaseSkillvercel-composition-patterns
supabase/supabase/.agents/skills/vercel-composition-patterns/SKILL.md
React composition patterns that scale. Use when refactoring components with
SupabaseSkillvitest
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.
SupabaseSkillwrite-the-docs
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.
SupabaseAGENTS.mdsupabase / apps
supabase/supabase/apps/docs/AGENTS.md
Next.js app router + MDX. Dev server: pnpm dev:docs → http://localhost:3001/docs (the bare / 404s). style-guide/ holds the docs style guide as plain markdown. Load the file you need rather than the whole directory. No tool enforces the guide, so applying it is the author's job, or the skill's. Load these before working. pm-the-docs, write-the-docs, edit-the-docs, ask-the-docs, and review-the-docs back the docs authoring process. See CONTRIBUTING.md for which stage each covers. They apply the style guide above. For architecture questions…
SupabaseAGENTS.mdsupabase / kb
supabase/supabase/apps/kb/AGENTS.md
When starting the dev server, run: Full documentation: https://docs.astro.build Consult these guides before working on related tasks: To run a full production build, run: Content lives under src/content/guides/*.{md,mdx}. Keep it plain GitHub-Flavored Markdown: - No custom/JSX components in guide bodies — content is also exported as plain .md (see below), and a component wouldn't survive that export. - For callouts, use GitHub's native alert syntax (> [!NOTE], > [!TIP], > [!IMPORTANT], > [!WARNING], > [!CAUTION]) — the build renders these…
Supabasellms.txtsupabase / learn
supabase/supabase/apps/learn/public/llms.txt
No summary in the file. Open it to read it.
SupabaseAGENTS.mdsupabase / studio
supabase/supabase/apps/studio/AGENTS.md
Next.js pages router + TanStack Start (mid-migration, see below), React 19. Dev server: pnpm dev:studio → http://localhost:8082. Load the skills matching the task; stack them when a task spans areas: Studio is migrating from the Next.js pages router (pages/) to TanStack Start (routes/). Both runtimes ship side-by-side; the STUDIOFRAMEWORK env var selects which one pnpm dev/build runs (default: next, resolved in scripts/dispatch.js). Full route map and strategy: TANSTACKMIGRATION.md.
SupabaseSkillexplorer
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.
SupabaseCopilot instructionssupabase
supabase/supabase/.github/copilot-instructions.md
You are a code reviewer for a large TypeScript/Next.js/React monorepo. Your reviews must be low-noise and high-signal. The team acts on fewer than 20% of default Copilot suggestions, so every comment you leave must earn its place. Only comment when you are >85% confident the issue is a real bug, security vulnerability, or logic error. If you are unsure, do not comment. Silence is better than noise. Our CI pipeline already validates the following. Never comment on these topics: This…
JuliusBrusseeAGENTS.mdcaveman
JuliusBrussee/caveman/AGENTS.md
Read CLAUDE.md before repository work. Binding routing: this repo owns skills, Engine, and MV3 extension; Agent SDK work belongs in /Users/julb/Desktop/GitHub/caveman-agent-sdk; Browse driver/MCP/benchmark/plugin work belongs in /Users/julb/Desktop/GitHub/caveman-browse; proprietary Pebble product…
JuliusBrusseeCLAUDE.mdcaveman / browse
JuliusBrussee/caveman/browse/CLAUDE.md
Repository routing: do not continue Browse product work here. Source of truth is JuliusBrussee/caveman-browse, local checkout /Users/julb/Desktop/GitHub/caveman-browse. This directory is a consumer copy; edit only for pinned integration, migration/removal, or…
JuliusBrusseeAGENTS.mdcaveman / engine
JuliusBrussee/caveman/engine/AGENTS.md
Detect a payload's type → route to a safety-classed compressor → count the token reduction → store the original for recovery. The stable four-call API (Compress/Retrieve/Detect/Stats) is what the proxy,…
JuliusBrusseeCLAUDE.mdcaveman / engine
JuliusBrussee/caveman/engine/CLAUDE.md
Detect a payload's type → route to a safety-classed compressor → count the token reduction → store the original for recovery. The stable four-call API (Compress/Retrieve/Detect/Stats) is what the proxy,…
JuliusBrusseeAGENTS.mdcaveman / extension
JuliusBrussee/caveman/extension/AGENTS.md
The consumer top-of-funnel: a toggle that, on ChatGPT / Claude / Gemini, prepends the caveman skill directive to each message you send and re-fires the send, so the AI replies…
JuliusBrusseeCLAUDE.mdcaveman / integrations
JuliusBrussee/caveman/integrations/CLAUDE.md
Declarative routing recipes for AI SDKs/frameworks: each recipe is the one-line base-URL shape that points a framework at the byte-safe gateway, with {{baseURL}} (gateway origin) and {{app}} (the /w/<app> attribution…
JuliusBrusseeAGENTS.mdcaveman / mcp
JuliusBrussee/caveman/mcp/AGENTS.md
A thin stdio JSON-RPC adapter exposing the compression engine as five MCP tools to any host (Claude Code, Cursor, …). It owns only the MCP framing; all compression is the…
Agent instruction files
What are agent instruction files?
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.