atc-ux

Reviews ATC controller and tower HMI screens against FAA, EUROCONTROL, and ICAO human factors standards.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/levori119/skyboard --skill atc-ux-levori119
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atc-ux
Source: https://github.com/levori119/skyboard/tree/main/.claude/skills/atc-ux
Command: npx skills add https://github.com/levori119/skyboard --skill atc-ux-levori119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing air traffic control (ATC) workstation interfaces without human factors guidance risks cluttered displays, poor color usage, and slow operator comprehension. This Skill provides a standards-based UX/UI audit checklist for controller (CTRL) and tower (TWR) screens so every display decision is grounded in FAA HF-STD-001, EUROCONTROL CWP/HMI, and ICAO Doc 9758 rather than personal opinion. ## Core Features & Use Cases - 8-Principle Audit Checklist: Evaluates perceptual hierarchy, color rationale, dark mode defaults, minimal glance time, human-in-command control, error prevention, consistency, and feedback/status visibility. - Standards-Backed Criteria: Each principle cites professional sources (FAA HF-STD-001, EUROCONTROL PHARE CWP/HMI, ICAO Doc 9758, Ahlstrom & Arend color usability research) with concrete pass/fail checks like WCAG AA contrast and redundant color coding. - Structured Review Workflow: Rates each principle as compliant, partial, or missing with examples, then prioritizes fixes by safety/operational value versus effort. - Use Case: Before shipping a new SectorDashboard or GroundView screen, run the audit to verify that critical alerts use red exclusively, text meets 4.5:1 contrast on dark backgrounds, and every action gives immediate visual feedback. ## Quick Start Ask the assistant to run an atc-ux review on the SectorDashboard screen and report which of the eight human factors principles pass or fail.

Frequently Asked Questions about atc-ux

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

FAQPage Schema
How do I review an ATC display for human factors compliance?

Select the screen or component, then evaluate it against the eight core principles: perceptual hierarchy, color rationale, dark mode, glance time, human-in-command, error prevention, consistency, and feedback. Mark each as compliant, partial, or missing with concrete examples, then rank fixes by safety value versus effort.

What UX standards apply to air traffic control interfaces?

The primary references are FAA HF-STD-001 (Human Factors Design Standard), EUROCONTROL CWP/HMI guidance from the PHARE program, ICAO Doc 9758, and the Ahlstrom & Arend 2005 FAA study on color usability in ATC displays.

What colors should alerts use in ATC HMI design?

Red is reserved exclusively for alerts requiring immediate attention, yellow for warnings or pending states, cyan for information, white for normal data, and gray for inactive elements. Color must never be the only channel; pair it with shape, text, or icons for colorblind users.

Does dark mode matter for controller workstation displays?

Yes, dark backgrounds are the recommended default for control rooms and towers because controllers prefer them and they reduce eye fatigue. Text must still meet at least WCAG AA 4.5:1 contrast, with AAA preferred for critical information.

When should confirmation dialogs be used in ATC interfaces?

Require confirmation only for destructive or irreversible actions like deletions or canceling a transfer, and avoid modals for routine clicks. Provide undo for common operations and large click targets following Fitts's law to prevent slips.