padronizacao-absoluta

To enforce consistent naming conventions for TypeScript files and imports, apply standardized rules like PascalCase for components and types, camelCase for hooks and services, and SCREAMING_SNAKE for constants during file creation and modification.

The best way to standardize project file structure is to validate inputs against a defined set of conventions for components, hooks, services, utils, and schemas, ensuring predictable organization and easier maintenance during onboarding.

When adding new modules, organize TypeScript directories by applying specific naming rules to each file type, such as PascalCase for UserCard.tsx components and camelCase for hooks, ensuring the project maintains its structural pattern effortlessly.

Yes, code organization rules for components and hooks integrate with ESLint to validate file structures and naming conventions, ensuring that file creation and modification adhere to predictable structural patterns across the codebase.

You need to apply naming conventions for schemas and constants whenever you create or modify code files, using camelCase for schemas and SCREAMING_SNAKE for constants to maintain predictable organization and prevent structural inconsistencies.