What problem does it solve? The strip transfer mechanism is the most critical core of the SKY-KING air traffic control system, and any uninformed change can break controllers' workflows. This Skill ensures the AI loads complete transfer-logic context before touching any transfer-related code. ## Core Features & Use Cases - Transfer Architecture Context: Documents the data model (strips, strip_transfers, sectors, sub_sectors), strip states (queued → active → pending_transfer), and the five transfer types including partial transfers with formation splits. - Change Governance Rules: Defines what may be changed freely (new fields via /migrate, transfer card UI), what requires CEO approval (accept/reject flow, split logic, state machine), and what is forbidden without full planning (strip_transfers table structure, getSectorSiblings, polling). - Mandatory Test Checklist: Lists five required post-change verifications including send/receive, rejection return, partial transfer splitting, duplicate prevention, and activity_log recording. - Use Case: Before modifying the IncomingTransferCard component or adding a transfer event type, activate this Skill so the AI understands the API routes (POST /api/strip-transfers, POST /api/strips/:id/split) and the activity_log event contract. ## Quick Start Load the transfer-logic skill before making any change to the SKY-KING transfer mechanism, split logic, or transfer UI cards.
