What problem does it solve? It prevents silent contract drift and broken request flows when implementing approved conversion, UX, and visual decisions on a production landing page that feeds a CRM endpoint. ## Core Features & Use Cases - Contract-Driven Implementation: Reads Conversion, UX, and Visual Director contracts before coding and flags conflicts instead of guessing. - CRM Request Integrity: Keeps frontend validation aligned with the live create-landing-request backend contract, including VIN or make/model/year vehicle identity, part identification, contact data, and photo upload rules. - Verification Discipline: Enforces build checks, real browser verification of critical request scenarios, mobile-first checks at ~390px, accessibility requirements, and a structured QA handoff. - Use Case: After a UX Architect specifies a new form error-recovery behavior, use this Skill to implement the smallest safe change in the Next.js/TypeScript/Tailwind codebase, verify both VIN and non-VIN submission paths in a browser, and hand off known risks to QA. ## Quick Start Implement the approved UX contract for the part request form, verify both vehicle identity paths in the browser at mobile width, and report contract status and remaining risks.