project-conventions

A domain-first directory layout organizes repository code by feature or domain rather than technical role. This project structure scales with growth by grouping related functionality, reducing cognitive load and onboarding friction for new contributors entering the codebase.

Standardize repository conventions for a new monorepo by applying a cohesive baseline covering branch strategy, directory layout, dependency pinning, and path portability. This reduces onboarding friction by enforcing consistent rules across apps and libraries within the repository.

Yes, project conventions guidance applies to apps, libraries, and monorepos. It provides a cohesive structural baseline that enforces domain-first layouts, exact dependency pins with lockfiles, and GitHub Flow branching to ensure consistency across different project scales and contexts.

Enforce exact dependency pinning by requiring exact versions with lockfiles and checking for hardcoded paths. This ensures path portability across environments, preventing environment-specific failures and guaranteeing reproducible builds for the repository.

GitHub Flow is the default branch strategy because it uses short-lived branches and PR-based merges to keep the repository history clean. This workflow reduces merge conflicts and integrates changes rapidly, lowering cognitive load for developers collaborating on the project.

Audit your repository for path portability issues and layout smells by running a sweep-ready scan that detects hardcoded paths and structural inconsistencies. This ensures the repository adheres to domain-first layouts and portable path handling conventions.