ros2-architectlisted

# ROS2 Architecture Covers the three current ROS2 distributions; patterns are consistent across all three with version-specific notes called out where they diverge. C++ (`rclcpp`) and Python (`rclpy`) treated as equal first-class targets. **Development environment via Pixi + RoboStack** — the modern, cross-platform alternative to `sudo apt install ros-*`. See [STACK.md](STACK.md) for distro details and pinned tool versions. Python-side `rclpy` nodes inherit the typing, dataclass, asyncio, and testing rules from [python-architect](../../languages/python-architect/SKILL.md) — this skill adds the ROS2-specific layer on top. ## 0. Distribution selection | Distro | Type | Released | EOL | When to pick | |---|---|---|---|---| | **Jazzy Jalisco** | LTS | May 2024 | May 2029 | **Default for new production systems.** Mature, broad community, 3+ years of support left. | | **Kilted Kaiju** | non-LTS | May 2025 | Dec 2026 | When you specifically need a feature added in Kilted and can plan a migration before Dec 2026. | | **Lyrical Luth** | LTS | May 2026 | May 2031 | **Default for new systems once the ecosystem catches up** (typically 1–3 months post-release as third-party packages migrate). Long support window. | - **Migrate from Kilted before Dec 2026** — direct target is Lyrical (next LTS) for a 5-year runway. - **Jazzy → Lyrical migration** is straightforward; most code ports with minimal changes. - **`ros2-architect`'s patterns apply to all three** — the differences are in spec