How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Significant-GravitasAGENTS.mdSignificant-Gravitas/AutoGPT/AGENTS.md
available use `unknown` ## Testing - Backend: `poetry run test` (runs pytest with a docker based postgres + prisma). - Frontend integration tests: `pnpm test:unit` (Vitest + RTL + MSW, primary testing approach). - Frontend
SupabaseAGENTS.mdsupabase/supabase/AGENTS.md
telemetry constants, feature flags | | `packages/api-types` | Generated platform Management API types | | `packages/pg-meta` | SQL builders for Postgres introspection (`SafeSqlFragment`) | | `packages/shared-data` | Static data: pricing, plans, regions, error codes | | `e2e/studio`, `e2e/docs` | Playwright E2E tests
bytedanceAGENTS.mdbytedance/deer-flow/backend/AGENTS.md
scheduler.multi_instance=true` opts into lease-aware recovery across Gateway instances and requires shared Postgres, `run_ownership.heartbeat_enabled=true`, and `run_events.backend=db`; otherwise startup rejects the configuration. Live scheduled runs
LangChainAGENTS.mdlangchain-ai/langgraph/AGENTS.md
libraries. Below is a high-level overview: - **checkpoint** – base interfaces for LangGraph checkpointers. - **checkpoint-postgres** – Postgres implementation of the checkpoint saver. - **checkpoint-sqlite** – SQLite implementation of the checkpoint saver
triggerdotdevAGENTS.mdtriggerdotdev/trigger.dev/AGENTS.md
root. See `.claude/rules/package-installation.md` for the full process. ```bash pnpm run docker # Core dev services (Postgres, Redis, Electric, MinIO, ClickHouse, s2-lite) # pnpm run docker:full # Same + observability stack (Prometheus, Grafana
NevaMind-AIAGENTS.mdNevaMind-AI/memU/AGENTS.md
service; do not add one. - Storage is pluggable across `inmemory`, `sqlite`, and `postgres`; repository contract changes require backend parity. - Scope data comes from `UserConfig.model`; validate `where` filters (`_normalize_where
cocoindex-ioAGENTS.mdcocoindex-io/cocoindex/AGENTS.md
Rust extension module (update when PyO3 APIs change) │ │ ├── connectors/ # External system connectors (localfs, postgres, qdrant, lancedb, google_drive) │ │ ├── connectorkits/ # Connector building utilities │ │ ├── resources/ # Abstractions: file.py (FileLike), chunk.py (Chunk), schema.py
OpenAIAGENTS.mdopenai/plugins/plugins/build-web-apps/skills/supabase-best-practices/AGENTS.md
Supabase Postgres Best Practices ## Structure ``` supabase-postgres-best-practices/ SKILL.md # Main skill file - read this first AGENTS.md # This navigation guide references/ # Detailed reference files ``` ## Usage 1. Read `SKILL.md
weave-osAGENTS.mdweave-os/router/AGENTS.md
repos, Service.VerifyAPIKey, | | | | | | APIKeyCache, id/hashing, Tink | | | | | | encryptor) | | | | | | internal/billing (balance checks + inference | | | | | | debits: Service + Repo iface; | | | | | | Postgres impl in | | | | | | internal/postgres) | | | | | | internal/feedback (pure HMAC signer for the | | | | | | no-login feedback-link token
iflytekAGENTS.mdiflytek/skillhub/AGENTS.md
management │ │ └── user/ # User-related auth services │ │ │ ├── skillhub-search/ # Search SPI + PostgreSQL full-text implementation │ │ ├── postgres/ # PostgresFullTextIndexService, QueryService │ │ └── service/ # Search SPI interfaces │ │ │ ├── skillhub-storage/ # Object storage SPI │ │ ├── local/ # LocalFileStorageService │ │ └── s3/ # S3StorageService
clideyAGENTS.mdclidey/whodb/AGENTS.md
need both env and log src/plugins/ # Database connectors (each has init() calling engine.RegisterPlugin) # Includes: postgres, mysql, sqlite3, mongodb, redis, elasticsearch, # clickhouse, duckdb, memcached (+ mariadb via mysql) graph/schema.graphqls # GraphQL schema graph
Agenta-AIAGENTS.mdAgenta-AI/agenta/api/AGENTS.md
business orchestration - DB layer: `api/oss/src/dbs/postgres/ /` - `dbes.py`: SQLAlchemy entities - `dbas.py`: shared mixins (when needed) - `dao.py`: Postgres implementation - `mappings.py`: DTO <-> DBE mapping Example to copy: - `api/oss/src/apis/fastapi/workflows/` - `api/oss/src/core/workflows/` - `api/oss/src/dbs/postgres/workflows/` ### Database schema migrations (which
SupabaseAGENTS.mdsupabase/supabase-js/packages/core/realtime-js/AGENTS.md
Listen to realtime updates from a Supabase PostgreSQL database. Handles channels, presence, broadcast, and Postgres CDC subscriptions. When helping a user work with this package: - **Usage and quick start**: [`README.md
yvgudeAGENTS.mdyvgude/lean-ctx/AGENTS.md
task")` with current status ## Provider Pipeline (Context Engine) External data sources (GitHub, GitLab, Jira, Postgres, MCP bridges, custom REST) are first-class citizens. All provider data flows through the same
AtmosphereAGENTS.mdAtmosphere/atmosphere/AGENTS.md
modules/` for the relevant family (e.g., CheckpointStore backends: `InMemory` + `Sqlite` ship in `modules/checkpoint/src/main/**`, and `Postgres` ships as the separate `modules/checkpoint-postgres` reactor module; Redis is pluggable
ObservalAGENTS.mdObserval/Observal/AGENTS.md
migrations** live in `observal-server/clickhouse/migrations/*.sql` and run through `services.clickhouse.migrations`. Keep Alembic for Postgres only. Never add ClickHouse DDL to startup code. The init container runs ClickHouse migrations after
crbnosAGENTS.mdcrbnos/carbon/AGENTS.md
Framework**: React Router v7 (NOT Remix), flat routes via `remix-flat-routes` - **Database**: Supabase (Postgres) with RLS, typed via `@carbon/database` + Kysely - **Background jobs**: Inngest (NOT Trigger.dev), via `@carbon/jobs` - **Apps
VercelAGENTS.mdvercel/chat/packages/state-memory/AGENTS.md
interface, update this file first — the test cases here become the spec the Redis / Postgres adapters must also satisfy. ## Coding conventions - Use named exports throughout. No default exports
VercelAGENTS.mdvercel/chat/packages/state-pg/AGENTS.md
state in PostgreSQL using the [`pg`](https://www.npmjs.com/package/pg) client. Pick this adapter when: - Postgres is already your primary datastore and you don't want to add Redis
SupabaseAGENTS.mdsupabase/etl/AGENTS.md
Repository Guidelines Postgres logical-replication engine. `etl` is the library, `etl-replicator` is the standalone binary, and `etl-destinations` holds built-in destinations. Product docs: https://supabase.github.io/etl/. Human walkthrough
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.
