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.