What problem does it solve? Integrating real robot hardware with ros2_control requires writing a pluginlib hardware component, wiring it into the URDF, and configuring controller bringup — a process with many subtle failure points like RT-safety violations and plugin name mismatches. This Skill guides you through the complete implementation so the hardware component works correctly with the controller_manager. ## Core Features & Use Cases - Hardware Plugin Scaffolding: Generate SystemInterface, ActuatorInterface, or SensorInterface implementations with correct lifecycle callbacks (on_init, on_configure, on_activate) and RT-safe read()/write() loops. - URDF and Pluginlib Wiring: Produce the <ros2_control> xacro tag, pluginlib export XML, and CMake/package.xml declarations with matching name aliases. - Bringup Configuration: Create controllers.yaml and launch files that start controller_manager, robot_state_publisher, and spawners in the correct order. - Use Case: You are connecting a custom motor driver board to a mobile robot. Use this Skill to generate a SystemInterface plugin that reads encoders in read(), sends velocity commands in write(), and bring it up with a diff_drive_controller. ## Quick Start Ask the AI to scaffold a ros2_control SystemInterface hardware plugin for your robot, including the URDF ros2_control tag, controllers.yaml, and launch file.