Platform Patterns
Transferable architectural patterns for building platforms.
These are architectural patterns distilled from real platform builds. Each pattern represents hard-won decisions about how to structure codebases, split data responsibilities, enforce security, and maintain auditability.
Start Here
New Project Checklist
Bootstrap sequence from zero to running CI
Bootstrap Commands
Copy-paste CLI sequences for every scaffolding phase
Stack Decisions
Record technology choices before writing code
Architecture Patterns
Project-agnostic patterns that apply regardless of repository structure, framework choice, or team size.
Data Architecture
Split transactional data from editorial content by purpose
Auth & Row-Level Security
JWT custom claims with database-level RLS policies
Audit-First Architecture
Append-only event tables for full history and compliance
Documentation Hub
Multi-collection knowledge base with llms.txt generation
Monorepo Patterns
Transferable across monorepo projects. Assumes pnpm workspaces + Turborepo.
Monorepo Architecture
Shared-code platform builds with consistent tooling
Three-Application Model
Admin, public site, and wiki from a shared codebase
Scaffolding-First Approach
Infrastructure and services before any feature code
Bootstrapping
Actionable guides for getting a project off the ground.
Stack Decisions
ADR templates and technology trade-off tables
Dependency Catalogue
Curated package selections by category
Bootstrap Commands
Executable CLI sequences from empty directory to CI
How to Use These Patterns
Each pattern page covers:
- When to use it — the problem it solves and the context where it applies.
- How it works — the concrete structure, conventions, and implementation details.
- Why it matters — the benefits and trade-offs of adopting the pattern.
Architecture patterns compose well together. A typical platform build uses several: split data architecture, RLS-based authorization, and append-only audit trails. If building a monorepo, layer the monorepo patterns on top.