validate-design

To validate design consistency, you can automatically compare markdown design docs in the docs/ directory against the actual codebase in backend/ and frontend/ directories to identify structural mismatches. This process surfaces inconsistencies between the documented architecture and the implementation.

Detecting API endpoint mismatches is done by parsing markdown design documents to extract verification items and comparing them against the implemented backend and frontend code. This comparison targets API endpoints, data schemas, and error handling to find discrepancies.

Yes, validating design consistency requires access to specific markdown files: docs/backend-design.md and docs/frontend-design.md. The tool parses the markdown structure of these files to extract sections, tables, and verification items for comparison against the codebase.

You generate a remediation-focused report by running a validation command that compares your design documentation with your app implementation. The resulting report guides engineers on exactly what design or code areas need to be fixed to resolve the detected mismatches.

Yes, design validation compares environment variables and data schemas by reading structured design documents and traversing the backend and frontend code. It checks these specific technical artifacts against the documented expectations to ensure full stack alignment.