mission-control-design

Design and maintain the Aries Mission Control dark-theme visual system across Ops, Brain, and Lab contexts.

2|1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/DeliciousHouse/aries-app --skill mission-control-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-control-design
Source: https://github.com/DeliciousHouse/aries-app/tree/main/skills/mission-control-design
Command: npx skills add https://github.com/DeliciousHouse/aries-app --skill mission-control-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mission Control design guidance to maintain a cohesive, production-grade UI across evolving Aries dashboards, shells, and operator surfaces, ensuring consistent look and behavior.

Core Features & Use Cases

  • Anchor the product around three module identities (Ops, Brain, Lab) with distinct color systems and dedicated design language.
  • Define a reusable neon-tuned visual system, typography, layout rules, and component patterns (session cards, docks, chips) for scalable UI.
  • Provide explicit guidance for multi-model support, interaction rules, and build standards to accelerate UI restyles and new screen development.

Quick Start

Implement the Mission Control design system by aligning UI across Ops, Brain, and Lab and applying the specified color, typography, and session-card guidelines.

Frequently Asked Questions about mission-control-design

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

FAQPage Schema
How do I maintain a cohesive dark-theme design system across multiple dashboards?

A cohesive dark-theme design system anchors UI around distinct module identities like Ops, Brain, and Lab, applying reusable color tokens, typography rules, and neon treatments to ensure consistent visuals across evolving dashboards.

What is the best way to design session-card patterns for operator surfaces?

Designing session-card patterns for operator surfaces requires defining a reusable neon-tuned visual system with explicit layout rules and component patterns, ensuring scalable UI behavior and consistent look across multi-model dashboards.

How do I set up color identity and typography rules for multi-module interfaces?

Setting up color identity and typography rules for multi-module interfaces involves defining distinct color systems for each module context and applying dedicated design language guidelines to maintain production-grade UI consistency.

Can I use a single design system for multi-model badges and navigation components?

Yes, a single design system can support multi-model badges and navigation components by providing explicit guidance on interaction rules and build standards, accelerating UI restyles and new screen development across operator surfaces.

When do I need design tokens for a dark-theme UI shell?

Design tokens for a dark-theme UI shell are needed when maintaining a cohesive visual system across evolving dashboards, ensuring consistent color identity, typography, and neon treatments are applied uniformly across all module contexts.

Does this approach work for scaling UI across Ops, Brain, and Lab contexts?

Yes, this approach works for scaling UI across Ops, Brain, and Lab contexts by anchoring the product around three module identities with distinct color systems and a shared neon-tuned visual system for cohesive operator surfaces.