This app is part of the Deepgram DX stack. When working in this repo, you must follow cross-stack documentation rules. A PostToolUse hook will remind you when you edit cross-stack files, but you are also responsible for catching changes the hook doesn't cover.
-
Incremental changes, comprehensive reviews. Make changes incrementally. But before finishing any task, do a comprehensive review to spot architectural misses — port conflicts, auth flow breakage, env var mismatches, or contract changes that affect other services.
-
Update dx-stack docs when you change cross-stack behavior. If your change affects ports, auth flows, env vars, redirect URIs, API contracts, or deployment config, update the reference docs at
/Users/lukeoliff/Projects/deepgram/dx-stack/before finishing. -
Know the architecture. Read
/Users/lukeoliff/Projects/deepgram/dx-stack/CLAUDE.mdfor the full stack context — port map, auth flows, service-to-service communication, and environment matrix.
| Change | Update |
|---|---|
| Port changes | dx-stack/CLAUDE.md port map + docs/runbook.md |
| Auth flow / session changes | dx-stack/docs/auth.md |
| OIDC client changes | dx-stack/docs/auth.md client table |
| Env var changes | dx-stack/docs/environments.md |
| New cross-service endpoints | dx-stack/CLAUDE.md cross-service section |
| Deployment / Fly config changes | dx-stack/CLAUDE.md deployment section |
| Database schema changes | dx-stack/docs/auth.md schema section |
| Redirect URI changes | dx-stack/docs/auth.md + seed.ts |
Code examples demonstrating Deepgram API usage across languages.