file-organization

To organize exports and imports in a TypeScript monorepo, enforce a one export per file rule and use alias-driven imports like @/ or @@ to ensure uniform paths and reduce cognitive load.

The best way to structure Vue components and models in a monorepo is co-locating types under a models/ directory, keeping schemas close to usage, and applying structured component guidelines.

Enforcing one export per file helps code organization by avoiding bulk exports and clarifying file responsibility, which enforces a strict export-first architecture across packages and reduces onboarding time.

To separate constants and MIME types when reorganizing files, centralize constant maps and MIME-type mappings rather than using ad-hoc lookups to maintain clear separation of concerns.

Yes, you can use alias imports to simplify navigation across monorepo packages by adopting project-wide aliases like #shared, @@, and @/ to enforce consistent import paths throughout the codebase.

Yes, this coding standard applies when creating, moving, or reorganizing files, exports, constants, or new packages in a monorepo to ensure consistent structure and naming throughout the repository.