coding-conventions

To enforce snake_case naming conventions, standardize field names across your data models, API payloads, and database schemas. This skill provides mapping guidelines and normalization rules to rename camelCase occurrences and align names from ingestion to persistence.

Inconsistent field naming between TypeScript and PostgreSQL causes type errors because camelCase in frontend payloads mismatches snake_case in database schemas. Aligning names across data models prevents data mapping issues, DB constraint violations, and runtime failures.

The best way to standardize API payload field names is applying a single snake_case convention across scraper, backend, and frontend components. Mapping guidelines and shared type references ensure consistent field names from data ingestion through persistence.

Yes, this naming convention skill applies to database schemas and frontend code paths. Scope covers data models, API payloads, and code paths across Python, TypeScript, and PostgreSQL where naming inconsistencies cause type errors or runtime failures.

To normalize camelCase fields to snake_case in a multi-language codebase, configure your project to consistently rename occurrences and verify mappings. This skill provides normalization rules and references for shared types across Python, TypeScript, and SQL schemas.

You need snake_case normalization rules when field names from web scraper ingestion mismatch backend or database schemas. Applying consistent naming prevents type errors and data mapping issues across Python, TypeScript, and PostgreSQL components.