architect

The entry point for a new Robium application. It combines a lean design conversation with robotics stack selection, chooses the cheapest meaningful proof, records decisions without freezing provisional assumptions, and routes implementation to the skills that own each layer.

When to use this skill

• Starting a new robotics application from a rough idea.
• Choosing or reconsidering the stack, simulator, embodiment, environment, data path, visualization, or compute target.
• Decomposing a multi-subsystem robotics idea into a first buildable slice.
• Writing a durable decision record for a new app or genuine re-architecture.
• Skip architect for a bounded change in an existing flow. Read the affected code and use the matching tool skill directly.

Key directives