Adds a structured reference under remote-aircraft/ covering the full implementation spectrum for RC-aircraft and fully autonomous drones — from structural design through production-grade deployment across four languages.

Guidelines (remote-aircraft/guidelines/)

Six markdown documents covering each requirement dimension:

Firmware skeletons (remote-aircraft/firmware/)

12 runnable skeletons — 4 languages × 3 complexity tiers:

Example — Zig comptime PID (zero-allocation, production tier):

const PidGains = struct { kp: f32, ki: f32, kd: f32 };

const PidState = struct {
    integral: f32 = 0.0,
    prev_error: f32 = 0.0,

    pub fn update(self: *PidState, g: PidGains,
                  setpoint: f32, measured: f32, dt: f32) f32 {
        const err = setpoint - measured;
        self.integral = std.math.clamp(self.integral + err * dt, -400.0, 400.0);
        const deriv: f32 = if (dt > 0) (err - self.prev_error) / dt else 0.0;
        self.prev_error = err;
        return g.kp * err + g.ki * self.integral + g.kd * deriv;
    }
};

Example — Python MAVSDK mission runner (production tier):

async def run_mission(connection_url: str, waypoints: List[Waypoint]) -> None:
    drone = System()
    await drone.connect(system_address=connection_url)
    await preflight_health_check(drone)          # GPS, IMU, battery check
    await drone.mission.upload_mission(build_mission_plan(waypoints))
    await drone.action.arm()
    await drone.action.takeoff()
    await drone.mission.start_mission()
    # safety_watchdog runs concurrently: RTL on low battery or link loss

Notes

• All busy-wait delay stubs in Zig/C are clearly annotated with warnings to replace with SysTick/hardware timer before use on real hardware.
• .gitignore updated to exclude root/ Go module cache artifacts.

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.