@unoverse-platform/studio

Unoverse Studio: the standalone authoring app. It reads your own rx/ project folder off disk and previews your components, templates, skills and nodes. No database, no Docker, no backend of its own.

npm install @unoverse-platform/studio
npx unoverse-studio

Studio opens on your project folder. Author in your editor, see it in Studio.

What you author

rx/components/   components: definition-backed UI, rendered by the generic SDK
rx/templates/    templates: whole app surfaces, states and layouts
rx/styles/       themes and tokens
prompts/         skills and prompt blocks
nodes/           declarative YAML node manifests

Everything is data. There is no codegen and no build step for your assets: the definition IS the artifact, and the same definition renders on web, in ChatGPT, in Claude, and on every other channel a universe serves.

Connecting a universe

Studio on its own is a viewer for your folder. Connected to a universe it becomes a full client:

• Live preview: Studio hosts the app natively. It asks the universe for its MCP-served app shell (ui://unoverse/app.html, the same one ChatGPT loads) and the app runs its own connections: chat, streaming, voice. Studio ships no renderer of its own; the renderer loads when required, from the universe that owns it.
• Publish: your components, templates, skills and prompts publish into the universe over its API, authorized by a publish key issued on that universe (unoverse key). Lint runs first; nothing leaves your machine until the rules pass.

The universe is somebody's deployment of the Unoverse platform. Yours, your team's, or a customer's. Studio never runs one.

License

MIT