architectlisted

# architect The entry point to robium. Given a robotics application idea, this skill turns requirements into a concrete stack decision — middleware, simulation, data, visualization, and training frameworks — plus a scaffold plan and a written **architecture brief**. It is the only skill that knows the whole robium catalog; everything else is reached by routing from here. Load it first on any new robotics app, then hand off to the domain skills for the actual build. ## When to use this skill - Starting a brand-new robotics application from a rough idea ("build a mobile robot that navigates a warehouse", "train a manipulation policy on an arm"). - The requirements exist but the stack is unchosen, or half-chosen and you want a sanity check before committing. - You need a durable, written architecture record the whole project builds from. - You want the routing map: "which robium skill do I load for phase X?" - Open-ended or backlog-driven kickoffs ("let's do demo 1", a vague feature idea) start with `brainstorming@superpowers` — it owns requirements-gathering. Architect takes over once requirements are settled (robot type, task, hardware, sim-vs-real, GPU) to make the stack decision itself, rather than brainstorming's own research improvising it. - Cross-references — go straight to the tool skill, skipping architect, when the stack is already chosen and the question is narrow: - Debugging or configuring an existing stack → the matching tool skill (`nav2`,