Featured
RepoLens
Helps engineers understand unfamiliar codebases: import a repo, get a structured map, chat over it, and plan implementations — never generate code.
Problem — Dropping into a strange monorepo means hours of grep before you can propose a safe change.
- Why shared packages/db, not api→worker imports — API and workers stay peers. Both depend on packages/db so the worker never becomes a sidecar of the HTTP layer.
- Why ARQ, not Celery — Backend is async-first. ARQ is asyncio-native; Celery’s async story is bolted on and heavier than this queue needs.
- Why Neon + Upstash from day one — Managed Postgres/pgvector and Redis kill local dual-config drift. Dev and prod speak the same wire protocol.