ground-view

Loads tower position context for Ground View development in the SKY-KING air traffic control system.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working on the SKY-KING tower (TWR) position need to understand how Ground View differs from the controller (CTRL) position before making changes, since both share core components but have distinct data models, routes, and UI behavior. ## Core Features & Use Cases - Context Loading: Loads the Ground View architecture, including the 3-panel layout (strip list, airfield map, transfer sectors) and its relationship to shared CTRL components. - API Reference: Documents Ground-specific routes such as /api/strips/ground-create, /api/strip-aircraft, and armaments/systems endpoints. - State & Safety Guidance: Explains groundStripAircraft state, 600ms debounced saves, formation summaries, and warnings about strip_aircraft schema changes and idx renumbering pitfalls. - Use Case: Before editing the tower position's aircraft drag-on-map feature, load this Skill to learn which components are shared with CTRL and which are TWR-only, avoiding regressions in MapView, TableView, or ClassicView. ## Quick Start Load the ground-view context and explain what I need to know before modifying the tower position's strip_aircraft editing flow.

Frequently Asked Questions about ground-view

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

FAQPage Schema
How do I start working on the Ground View tower position in SKY-KING?

Load the ground-view context first, then read CLAUDE.md. The Skill explains the 3-panel layout, Ground-specific API routes like /api/strips/ground-create, and which components are shared with the CTRL position versus unique to TWR.

What is the difference between Ground View and the controller position?

Ground View (TWR) manages airfield and ground operations with per-aircraft strip_aircraft rows, armaments, systems, and an airfield map. The CTRL position manages sector-based flight strips. Both share core strip card components, transfer panels, and filtering via DRY principles.

How does per-aircraft editing work in Ground View?

Each strip has strip_aircraft rows with datk (parking number) and kipa fields, edited via /api/strip-aircraft endpoints. Changes are debounced by 600ms before saving, and any modification must also update the server-computed formation summary.

Can I change the strip_aircraft table structure directly?

No. Schema changes to strip_aircraft require running /migrate and updating data-model.md. Also note that idx in strip_aircraft is a renumbered sequential index, not the original aircraft number stored in strips.aircraft_indices.

What should I check to avoid breaking other views when editing Ground View?

Verify that changes do not break MapView, TableView, or ClassicView, since Ground View shares core strip card components, the DraggableNeighborPanel transfer mechanism, ConfirmModal, ClockWidget, and the Query Builder filter with the CTRL position.