meridian-browser-workstation

Route TypeScript/React browser tasks to src/Meridian.Ui/dashboard with build/test validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meridian browser workstation workflows require consistent UI behavior, shared contract alignment, and reliable validation so that changes don’t break operator-facing flows.

Core Features & Use Cases

  • Browser-lane routing and scope confirmation: Ensures tasks target src/Meridian.Ui/dashboard/ and don’t accidentally drift into other product surfaces.
  • UI guardrails and contract alignment: Keeps browser navigation and interaction behavior aligned with shared UI contracts, enforcing top-level and non-mobile constraints.
  • Deterministic validation: Runs browser workstation build/test commands and reports exact outcomes and residual risks for safe delivery.

Quick Start

Use meridian-browser-workstation to implement and validate a change to the Trading page behavior in src/Meridian.Ui/dashboard while following Meridian UI guardrails.

Frequently Asked Questions about meridian-browser-workstation

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

FAQPage Schema
How do I prevent mis-scoped UI changes in a React dashboard?

To prevent mis-scoped UI changes in a React dashboard, route tasks through browser-lane scope confirmation. This ensures work targets src/Meridian.Ui/dashboard without drifting into other product surfaces.

What is the best way to align TypeScript UI changes with shared contracts?

Aligning TypeScript UI changes with shared contracts requires applying UI guardrails during implementation. This enforces top-level and non-mobile constraints, keeping browser navigation aligned with shared UI contracts.

How do I validate browser workstation builds and report residual risks?

Validate browser workstation builds by running deterministic build and test commands. This reports exact validation outcomes and identifies residual risks for safe delivery of TypeScript and React changes.

Can I use this workflow for changes outside of the src/Meridian.Ui/dashboard directory?

No, this workflow targets src/Meridian.Ui/dashboard and overlapping seams in src/Meridian.Ui.Services and src/Meridian.Ui.Shared. It enforces lane ownership checks to prevent changes outside these boundaries.

Why does my Meridian web UI change fail lane ownership checks?

Meridian web UI changes fail lane ownership checks when tasks drift outside src/Meridian.Ui/dashboard. Routing tasks through browser-lane confirmation enforces scope boundaries and prevents contract drift.