design-review

To validate SwiftUI implementation against design specifications, you audit your source files by comparing them directly with screen design documents, checking color, typography, spacing, components, and accessibility to identify conformance gaps and output a diff report.

Checking SwiftUI accessibility conformance involves scanning your source files against defined design criteria to verify that implemented UI components and screen layouts match the accessibility rules specified in your design documentation.

Yes, you can review all SwiftUI screens at once. The validation process applies to both per-screen reviews and entire codebase audits, cross-referencing your SwiftUI source files against design docs to ensure comprehensive UI conformance across the project.

Yes, design documents are required. The review process requires access to docs/design and your SwiftUI source files to verify color, typography, spacing, and component conformance, applying defined criteria from the frontmatter and processing flow to identify gaps.

A SwiftUI design review report includes identified differences between your design documents and current implementations, detailing specific conformance gaps in color, typography, spacing, components, and accessibility, along with actionable improvement suggestions.