Ui

When the UI is waiting on an async task:

Render Android apps edge-to-edge and consume WindowInsets so content is never hidden behind the status bar, navigation bar, or IME.

Use type-safe Navigation Compose with serializable routes, single-activity architecture, and hoisted nav state.

Migrate off deprecated back handling to OnBackPressedDispatcher and support the predictive back gesture with progress-driven animations.

Motion should be purposeful — guide attention, show spatial relationships, and provide

Adopt the system Apple design language and materials over custom chrome, and version-gate brand-new design APIs like Liquid Glass.

Use color with intention — never as the sole means of conveying information.

Target LCP <= 2.5s, INP <= 200ms, CLS <= 0.1 at field p75, and enforce a performance budget in CI.

Share one semantic token source across platforms, then render values in each platform's native units, type scale, and idioms.

The dashboard service is a generic API and UI layer. It has no knowledge of git, files, or roadmap structure. Agents ...

Choose the right pattern for the content type and user task.

Generate per-platform token artifacts from one source via a build step; never hand-edit the generated outputs.

- Use `d:DataContext` and `d:DesignInstance` for XAML designer preview data

Every user action should have visible feedback. The weight of the feedback should match

Use built-in WinUI 3 controls — they implement Fluent 2 natively. Never custom-draw what a standard control can do.

Forms are where users do real work. Reduce friction at every step.

XAML layout uses effective pixels (epx) — scaling is automatic for all XAML-rendered content.

Icons supplement text — they do not replace it (except for universally understood symbols

Minimize Compose recomposition with stable types, deferred state reads, lazy-list keys, and release-build measurement.

Run side effects through the correct keyed Compose effect API, never directly inside composition.

Hoist UI state to its lowest common owner or the ViewModel, keep composables stateless, and enforce state-down/events-up unidirectional flow.

Design for the content, not a fixed screen size. Layouts should adapt gracefully from

Theme Compose UIs with Material 3 color roles, ColorScheme, type and shape scales, and full dark support.

Adopt modern interoperable CSS features (container queries, @layer, :has(), subgrid, nesting, view transitions) gated on Baseline status with fallbacks.

Defer to these canonical sources before applying the defaults in this file:

All UI components MUST include preview declarations for rapid visual verification during development. Previews should...

Ship a Web App Manifest plus a service worker with an explicit caching strategy, and account for iOS install/push/storage limits.

Use a consistent spatial scale based on a **4px base unit** (8px primary grid). All spacing,

Every view that loads data or can be empty must handle all four states explicitly. Never

WinUI 3 supports tri-state theming: Light, Dark, and High Contrast.

Implement themes as alternate value sets for the same semantic tokens; swap the active set, never the component code.

Interactive elements MUST be large enough to tap or click accurately. Defer to the platform

Use the platform's system font. Establish a type scale with clear roles — don't invent

Establish clear importance through size, weight, color, and spacing. Every screen should

Apply Mica as the backdrop of long-lived windows and Acrylic for transient surfaces, honoring user theme and system settings.