seanrobmerriam

Tests must not depend on external systems, databases, or network calls. Mock external dependencies. Use test data, not production data. Tests must be independent and repeatable. Running tests multiple times must produce same results.

Every code path must have an explicit return value or exit condition. Functions must not reach the end without returning. If a function should return nothing, explicitly return undefined, null, or void.

Every error that could occur must be handled explicitly. Don't assume operations succeed. Wrap risky operations in try-catch blocks or use error checking. Propagate errors upward with context.

All functions, endpoints, and external interfaces MUST validate inputs before processing. Invalid inputs must be rejected with clear error messages describing what was wrong and what format is expected.

Code must maintain consistent state before, during, and after operations. Partial updates that leave system in inconsistent state are forbidden. Use transactions or atomic operations. If operation fails, restore previous state.

Every operation must provide clear feedback on success, failure, or partial completion. Users must know what happened, why it happened, and what to do next. Log operations for debugging. Return structured results with status and details.

Don't assume code works as intended. Test actual behavior against expected behavior. Write tests for normal cases, edge cases, and error cases. Test boundaries, limits, and constraints. Verify output matches specification.

Every loop must have a clear, explicit exit condition. Infinite loops are forbidden unless absolutely necessary and documented. Loop variables must be initialized, modified, and checked correctly. Don't modify loop variables within the loop body.

Simulate, render, and model aircraft flight instruments and sensors in software — including real-time display widgets, physics-accurate instrument behavior, sensor error modeling, and failure simulation. Use this skill whenever the user asks to build, design, or model any aircraft instrument or avionics display, including: attitude indicator, airspeed indicator, altimeter, VSI, turn coordinator, heading indicator, HSI, CDI, NAV/COM radios, transponder, EGT/CHT gauges, fuel quantity, oil pressure, ammeter, vacuum gauge, glass cockpit displays (PFD/MFD/EFIS), autopilot annunciators, engine instruments, or any cockpit sensor. Also trigger for: "simulate instrument lag", "model pitot-static errors", "build a six-pack widget", "render a gyro horizon", "instrument failure injection", "simulate icing on pitot tube", "gyroscopic precession model", "VOR needle simulation", "ILS CDI/glideslope", "build an EFIS", "model gyro tumble", "ADC (air data computer) simulation", or any request to render instruments as canvas/SV

Design and build flight simulators — from browser-based canvas/WebGL implementations to architecture documents for full sim systems. Use this skill whenever the user asks to build, design, or reason about a flight simulator, aircraft simulation, flight dynamics model, avionics system, ATC simulator, autopilot system, or any software that models aircraft behavior in 3D space. Also trigger for: "make a flying game", "simulate aircraft physics", "build a cockpit UI", "design a flight model", "how does X work in a flight sim", "build an autopilot", "ATC radar display", or any request involving aerodynamics, flight instruments, navigation systems, or aircraft performance modeling. Covers both educational browser-based sims and serious simulation architecture.

Expert reference and instructional resource for Instrument Flight Rules (IFR) operations, procedures, training, and systems. Use this skill whenever the user asks about IFR flying, instrument flying, instrument rating training, IFR procedures, approach plates, departure procedures, en route navigation, hold entries, airspace, ATC communication scripts, weather minimums, filing flight plans, partial panel flying, unusual attitudes, instrument currency, CFII instruction, or any topic related to flying in IMC (Instrument Meteorological Conditions). Also trigger for: "how do I fly an ILS", "explain a hold", "what is a missed approach", "VOR/DME approach", "RNAV/GPS approach", "IFR en route", "approach briefing", "instrument scan", "pitot-static system", "gyroscopic instruments", "IFR weather minimums", "alternate airport requirements", "IFR currency", "6 month IFR proficiency", "partial panel", "unusual attitude recovery", or any request to generate IFR training materials, lesson plans, or scenario briefs.

Create accurate, well-formatted aviation checklists for any phase of flight and any aircraft type. Use this skill whenever the user asks to create, generate, write, format, or review a flight checklist, cockpit checklist, emergency checklist, abnormal procedure checklist, or any document that organizes aircraft operating steps by phase or condition. Trigger for: "make a checklist for [aircraft]", "create a normal procedures checklist", "write an emergency checklist", "build a preflight checklist", "design a cockpit flow", "generate POH-style checklist", "create a checklist for my sim", "format these procedures as a checklist", "IFR departure checklist", "approach and landing checklist", or any request to turn aircraft procedures into a structured, actionable list. Covers GA piston, turboprop, jet, helicopter, and simulator/game aircraft.

Create detailed, realistic in-flight emergency scenarios for pilot training, simulator sessions, instructional design, and sim game scripting. Use this skill whenever the user asks to create, generate, write, or design any in-flight emergency, abnormal procedure scenario, or pilot training exercise involving system failures, weather encounters, medical emergencies, or aircraft malfunctions. Trigger for: "create an engine failure scenario", "write an emergency training scenario", "design a sim emergency", "build a partial panel scenario", "make an IFR emergency exercise", "generate a CFII training scenario", "write an emergency for my flight sim game", "create a progressive failure sequence", "design an inadvertent IMC scenario", "make a hypoxia scenario", "engine fire", "electrical failure scenario", "fuel exhaustion scenario", "structural damage scenario", "bird strike", "gear malfunction", "pressurization failure", or any request to describe realistic aircraft emergencies with symptoms, decision points, and

Guide for structuring and reviewing Erlang/OTP applications with `application`, `supervisor`, and `gen_server` behaviours, supervision trees, child specs, restart strategies, and crash/restart semantics. Use when designing, implementing, reviewing, or debugging Erlang services that should follow OTP principles such as process isolation, let-it-crash failure handling, and supervisor-managed recovery.