File Organization

Organize a multi-layered codebase by establishing a canonical repository layout that separates shared, frontend, backend, and utilities directories. This guideline enforces directory conventions and provides example structures to ensure consistent file placement across all layers.

Standardize project structure for onboarding by applying a canonical directory layout across core areas like app, lib, components, and public. This consistent placement guidance speeds up developer productivity and helps new contributors navigate the codebase faster.

Structure a repository during an architectural refactor by aligning existing files with a canonical directory convention. This guideline provides a sample tree structure and placement rules to enforce architecture alignment and maintain consistency across shared code, frontend, and backend layers.

Yes, this directory convention specifically applies to projects spanning frontend, backend, and shared layers. It enforces alignment with architecture rules and provides example structures to ensure consistent file placement across all core areas including shared, app, lib, and components.

You need a canonical repository layout during onboarding, refactoring, or architectural reviews to maintain consistency. This guideline establishes a directory convention across shared code, frontend, backend, and utilities, making it easier to onboard new contributors and enforce architectural alignment.

To clarify your project structure, include canonical directories for core areas such as shared, app, lib, components, public, and documentation. This guideline enforces a directory convention and provides placement guidance to ensure your repository layout remains consistent and maintainable.