Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Create a simulation-only exercise for [robotics signal or workflow]. Identify each node, topic, message type, unit, coordinate frame, and timestamp convention. Generate a small known input and trace it through transformation and visualization. Test delayed, missing, stale, and incompatible messages, plus startup and reset. Verify at least one coordinate transformation against a hand-calculated example. Keep all actuation simulated. Report the observed data path, repeatable checks, model assumptions, and the gap between this software exercise and any future physical deployment.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- ROS REP 103 — Units and coordinate conventions
- Nav2 — Odometry and coordinate transforms
- ROS 2 — Topic communication concepts
Documentation links checked .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Robotics prompt keeps all actuation simulated and asks for independent coordinate fixtures; no simulator was executed.