What problem does it solve? Connecting an AGV or mobile robot running ROS 2 / Nav 2 to a VDA 5050 fleet-control master requires translating MQTT/JSON order messages into navigation goals while keeping protocol concerns out of the domain model. This Skill provides the architecture, mapping rules, and checklist to build that connector without coupling domain logic to MQTT or ROS. ## Core Features & Use Cases - Clean Architecture blueprint: Domain entities (Order, Node, Edge, Action, State) with abstract ports for MQTT and navigation, plus application services for order handling, state assembly, and instant actions. - VDA 5050 to Nav 2 mapping cheat-sheet: Maps order nodes to NavigateToPose goals, edge speed limits to controller caps, telemetry topics to state fields, and instant actions like cancelOrder and initializePosition to Nav 2 equivalents. - QoS and protocol compliance guidance: Aligns MQTT QoS levels with ROS 2 QoS profiles, covers last-will connection handling, headerId increments, and JSON schema validation against the official v3.0.0 schemas. - Use Case: A robotics engineer needs their warehouse AGV to accept orders from a VDA 5050 master control system. Use this Skill to structure the connector so order stitching, action status state machines, and state publishing all live in testable application services. ## Quick Start Ask the AI to scaffold a VDA 5050 connector package with domain entities, MQTT and Nav 2 adapters behind ports, and an order handler that maps released nodes to NavigateToPose goals.
