Form Validation Contract Repair

The problem

Validation logic often drifts across the stack. You end up with frontend schemas that allow data the server rejects, inconsistent type coercion for numbers or booleans, and database constraints that surface as generic, unhelpful errors.

What it does

• Traces the complete input lifecycle from browser constraints to database persistence.
• Identifies mismatches in field names, types, length limits, and conditional requirements across layers.
• Aligns client-side schemas with authoritative server-side domain rules.
• Maps database constraints and persistence failures to stable, localized public error codes.
• Generates bounded repository patches and deterministic local tests for verification.

Frameworks & tools

Works with any stack including React, Vue, Next.js, Django, Rails, Laravel, TypeScript (Zod/Yup), Python (Pydantic/DRF), Prisma, and OpenAPI specs.

Why this beats prompting it yourself

Manually tracking a single field through components, schemas, transport adapters, and database models is error-prone and tedious. This skill automates the trace across your entire repository to ensure the contract is airtight without weakening security boundaries.

Use cases

• Fixing "Submit" button failures where the UI thinks data is valid but the API disagrees.
• Standardizing how empty strings, nulls, and booleans are coerced during transport.
• Repairing stale validation messages and missing translation keys.
• Aligning OpenAPI documentation with actual runtime validation behavior.

Known limitations

Cannot access production databases or live APIs. It does not perform data migrations or decide business thresholds without human approval.