coding-conventions

TypeScript and React coding standards are enforced by defining strict file-type conventions, naming rules, and ESLint expectations. This prevents style drift and reduces code review friction by standardizing component and hook authoring.

The best way to structure React hooks and components is to maintain a one-component, one-hook per file rule using `.ts` and `.tsx` extensions. Components use PascalCase, hooks use the `useX` naming pattern, and pages use the `*Page.tsx` suffix.

Tailwind CSS class conflicts are managed using `tailwind-merge` for class conflict resolution. The conventions require Tailwind-only styling to ensure consistent design implementation across components without conflicting utility classes.

No, you cannot safely disable ESLint rules to bypass coding conventions. The standards discourage lint bypassing, prohibit unsafe disable directives, and enforce strict comment and TODO policies to maintain code quality and reviewability.

Grouping imports using the `@/` alias enforces import discipline and predictability across the TypeScript codebase. This practice standardizes module resolution, reduces style inconsistency, and aligns with the expected ESLint configuration.

Placeholder comments and unreferenced TODOs are strictly prohibited by the coding conventions. This limitation ensures that all code annotations are actionable and tracked, preventing abandoned code notes from increasing review friction and causing style drift.