Project Structure (Monorepo)

The repo is a Turborepo monorepo split into two workspaces: packages/ holds the shared, versionless building blocks, and apps/ holds the deployable apps. Everything in packages/ is one of three families — core-*, platform-*, or feature-* — and each apps/ entry is a deployable target (mobile, web, backend, e2e). Each family has a fixed job and a fixed place in the dependency graph. Get the family and the direction right and the graph stays acyclic, features stay swappable, and a change to one feature can never ripple sideways into another.

Two rules hold the whole thing together: dependencies only ever point downward (apps/* → feature-* → platform-* → core-*), and every package is a black box reached only through its published entry point. The rest of this file is those two rules plus the naming and internal-structure conventions that keep them enforceable.