← ClaudeAtlas

mission-creationlisted

Use this skill to create and drive a UAV mission end-to-end through the web UI with the Playwright MCP browser tools on LOCALDEV (https://<localdev-host>) — rebuild/redeploy, Keycloak login, the multi-step BY_ROUTE/REALTIME mission wizard, pre-flight, the Start-Mission FSM, AND the full per-drone flight-command lifecycle (arm → take-off → hover → start/fly → stop → observation divert → resume → home/land/disarm), per-tab verification, and cleanup. Use it for E2E UI verification (incl. verifying a controlbox/FSM change against real SITL), demos, or reproducing mission-flow bugs. Do NOT use it against staging or production (shared/real environments), for API-only or DB-seeded mission creation (no browser), or when localdev is not running.
atretyak1985/swarmery · ★ 3 · AI & Automation · score 62
Install: claude install-skill atretyak1985/swarmery
# Purpose Drive the full UAV mission lifecycle through the **web UI** on **localdev** using the Playwright MCP browser tools: (optionally rebuild the code under test), authenticate, create a mission with the wizard, run pre-flight, start it, **fly the drones through the FSM (arm/take-off/hover/start/stop/divert/resume/home/land/disarm)**, walk every flight tab, and clean up. Use it to verify a feature end-to-end — including a **controlbox / drone-FSM change against real SITL** — produce a demo mission, or reproduce a mission-flow bug. # When to use this skill - Trigger A — Verifying a mission-related change end-to-end through the real UI (not unit/API level) - Trigger B — Verifying a **controlbox / drone-FSM / MAVLink** change against **real SITL** by actually flying a drone - Trigger C — Reproducing a bug that only manifests in the live mission flow (wizard, pre-flight, fly tabs, telemetry, camera, divert/resume) - Trigger D — Producing a running demo mission with simulated drones on localdev - Trigger E — Smoke-testing the Awareness / Flight Control / 3D View tabs against live telemetry # When NOT to use this skill - Anti-trigger A — Targeting **staging or production** (project.json → cloud.envAlias) → STOP. Those are shared/real environments; mission create/terminate/flight-commands there affect other people (and real drones). Get explicit human approval and follow your staging-operations runbook for any staging work. - Anti-trigger B — Creating missions via REST/Grap