meridian-design-system

Standardize operator workstation UI design tokens by enforcing a unified design system for color, typography, radii, borders, shadows, and surface hierarchy. This ensures dense evidence tables match the Meridian cockpit aesthetic across Trading, Portfolio, and Accounting screens.

Design operator workbench layouts by enforcing an operator-first structure: a masthead, left rail, and toolbar strip. Use evidence-first composition and split reference workbenches to standardize financial trading screens across Strategy, Data, and Settings modules.

Define state semantics for operator UI dashboards by applying visual rules for Healthy, Observe, and Critical states. Pair these with operator-safe microcopy and casing conventions governed by content fundamentals to ensure clear, consistent dashboard communication.

Yes, you can mock screens across Reporting and Portfolio modules. The system standardizes visual geometry and state behavior for all Meridian workstation areas, satisfying required workflows using colors_and_type.css and visual foundations references.

Your Meridian UI screen looks inconsistent because it lacks a single operator-focused design reference. Without enforced layout patterns, state semantics, and tone rules, UI decisions drift across Trading, Accounting, and Reporting workbenches.

Yes, you need colors_and_type.css to maintain visual geometry in operator UI design. It provides the token-accurate styling for surface primitives, borders, and shadows required to achieve consistent state behavior across Meridian workstation screens.