What this prompt does
This prompt makes the model a senior product designer and frontend engineer building tools for operators, and asks it to design a drone mission planner returning working component code rather than a feature list. It specifies six deliverables: a satellite map with draggable waypoints and inline leg editing, an altitude-profile panel that updates live, a no-fly-zone overlay that blocks or warns on conflicting waypoints, a mission-duration and battery estimate with a low-battery warning, return-to-home settings plus a pre-flight safety summary, and export to DJI/Pix4D formats with save/load. The structure works because it forces the UI to enforce physics and regulations rather than just displaying notes.
Three variables drive it. [platform] sets the target (default desktop control station). [stack] defines the framework and map library, such as Electron + React + Mapbox. [mission_type] describes the typical mission, like an automated survey mapping grid, which shapes defaults and the waypoint workflow. The critical detail is reactivity: the prompt asks that the altitude profile and battery estimate respond live to every waypoint drag, because a stale estimate is worse than none. No-fly zones and battery limits should block actions, not merely warn, so an unsafe or illegal plan can't quietly slip through.
When to use it
- You are building a drone, UAV, or operator mission-planning tool with map-based waypoints.
- Safety constraints like no-fly zones and battery limits must actively block, not just display.
- You need an altitude profile and battery estimate that recompute live as waypoints change.
- A pre-flight safety summary and return-to-home settings are part of the workflow.
- You need export to industry formats like DJI or Pix4D plus mission save/load.
- You want working components for a desktop or other operator platform, not a feature list.
Example output
Expect mission-planner component code in your [stack] plus a short note on how waypoint edits propagate to the altitude and battery estimates. The satellite map carries draggable waypoints with inline leg editing; an altitude-profile panel updates live; a no-fly-zone overlay visibly blocks or warns on conflicts; a duration and battery estimate shows a clear low-battery warning; return-to-home settings and a pre-flight safety summary precede launch; and export to DJI/Pix4D plus save/load round it out. It targets the [mission_type] you specify and is a buildable scaffold, not finished software.
Pro tips
- Set
[mission_type]precisely, since a survey grid and an inspection flight imply different waypoint defaults and workflows. - Choose
[platform]realistically; a desktop control station and a tablet field app have different layout constraints. - Make the altitude profile and battery estimate react live to every waypoint drag — a stale estimate is worse than none.
- Insist that no-fly zones and battery limits block actions, not just show a note, so unsafe plans can't slip through.
- Match
[stack]to your real map library so overlays and draggable markers are idiomatic. - If exports are weak, re-run asking explicitly for the DJI and Pix4D file structure plus mission save/load behavior.
