How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
relaticleCLAUDE.mdrelaticle/relaticle/CLAUDE.md
table alias, because `whereKey()` and `whereRelation()` qualify columns with the table name, which Postgres rejects under an alias. `tests/Arch/ConventionsTest.php` fails when a public method outside a model, enum, or `Scope
e2b-devCLAUDE.mde2b-dev/infra/CLAUDE.md
Spec: `spec/openapi-dashboard.yml`; team reads, template tags, builds, `/v1/management`, deprecated admin team bootstrap - Talks to Postgres and ClickHouse; never to orchestrators (see `docs/ARCHITECTURE.md`) - Port: 3010 **Orchestrator (`packages/orchestrator/`)** - Firecracker microVM orchestration - Entry
Open-Source-LegalCLAUDE.mdOpen-Source-Legal/OpenContracts/CLAUDE.md
InMemoryCache definition inside wrapper, not test file 9. **Backend Tests Waiting > 10 seconds on Postgres to be Ready**: Docker network issue. Fix with: `docker compose -f test.yml down && docker kill
JwuthriCLAUDE.mdJwuthri/Tracely-ai/CLAUDE.md
make install # uv sync --all-packages --all-extras + pnpm install make infra-up # clickhouse, postgres, redis, minio (docker) make migrate # ClickHouse DDL runner + Alembic (Postgres) make seed # default project + ingest
Team-CommonlyCLAUDE.mdTeam-Commonly/commonly/CLAUDE.md
# CLAUDE.md / AGENTS.md This file provides guidance to Claude Code, Codex, and compatible agent tooling
SupabaseCLAUDE.mdsupabase/postgres-meta/CLAUDE.md
guidance to Claude Code (claude.ai/code) when working with code in this repository. ## Overview postgres-meta is a RESTful API for managing PostgreSQL databases. It provides a normalized interface over
jonwigginsCLAUDE.mdjonwiggins/optio/CLAUDE.md
Health Mon │ │ ┌─ Persistent Agent Pod ┐ │ │ Sessions │ │ - Connection │ │ │ long-lived; turns │ │ │ │ │ Service │ │ │ wake on messages │ │ └─────────────┘ └──────┬───────┘ │ └────────────────────────┘ │ │ └──────────────────────────────┘ ┌──────┴───────┐ │ Postgres │ State, logs, workflows, persistent agents, │ │ inboxes, connections, secrets │ Redis │ Job queue, pub/sub └──────────────┘ All services
kossakovskyCLAUDE.mdkossakovsky/selfhost-ai/CLAUDE.md
access is routed through Caddy reverse proxy on ports 80/443. - **Shared secrets**: Core services (Postgres, Valkey (Redis-compatible, container named `redis` for backward compatibility), Caddy) are always included. Other services
StripeCLAUDE.mdstripe/pg-schema-diff/CLAUDE.md
Features**: - Computes diffs between schemas (DDL files, databases, or directories) - Generates SQL using native Postgres online operations (concurrent index builds, online constraint validation) - Provides hazard warnings for dangerous operations - Validates
LeslieLeungCLAUDE.mdLeslieLeung/glean/CLAUDE.md
PORT`: Web interface port (default: 80) - `ADMIN_PORT`: Admin dashboard port (default: 3001) - `POSTGRES_DB/USER/PASSWORD`: Database credentials - `SECRET_KEY`: JWT signing key - `CREATE_ADMIN`: Create admin account on startup (default
ThinkWatchProjectCLAUDE.mdThinkWatchProject/ThinkWatch/CLAUDE.md
crates/test-support/tests/`. They boot the full server in-process against a fresh per-test Postgres database and a dedicated Redis logical DB (1 by default). Each test fn carries `#[ignore
gotempshCLAUDE.mdgotempsh/temps/CLAUDE.md
Problem Details format) ### Mock Patterns **Sea-ORM MockDatabase:** ```rust let db = MockDatabase::new(DatabaseBackend::Postgres) .append_query_results(vec![ vec![backup::Model { id: 1, name: "test".into(), .. }], ]) .into_connection
ethanplusaiCLAUDE.mdethanplusai/jarvis/jarvis_home/CLAUDE.md
name, and not a run. - "Where's the auth logic?", "does it use Postgres?", "which file sends the email?" → `search_repo`, then `read_file` on a hit with `around
kgoedeckeCLAUDE.mdkgoedecke/doop/CLAUDE.md
First-time setup after clone ```bash bun install bun run dev # zero-config: embedded Postgres (pglite), server + web concurrently ``` Or self-host via Docker: `docker compose up` (real Postgres, port
sandbox-quantumCLAUDE.mdsandbox-quantum/switch/CLAUDE.md
governance platform. It onboards, orchestrates, and secures third-party AI agents using a Postgres-backed message store as the internal message bus. Agents register via the Agent Bridge
CannerCLAUDE.mdCanner/wren-engine/.claude/CLAUDE.md
Production server on port 8000 just test # Run pytest with marker (e.g., just test postgres) just lint # ruff format check + ruff check just format # ruff auto-fix + taplo ``` Available test
runvendoCLAUDE.mdrunvendo/vendo/CLAUDE.md
rule: every single-player capability keeps a no-key bring-your-own path (own Postgres, sandbox account, model key, OAuth apps). - Adapter rule: one adapter interface per block; Cloud
matiasbattocchiaCLAUDE.mdmatiasbattocchia/open-bsp-api/CLAUDE.md
overview Open BSP API — a multi-tenant WhatsApp Business Platform integration built with Deno, Postgres, and Supabase Edge Functions. See README.md for full details. ## Local checks must match CI (deno
bryanyzhuCLAUDE.mdbryanyzhu/agentic-ai-system-course/CLAUDE.md
reference for Ch.13, Ch.19, Ch.20. - **Paperclip** — workflow control plane (multi-agent orchestration, governance, durable Postgres state). Strong reference for Ch.08, Ch.12, Ch.15, Ch.19. External references to fetch from
oliver-kriskaCLAUDE.mdoliver-kriska/claude-elixir-phoenix/CLAUDE.md
# Plugin Development Guide Development documentation for the Elixir/Phoenix Claude Code plugin. ## Overview This plugin
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
