What this prompt does
This template generates a full drone fleet command interface, structured around operational clarity as a first principle. The prompt does not treat this like a typical dashboard — it explicitly encodes the constraint that "lives may depend on this UI," which forces the AI to prioritize emergency access, telemetry legibility, and signal loss handling over aesthetics. The seven output sections map directly to what a real operator needs: spatial awareness (map), fleet status, drone-level telemetry, mission authoring, geofencing, alerts, and emergency controls.
The template works because it bakes in anti-patterns as explicit prohibitions. Telling the model not to bury the emergency stop button or not to hide telemetry data produces structurally different output than a generic "design a dashboard." The color system (green/blue/amber/red) and typography split (condensed panels, monospace coordinates) give the AI a concrete visual language to implement rather than invent.
When to use it
- You are building a SaaS platform for commercial drone operators managing agricultural, inspection, or delivery fleets.
- A logistics startup needs a ground control station UI prototype to demo to investors or regulators.
- You are designing a public safety or search-and-rescue drone coordination tool and need a starting point for operator workflows.
- A hardware manufacturer wants a reference UI to bundle with their fleet management SDK.
- You need a Figma-ready wireframe spec or a React/Vue scaffold for a drone operations center.
- You are evaluating what a fleet control UI should cover before writing a product spec.
Example output
For [use_case] = "last-mile delivery fleet", [fleet_size] = "50 drones", [operations] = "urban package delivery", [framework] = "React + Leaflet":
Map view renders 50 drone markers on a dark Leaflet tile (CartoDB Dark Matter),
each color-coded by state. Clicking drone #DR-017 opens a side drawer:
Battery: 34% [AMBER] Altitude: 82m Speed: 12.4 m/s Signal: -68 dBm
Mission: Drop zone ETA 2m 14s Payload: released
Commands: [Return to Home] [Emergency Land] [Hold Position]
Fleet sidebar (scrollable, condensed):
DR-001 Active 98% Mission 3/7
DR-017 En-route 34% Drop ETA 2m
DR-033 Low batt 18% [ALERT] Returning
DR-044 Offline -- [SIGNAL LOST]
Pro tips
- Set
[fleet_size]precisely — "12 drones" produces a sidebar design very different from "200 drones," because the AI will choose virtualized lists versus grid cards automatically. - If your
[framework]is Mapbox GL JS rather than Leaflet, say so explicitly — the generated tracking code uses different layer and source APIs, and mixing them breaks the output. - For regulated airspace operations, add "FAA Part 107 / EASA UAS compliance labels required" to
[operations]— the prompt's geofencing section will then include airspace class overlays and authorization zone markers. - Pair the emergency controls section output with your actual hardware SDK's command signatures before using it in production — the prompt generates plausible API shapes, not SDK-specific bindings.
- If you only need the mission planner section, extract just item 4 from the Generate list and pass it as a standalone prompt — the template is modular enough to use in parts without losing coherence.
