repo-standards

Standardizing folder structure involves enforcing consistent naming, typing, and layouts like features/<feature-name>/ containing components, actions, server, schemas, types, and utils. This makes repositories predictable and onboarding easier by reducing bike-shedding over conventions.

To scaffold a new feature, apply a recommended pattern creating a features/<feature-name>/ directory containing components, actions, server, schemas, types, and utils sub-folders. This structure speeds up feature development by centralizing imports and folder responsibilities.

A review checklist improves PR hygiene by flagging inconsistencies, hidden conventions, and premature abstractions during code reviews. It guides necessary refactors to ensure typing discipline and naming conventions are maintained across the project repository.

You need repository standards when your codebase becomes unpredictable and onboarding slows down. Enforcing folder structure, typing discipline, and PR hygiene during feature scaffolding and code reviews ensures consistent patterns and reduces debate over conventions.

Yes, you can apply these scaffolding conventions during refactoring. The review checklist flags hidden conventions and premature abstractions in existing code, guiding refactors to align with the standardized folder layout, typing, and naming discipline.

When applying repository structure conventions, avoid premature abstractions and introducing hidden conventions. Use the provided review checklist during code reviews to flag these issues and guide refactors rather than creating unstructured or non-standard folder layouts.