Strict-TypeScript product monorepo — independent R&D

Challenge

Shipping several related product surfaces — consumer apps plus an AI-agents layer — usually implies a platform team: shared design system, typed backend, CI/CD, and enough people to stop repos from drifting. I ran it as independent product R&D: one architect–engineer loop that still had to clear production quality bars.

The problem: share identity and infrastructure across apps without copy-paste, while moving fast enough to validate the ecosystem in the market — not only on paper.

Constraints

• Solo builder throughput — Architecture had to multiply output, not just organize it.
• Shared identity without drift — UI and API patterns reused across apps with typed contracts.
• Real backend — Live data, auth boundaries, and deployable services — not a static marketing shell.
• Disclosure-safe public narrative — Anything published passes the same scan gates as this site.

Approach

I built a strict-TypeScript monorepo (Turborepo) with shared packages, a typed Convex backend, and Next.js surfaces — orchestrated by the same multi-agent pipeline in the Agentic OS study.

Monorepo and platform decisions

• Turborepo workspace — Shared lint, typecheck, and test tasks with cache-friendly pipelines across apps.
• Design tokens + components — One visual language across product and marketing surfaces.
• Convex for typed backend — Real-time data and server functions with end-to-end TypeScript contracts.
• Auth and environment boundaries — Clerk patterns reused without leaking secrets into client bundles.
• Agent-orchestrated SDLC — Plan → implement → audit → test → ship with host-resource caps; auditor agents block unsafe diffs before merge.

Public proof of the same system includes the interactive agent demo on this portfolio and the CI gates documented in the colophon. Throughput method lives on the about page.

Outcomes

Multiple production-oriented surfaces on a shared foundation — platform work that would normally need a small team, executed with agent-assisted delivery and hard automated gates.

Measurable impact

| Area | Result | | --- | --- | | Structure | Multi-app monorepo with shared UI and typed backend | | Quality | Zero-any TypeScript and CI gates on every change | | Orchestration | 50+ agent roles in daily engineering use | | Public proof | Interactive demo + CI-gated portfolio ship under the same system |

User counts, revenue, and internal product codenames are not disclosed.

What this demonstrates

• Platform thinking solo — Monorepo, shared primitives, and deploy pipelines without a large org chart.
• Agents with verification — Force multiplier only when audit and test gates stay in the loop.
• Inspectable craft — Gates and CI are public; the colophon lists what blocks every publish.

Read the orchestration depth in Agentic OS or long-horizon enterprise ownership in the Coca-Cola / Judo study.