What problem does it solve? Frontend and backend teams often diverge on URL naming, field names, response envelopes, and pagination conventions, causing integration bugs discovered only during joint debugging. This Skill establishes a single machine-checkable wl-api-contract.json contract and renders a per-page api.md so both sides code against the same verified interface definition. ## Core Features & Use Cases - Contract lifecycle commands: Preview, validate, compare, and render contracts via wl-skills contract init/validate/compare/render, with strict mode for frontend-backend handshake. - Standardized conventions: Enforces URL patterns (/service/resource/action), standard CRUD operations, business action naming (submit/approve/release), and the real response envelope { code, message, data } with success code 2000. - Dictionary contract integration: Embeds machine-parseable dict-contract blocks in api.md and syncs them into module-level dicts.ts for D1 validation. - Use Case: After scanning prototypes into a page inventory, generate api.md files for seven customer-management pages, send them to the backend for review, run strict contract compare, and only then generate data.ts API_CONFIG code. ## Quick Start Ask the AI to generate api.md interface contracts for all pages listed in your prototype scan report using the mmwr service prefix.