repo-structure-conventions

You can audit repository structure during onboarding by running an initial audit to identify gaps between the current layout and universal conventions, covering root-level files, directory naming, and build-artifact isolation before proposing remediation.

The best way to enforce scalable file organization is to audit repositories against universal conventions, ensuring consistent root-level layouts, app-type-specific directory structures, and proper build-artifact isolation across all managed projects.

Scaffolding generates a compliant root-level layout and directory structure for new repositories, while remediating proposes explicit file moves and renames to align existing projects with conventions without silently breaking imports or CI.

Yes, you can safely restructure directory naming conventions by using remediate mode, which proposes explicit file moves and renames for review rather than executing silent changes, ensuring imports and CI pipelines remain intact.

Yes, repo structure governance handles build artifact isolation by enforcing .gitignore patterns and defines CODEOWNERS patterns for clear ownership mappings, while delegating specialized governance tasks like secret hygiene to other skills.

You should apply app-type-specific directory structures after app-type classification, during repository creation or restructuring, ensuring the root layout and directory naming conform to industry-standard conventions for scalable navigation.