What problem does it solve? It keeps every API contract in a React/TypeScript app consistent by making Effect Schema the single source of truth for decoded types, wire types, fixture generators, and MSW encoders, eliminating hand-written parallel interfaces and drift between frontend and backend shapes. ## Core Features & Use Cases - Field naming bridge: Converts backend snake_case keys to camelCase app fields via Schema.fromKey, and derives mutation bodies from Encoded wire types. - Shared schema utilities: Provides UnwrappedDataResponseSchema, open/transformed enum helpers, pagination envelopes, calendar date schemas, and a non-recursive BigDecimal stand-in that avoids TS2589 inference blowups. - Recursive and union schemas: Documents the Schema.suspend plus paired-interface pattern for tree structures and per-file union arms for polymorphic payloads. - Use Case: When adding a new invoices endpoint, define one schema under features/invoices/, reuse PaginatedResponseSchema for list responses, and let hooks, fixtures, and MSW mocks all derive from that single definition. ## Quick Start Ask the assistant to create an Effect Schema for a new API response following the schemas conventions, providing the backend contract so field names and nullability are not guessed.