system-architect

Design ROS 2 system architectures and node graphs with QoS policies.

8|2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/p1tl0rd/antigravity-ros2-skills --skill system-architect-p1tl0rd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/p1tl0rd/antigravity-ros2-skills/tree/main/.agent/skills/system-architect
Command: npx skills add https://github.com/p1tl0rd/antigravity-ros2-skills --skill system-architect-p1tl0rd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ROS 2 System Architect provides a structured blueprint for designing scalable node graphs, topic namespaces, and QoS configurations, reducing integration risk and boilerplate work.

Core Features & Use Cases

  • Node graph diagram delivery and hierarchical launch architecture design.
  • Interface and lifecycle guidance for robust ROS 2 components.
  • Example: design a multi-node system with clear QoS and remapping for modular deployment.

Quick Start

Describe your ROS 2 system goal in one sentence and the skill will generate a complete architectural plan.

Frequently Asked Questions about system-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a scalable ROS 2 system architecture with node graphs?

To design scalable ROS 2 system architectures, specify your system goal to generate a complete blueprint detailing node graphs, hierarchical launch architectures, and interface definitions.

How do I structure ROS 2 namespaces and launch configurations for a multi-node deployment?

Structuring ROS 2 namespaces and launch configurations is handled by generating a hierarchical launch architecture design that defines remapping and modular deployment for your multi-node system.

What is the best way to plan QoS policies and lifecycle management for robotic software projects?

Planning QoS policies and lifecycle management involves generating an architectural plan that enforces best practices for robust ROS 2 components, ensuring reliable communication across your robotic software projects.

Can I use this to generate interface definitions and node graph diagrams for modular ROS 2 deployment?

Yes, you can generate interface definitions and node graph diagrams for modular ROS 2 deployment by providing a one-sentence description of your system goal to produce the required deliverables.

What deliverables should I expect when creating a ROS 2 architectural plan for topic namespaces and remapping?

Deliverables for a ROS 2 architectural plan include a Node Graph Diagram, Interface Definition, and Launch Architecture, which collectively specify topic namespaces, QoS policies, and remapping configurations.