codebase-conventions

Naming conventions standardize identifiers across your project. Apply kebab-case to file names, uppercase SQL keywords, use explicit return types in TypeScript, and organize files by function—placing frontend components under src/components/ui. This reduces cognitive load and prevents naming surprises across teams.

File organization establishes predictable structure across src/, supabase/, openspec/, and docs/ directories. Define naming conventions, enforce file size limits (200-line maximum), and specify where components, migrations, and specs belong. Consistent structure helps developers locate code quickly and maintain quality.

SQL style guidelines enforce uppercase keywords and consistent formatting; TypeScript constraints require explicit return types and strict typing. Document these rules in your conventions reference, apply them during code review, and use linting tools to catch violations automatically across contributions.

Project limits set boundaries for consistency: enforce 200-character description lengths, define answer enum structures, and establish the 200-line file size cap. These constraints prevent outliers, simplify maintenance, and ensure predictable patterns across the repository.

Conventional commits standardize commit messages with type prefixes (feat, fix, docs, etc.), making project history searchable and automated changelog generation possible. Clear commit practices reduce ambiguity during code review and help team members understand change intent quickly.