ros2-engineering-skills

# ROS 2 Engineering Skills > **Single responsibility:** This skill is an **API reference & code template guide** > for ROS 2 development. It tells you *how to use ROS 2 APIs correctly* and > *what mistakes to avoid*. It does NOT do CI/CD orchestration, incident response, > data analysis, or deployment automation — those are separate skill categories. A progressive-disclosure skill for ROS 2 development — from first workspace to production fleet deployment. Detailed patterns and code templates live in `references/`; read the relevant file before writing code. ## How to use this skill This always-loaded file carries routing, core principles, pitfalls, and anti-patterns — enough for quick questions and architectural decisions. For implementation work, use the Decision Router below to load the reference file(s) matching the task; the AI pitfalls table lists mistakes worth re-checking before generating code. `scripts/` are tools to run (scaffolding, QoS checking, launch validation), not reading material. When domains intersect (e.g. Nav2 + ros2_control) and recommendations conflict, favor safety > determinism > simplicity. **Execution log (opt-in):** When the Stop hook runs (Claude Code only) *and* the `SKILL_RUNS_LOG` environment variable is set, a session summary is appended to `.skill-runs.log`. If that file exists in the workspace, read the last few lines to avoid repeating past mistakes. Without the opt-in — and on platforms without hooks — the file is never created, so ...