bobi-stack
Bobi Labs · internal infrastructure
Role
PM-builder · internal infrastructure
Duration
Built 2026 · in continuous use
Status
Live · internal · runs under every engagement
The problem
AI-assisted delivery is fast until it is not. Context resets between chats, a convention that lived in someone's head lapses silently, and the second month of an engagement quietly stops resembling the first. The speed is real but it leaks at the seams nobody is watching.
Every new engagement also pays the same setup tax: auth, a typed data layer, RLS, deploy, the same five decisions made slightly differently each time. That tax is paid in the most expensive week, the first one.
The approach
One scaffold, started from on every build. Next.js, Supabase, a typed query and mutation registry, and RLS already wired, so day one is feature work, not plumbing.
The discipline ships with the code, not with the founder's memory. A session-start and session-end checklist, a memory-file system (feedback / project / user / reference), and parsed call-note conventions keep context from leaking between chats and across weeks.
CLI-first ops and atomic conventional commits, so CI and local never disagree and the git log reads as an audit trail a client can follow.
What shipped
- ▪Pre-wired Next.js + Supabase + TanStack Query stack with a typed data layer: schema types reach the component with nothing hand-written.
- ▪Query and mutation registries with paired hooks and a config test that fails loudly on registry drift.
- ▪Session lifecycle and memory-template system that survives chat resets across a multi-week engagement.
- ▪Public presence at bobistack.bobilabs.dev. The repository itself is private.
Stack & decisions
Next.js + TypeScript
App Router. The scaffold every engagement forks internally.
Supabase + RLS
Postgres + RLS as the authorization layer from the first table. Types generated end to end.
TanStack Query
Registry-paired query and mutation hooks. Auto-invalidation on write, no manual cache wrangling.
Claude Code
Session-start and session-end checklists, memory-file conventions, and a setup skill that fills project docs from the real codebase.
Outcome
- →In continuous internal use. Every Bobi Labs build starts from it, which is a measurable chunk of the team's first-week speed.
- →Conventions survive context resets. The second month of an engagement looks like the first because the discipline is enforced by the scaffold, not by memory.
What you won't see in screenshots
bobi-stack is proprietary Bobi Labs infrastructure and the repository is private. The public page at bobistack.bobilabs.dev describes it without exposing the code. It may be opened up later once it has proven out further.
Have something we should ship?
60-minute scoping call, then a clear plan for how we'd approach it.