liftera-architecture

To enforce monorepo architecture rules, keep application code inside apps/* and reusable code inside packages/*. This prevents ad-hoc imports and tangled dependencies by ensuring code lives in correct locations with clear ownership.

Importing app code from another app breaks monorepo architecture because it creates tangled dependencies. You should never import across apps; instead, extract shared logic into a package to maintain proper cross-app collaboration boundaries.

The best way to organize reusable code in a monorepo is to centralize it inside packages/*. You should never duplicate UI or utilities across apps; instead, design platform-agnostic packages with stable entrypoints to ensure dependency discipline.

You need to extract shared logic into a package when multiple apps require the same functionality. This enforces dependency discipline at the package level and ensures reusable code remains platform-agnostic with stable entrypoints, minimizing root-level changes.

No, you should never duplicate UI or utilities across apps in a monorepo. Instead, centralize shared UI inside packages/ui to maintain dependency discipline and ensure code lives in the correct locations with clear ownership.

Yes, this monorepo architecture guidance applies to repository changes, new packages, and new apps. It ensures code lives in the correct locations and dependencies stay well-scoped when planning any structural addition to the monorepo.