workstation-screen-composition

Compose Meridian WPF workstation screens into consistent operator workflows.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill workstation-screen-composition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workstation-screen-composition
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.codex/skills/workstation-screen-composition
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill workstation-screen-composition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents WPF workstation screens from becoming inconsistent, fragile, and hard to operate by standardizing how navigation, commands, status, grids/inspectors, and diagnostics are composed into a single operator experience.

Core Features & Use Cases

  • Operator-consistent screen contracts: Establishes a clear structure for primary workflow areas (grid/summary), detail tabs, diagnostics, and recovery states.
  • Shared primitives-first composition: Guides reuse of existing shell chrome and shared controls/styles/templates, only creating new primitives when repetition warrants it.
  • View-model owned behavior: Encourages shallow XAML and projection of state/workflow into the view model to improve maintainability and testability.
  • Evidence-backed implementation hygiene: Calls out required tests for routes/registration, loading/empty/error/selected states, and command availability/navigation handoffs.

Quick Start

Use the workstation-screen-composition skill to reshape an existing WPF workspace into Meridian’s workstation layout with shared navigation, command/status behavior, and a grid-plus-inspector flow.

Frequently Asked Questions about workstation-screen-composition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize WPF workstation screen layouts for consistent operator workflows?

Standardize WPF workstation screen layouts by composing shared navigation, command groups, status indicators, and grid-plus-inspector flows into a single consistent operator experience using shallow XAML and view-model owned state.

What is the best way to structure navigation and command groups in a WPF desktop workstation?

Structure WPF desktop workstation navigation and command groups by reusing shared shell chrome and primitives, projecting workflow state into the view model rather than embedding complex logic directly within the screen XAML.

How do I handle loading, empty, and error states in a WPF workstation screen?

Handle loading, empty, and error states in WPF workstation screens by defining explicit recovery behaviors within the view model, ensuring the screen contract standardizes these operator states alongside primary workflow areas.

Does WPF screen composition require specific tests for routes and command availability?

WPF screen composition requires specific tests for route registration, command availability, navigation handoffs, and loading or error states to ensure evidence-backed implementation hygiene across the operator workflow.

When should I create new shared primitives versus reusing existing ones in WPF workstation UI?

Create new shared primitives in WPF workstation UI only when repetition across screens justifies it, otherwise reuse existing shell chrome, controls, styles, and templates to maintain a consistent operator experience.

Can I reshape an existing WPF workspace into a standardized grid and inspector flow?

You can reshape an existing WPF workspace into a standardized grid and inspector flow by applying workstation screen composition patterns to standardize layout, navigation, and view-model owned behavior.