view-specifications

To standardize SwiftUI view specifications, use a template-driven structure in SKILL.md that defines sections for headers, wireframes, layouts, content, data models, interactions, implementation references, and accessibility. This ensures consistent guidance from design to code.

A cross-platform UI design view specification should include sections for wireframes, layout, content, data contracts or models, interaction patterns, implementation references, and accessibility to maintain alignment between design intent and engineering work.

You create a spec for a modal list view by describing your view and wireframes to generate a complete spec draft. The template standardizes headers, layouts, and child views to clarify inputs and interactions.

Yes, the view-specification template includes Implementation Reference scaffolding specifically designed to document file locations and key code patterns, ensuring teams have consistent engineering guidance.

You can use this template-driven approach for both SwiftUI and cross-platform views. It applies to designing views across different platforms by guiding headers, layouts, child views, and data contracts consistently.

The best way to align wireframes with engineering work is to enforce a standardized view specification that clarifies inputs, layouts, and interactions, bridging the gap between design intent and implementation.