patch-route-field-silently-dropped

What problem does it solve?

This Skill fixes the common fullstack bug where fields submitted via PATCH or POST routes appear to save successfully but disappear after a page refresh, or cause unexpected HTTP 502 errors due to mismatched field names between frontend TypeScript types, backend validation schemas, and Prisma ORM relation names.

Core Features & Use Cases

• Diagnoses silent field drops caused by validation schemas that strip unrecognized fields before they reach the Prisma handler.
• Resolves 502 errors and missing nested relation data from mismatched field names between frontend types and Prisma relation keys (e.g. manDays vs manDayLines).
• Corrects response-side field drift where Prisma returns relation data under the correct wire key, but the frontend type uses a different name leading to silent empty values or crashes.
• Common use case: Fix a CRM service form where man-day line items disappear after save, or a Kanban board edit dialog that always defaults to the first stage regardless of the card's actual stage.

Quick Start

Use this skill to diagnose and fix a PATCH route where submitted form fields disappear after page refresh, or resolve 502 errors caused by mismatched Prisma relation field names between your frontend and backend.