- Home
- Skills
- Agents & Orchestration
- Form Validation Contract Repair
More screenshots
Works with the AI Agents you already use
Form Validation Contract Repair
Repair form-validation drift in a repository using Cursor.
$1
Form Validation Contract Repair
Example session with this skill installed
My signup form allows 2-character names but the backend requires 3. The age field arrives as a string but the API wants a number. Repair the contract and add tests.
- Read your context and instructions
- Compiled the form validation contract
Repair decision: FORM VALIDATION CONTRACT DRIFT FOUND.
Identified drift in display-name length and age type coercion.
Plan: Centralize shared Zod schema for length limits, add explicit string-to-number parser in Server Action, and update mocks.
Patch ready for local review.
Connects securely to your tools. The creator never sees your data.
About this skill
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.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Does not access production data, live APIs, or secrets. Cannot perform database migrations or decide business rules without human input. Requires existing repository files and local test tools.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.