architecture-standards

To enforce architecture and naming conventions, load centralized repo-wide standards that standardize code organization, file naming, and layer separation. This ensures consistent structure and uniform boundaries across teams, reducing onboarding friction and maintainability issues.

The best way to standardize code organization is to apply structured architecture rules that define layer separation, module decomposition, and component boundaries. This guides team-wide practices to ensure scalable projects and maintainable repositories from day one.

You need repo-wide architecture standards when starting a new repository or integrating new features to align structure and naming from day one. They prevent structural drift and inconsistent code organization that leads to onboarding friction and maintainability problems.

Set up file naming and module decomposition guidelines by loading the architecture-standards skill and referring to its Core Rules when organizing components and files. This applies consistent conventions to renderer, API, and main layers.

Yes, you can use these repo guidelines to improve team collaboration by guiding team-wide practices for component boundaries, data flow, and subdirectory organization. This ensures scalable projects and uniform coding practices across teams.

Project structure drifts due to a lack of centralized repo-wide standards, leading to inconsistent code organization. Prevent this by enforcing architecture rules and naming conventions that standardize boundaries and decomposition across teams.