Frontend TypeScript Types Skill

To define frontend TypeScript types aligned with backend schemas, model data structures following conventions in frontend/types/index.ts, mapping backend snake_case names to frontend camelCase fields for usability. This ensures type safety and predictable data contracts across your codebase.

Mapping snake_case API response fields to camelCase in TypeScript involves creating separate type definitions for API responses and frontend data. This preserves frontend ergonomics while keeping the data contract predictable and maintainable.

You should use separate TypeScript types for API responses, forms, and query parameters when modeling frontend data shapes from backend contracts. This separation ensures consistent naming conventions and type safety across different data flows in your application.

Choosing between interfaces or types when defining frontend TypeScript data shapes depends on the patterns documented in frontend/types/index.ts. Following these established conventions ensures consistency, maintainability, and alignment with existing codebase patterns.

To ensure TypeScript frontend types stay consistent with backend schemas, define types that mirror backend data while preserving frontend ergonomics. Follow naming conventions and interface patterns in frontend/types/index.ts to maintain alignment and type safety.