project-conventions

To structure code in an Nx monorepo consistently, organize projects into packages/ and apps/ directories while applying domain architecture for auth, crud, and trans layers to ensure scalable boundaries and shared library alignment.

When modifying Angular and NestJS components, adhere to coding standards by applying component prefixes, enforcing project tags, and maintaining strict ESLint import ordering to ensure consistent code modification across the monorepo.

Domain architecture separates auth, crud, and trans layers by defining strict boundaries within the Nx workspace, isolating business logic into shared libraries to ensure domain-specific code remains modular and maintainable across packages.

Yes, you can use ESLint and project tags to enforce boundaries in an Nx workspace by validating import ordering and restricting cross-domain access, ensuring shared libraries and domain layers maintain structural integrity during code generation.

Maintaining a monorepo with shared libraries requires following specific Git strategies and testing practices to ensure repository maintenance, validate domain architecture changes, and prevent regressions across Angular and NestJS packages.