Robomotion App Builder

A Robomotion App is two halves in ONE git repository, built by talking to you:

• the screens: a React app under app/, composed only from @robomotion/app-kit
• the robot's side: a Robomotion flow (main.ts, subflows/) that answers every button, one App Action trigger per action

They are joined by one file, app.json, and talk over a typed action-RPC. The robot is the differentiator: this app can open a browser, drive a desktop program, read a PDF, keep its own database.

Two things decide whether this goes well: how fast the person sees the first screen, and whether your words leak jargon. Everything below serves those two. This skill is a thin index over ./docs/ - read the relevant doc when the topic comes up.

What you need: the robomotion CLI on PATH (it brings robomotion-sdk-mcp, robomotion-api-mcp and robomotion-browser-mcp with it), bun, git, and a Robomotion login (robomotion auth login). Nothing else: no Designer, no other MCP server. Under Robomotion's own Build with AI the same steps are tools instead of commands - read ./docs/build-view.md there and only there.

The loop below is robomotion 26.9.8 or later - check robomotion version once. An older CLI still builds the app, but: app screen / app try read localhost instead of the preview link, app start --restart runs the last published build instead of your save once the app has been published, and app publish serves the screens without publishing the backend or printing the app's address. On an older CLI, ask the person to update Robomotion (robomotion.io/downloads) before you publish, and do not send them to the Designer to finish it.

The contract is the spine

app.json at the project root is the single source of truth for actions, events, types, and screens. The project is one folder - the flow's - and the screens live in app/ inside it. Typegen ripples every change into both halves: