view-spec-writer

To write view specifications for read-only dashboards, define a unique View ID, Title, Actor, Data source, and Trigger. You must also include clear display rules, default sorting, pagination, and empty-state behavior to capture the precise UI presentation.

A view spec is a declarative blueprint that captures read-only UI behavior for data presentation screens like lists and feeds. It specifies essential fields such as View ID, Actor, and Data source without forcing a complete use-case structure.

To handle conditional display rules for role-based views, define data-dependent changes, loading states, and error states within the view specification. This ensures the read-heavy UI adapts correctly based on the specific actor and data availability.

Yes, view spec writing integrates with screen-inventory to map views to screens and variants. This integration provides a precise, implementation-agnostic blueprint for UI presentation while maintaining a comprehensive screen inventory.

Use view specifications when designing read-heavy features where the main outcome is data presentation rather than state changes. They provide a precise blueprint for dashboards and reports without forcing a complete use-case structure.

A UI specification should include performance constraints alongside display rules and default sorting. These constraints ensure read-heavy screens like dashboards and feeds maintain optimal data presentation performance under various loading and error states.