ctrl-view

Loads controller workstation context for the SKY-KING flight control desk application.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working on the SKY-KING air traffic control system need the correct architectural context for the flight controller (CTRL) workstation before making changes, otherwise they risk breaking shared components used by the tower (TWR) position or violating domain constraints. ## Core Features & Use Cases - Context Loading: Provides the full operational picture of the CTRL workstation, including its four views (Map, Table, Vertical, Classic), main UI layout, and unique features like Flight Zones Mode, Block Spaces, and OCR handwriting recognition. - API and State Reference: Lists the key REST routes (strips, block-spaces, map-zones, serials) and the relevant App.tsx state (strips, transfers, session, filterQuery, viewMode) for the controller position. - Change Safety Guidance: Documents what is shared with TWR versus CTRL-only, with explicit warnings about query filtering, table_modes, and relevantSectors. - Use Case: Before modifying the StripCard component or map display logic, load this context to know whether the change affects both CTRL and TWR positions and whether a /qa run is mandatory. ## Quick Start Load the ctrl-view context before working on the flight controller workstation screen in SKY-KING.

Frequently Asked Questions about ctrl-view

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

FAQPage Schema
How do I work on the flight controller view in SKY-KING?

Load the ctrl-view context first, which describes the CTRL workstation's four views (Map, Table, Vertical, Classic), its main UI layout, and its state in App.tsx. It also lists the relevant API routes for strips, block spaces, and map zones.

What features are unique to the CTRL position versus the TWR tower position?

CTRL-only features include the sector MapView, Flight Zones Mode, Block Spaces, DraggableNeighborPanel, OCR with learned_digits, and altitude conflict detection. Shared with TWR are base strip card components, transfer logic, ConfirmModal, ClockWidget, and activity_log.

Does changing the StripCard component affect other workstations?

Yes, the base StripCard is shared between CTRL and TWR, so modifying it impacts both positions and requires running /qa. Changes to the CTRL map view do not affect the TWR ground map since they are separate maps.

Which API routes does the controller workstation use?

The CTRL position uses /api/strips for strip CRUD, /api/block-spaces, /api/map-zones, /api/strip-zone-assignments, /api/serials, and /api/activity-log. These are Express routes backed by PostgreSQL.

What should I avoid changing in the controller view?

Avoid changing query filtering logic without checking workstation_personal_filters, and be careful with table_modes since other workstations depend on specific modes. The session's relevantSectors field controls what the controller sees and must be updated everywhere it is used.