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.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
OpenAISkillopenai/codex/codex-rs/skills/src/assets/samples/skill-creator/SKILL.md
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
Steady14 mentions in 2 weeks
189 projects use a version of this
Often used withtaskflow-inbox-triagemermaid-diagram-generatorecosystem-reference
OpenAIAGENTS.mdopenai/codex/codex-rs/tui/src/bottom_pane/AGENTS.md
When changing the paste-burst or chat-composer state machines in this folder, keep the docs in sync: - Update the relevant module docs (chat_composer.rs and/or paste_burst.rs) so they remain a readable, top-down explanation of the current behavior. - Keep implementations/docstrings aligned unless a divergence is intentional and documented. Practical check: - After edits, sanity-check that docs mention only APIs/behavior that exist in code (especially the Enter/newline paths and disable_paste_burst semantics).
Steady14 mentions in 2 weeks
No other project uses it yet
SupabaseAGENTS.mdsupabase/supabase/AGENTS.md
pnpm 11 + Turborepo monorepo. Requires Node 24 (see .nvmrc). Every PR must pass typecheck + lint (one workflow), Prettier, and a typos check. Other checks are path-filtered: Studio unit tests/build and the lint ratchet (ESLint warning count must not increase) run on apps/studio/** changes and the Tailwind class rules (shadcn/*) for www, docs, design-system, ui-library, learn, and kb; app-specific test suites run on their own paths. Never hand-edit generated files: packages/api-types/types/**, **/routeTree.gen.ts, `**/__
SupabaseSkillsupabase/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
SupabaseSkillsupabase/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.
SupabaseSkillsupabase/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
SupabaseSkillsupabase/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-specadd-new-modelcompare-screenshots
SupabaseSkillsupabase/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.
188 projects use a version of this
SupabaseSkillsupabase/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
SupabaseSkillsupabase/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.
SupabaseSkillsupabase/supabase/.agents/skills/react-hook-form/SKILL.md
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
8 projects use a version of this
SupabaseSkillsupabase/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
SupabaseSkillsupabase/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
SupabaseSkillsupabase/supabase/.agents/skills/studio-error-handling/SKILL.md
Error display and troubleshooting pattern for Supabase Studio. Use when
SupabaseSkillsupabase/supabase/.agents/skills/studio-queries/SKILL.md
React Query conventions for data fetching in Supabase Studio. Use when
SupabaseSkillsupabase/supabase/.agents/skills/studio-shortcuts/SKILL.md
Keyboard shortcut conventions for Supabase Studio. Use when adding a
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/studio-testing/SKILL.md
Testing strategy for Supabase Studio. Use when selecting, writing,
SupabaseSkillsupabase/supabase/.agents/skills/studio-ui-patterns/SKILL.md
Design system UI patterns for Supabase Studio. Use when building or updating
SupabaseSkillsupabase/supabase/.agents/skills/telemetry-standards/SKILL.md
PostHog event tracking standards for Supabase Studio. Use when adding
No other project uses it yet
SupabaseSkillsupabase/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
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 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.
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.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
