unoverse 0.1.28 → 0.1.29

package/README.md

@@ -1,19 +1,35 @@
 # unoverse
 
-The Unoverse front door.
+The Unoverse front door. Build agent-powered apps: interfaces as data, workflows
+on a canvas, agent skills in plain markdown.
 
 ```bash
-npm create unoverse@latest      # what are you building?
+npm install -g unoverse
+unoverse create        # asks what you're building, then sets it up
 ```
 
-- **A Studio project** — author components, templates, nodes, and agent skills.
-  Most people start (and stay) here. Launches [Unoverse Studio](https://www.npmjs.com/package/@unoverse-platform/studio).
-- **A universe** — run the full platform on your own infrastructure. For
-  operators: requires a registry access token from your Unoverse admin.
-- **A client app** — a website or embed talking to an existing universe.
+- **Studio** — author components, templates, nodes, and agent skills. Most
+  people start (and stay) here.
+- **Universe** — run the platform yourself, on your own infrastructure. Needs a
+  registry access token from your Unoverse admin.
+- **Client** — a client accelerator that talks to unoverse.
 
-Already have a universe? Its operator CLI lives inside it: `cd <universe> && ./unoverse`.
+Standing in a universe folder, the same command operates it:
 
 ```bash
-unoverse studio    # launch Studio any time
+unoverse start         # run it (--pull for the latest images)
+unoverse check         # is it healthy
+unoverse logs          # what is it doing
+unoverse where         # its addresses, local and deployed, probed live
+unoverse deploy        # ship it to your server
+unoverse stop
 ```
+
+## Build with Claude
+
+Creating a universe also installs a Claude Code skill (`.claude/skills/unoverse-create`)
+and registers the `canvas` MCP (`.mcp.json`). Open the folder in Claude Code and ask for
+what you want: components, templates, custom nodes, agent skills, or whole workflows
+built live on your Canvas. `unoverse update` keeps the CLI and the skill current.
+
+Documentation: https://github.com/unoverse-platform/docs

package/operator/skills/unoverse-create/SKILL.md

@@ -67,21 +67,21 @@ material.
 
 ## Step 3 — Deploy loop (after the artifact is written)
 
-Create a client org with `./unoverse new org <name>` (folder structure + default token
-set). Components and templates have NO scaffold command — author them from the references
-(mirror the closest existing artifact), and ALWAYS run `./unoverse lint` before deploying —
-it enforces the schema, token law, and state rules with doc-cited messages (0 errors
-required; justify any warning).
+Components and templates have NO scaffold command — author them from the references
+(mirror the closest existing artifact). Validation lives in Studio: its publish step
+lints every definition before anything leaves the machine (0 errors required, doc-cited
+messages; justify any warning), and the conformance checklist is
+[UNOVERSE_CONFORMANCE](https://github.com/unoverse-platform/docs/blob/main/unoverse/UNOVERSE_CONFORMANCE.md).
 
 | Artifact | To see it live |
 |---|---|
-| Component / atom / template / style | `./unoverse lint`, then restart unoverse — nodes SYNTHESIZE from definitions (no codegen); deploy with `unoverse deploy design` |
-| Existing component restyle/edit only | takes effect live (SDK reads `rx/` directly) |
-| Agent skill / prompt block | `docker compose restart unoverse` |
-| Node | `unoverse node lint`, then `unoverse node test <NodeType>`. No build: a node is YAML |
+| Component / atom / template / style | Preview in Studio (`unoverse studio`), then publish from Studio — the publish lint gates it |
+| Existing component restyle/edit only | takes effect live (the SDK reads `rx/` directly) |
+| Agent skill / prompt block | publish from Studio, same gate |
+| Node | Studio's Nodes screen: Load sample → Run. A node is YAML; running it is the only proof (no build) |
 
-Verify with `./unoverse check` (services, node catalog, bundles). Preview components in
-Studio: run `unoverse-studio` from the project folder, which opens on :4108.
+Verify the platform with `unoverse check` (services, schema, environment). Studio opens
+on :4108 (`unoverse studio` from the project folder).
 
 > In the platform monorepo (not the starter), the node docs live at
 > `packages/docs/nodes/`, the design journey at `packages/docs/design/`, and the dev loop

package/operator/skills/unoverse-create/references/agent-skill.md

@@ -62,4 +62,4 @@ is invalid.
 ## Ship
 
 `docker compose restart unoverse` — the runtime rescans skills at boot. Verify the
-skill appears via the platform's skill listing (`./unoverse check` for overall health).
+skill appears via the platform's skill listing (`unoverse check` for overall health).

package/operator/skills/unoverse-create/references/component.md

@@ -22,7 +22,7 @@ apps/unoverse/rx/orgs/<org>/components/<name>/ # ORG tier (the client's own micr
 A **flat component** (simple card/chart) is just `<name>.json` + `root` — one face, no manifest,
 no folders. Structure is EARNED; start flat.
 
-## The rules (lint enforces all of these — 0 errors required)
+## The rules (Studio's publish lint enforces all of these — 0 errors required)
 
 1. **Three homes for everything it shows** (AUTHORING §3):
    - static content → **hardcoded literals** in the layout (`value`, literal `items: []` on
@@ -147,6 +147,6 @@ component — its key nouns/verbs must appear in `whenToUse`'s first sentence.
 
 1. Study the closest exemplar; copy its folder shape.
 2. Write the envelope + manifest + layouts; put every shown thing in its ONE home.
-3. `./unoverse lint` — 0 errors (it cites the doc for every rule).
+3. Publish from Studio — its lint must report 0 errors (it cites the doc for every rule).
 4. Restart unoverse → Studio: mock (prop defaults + state picker + Inline/Focused
    toggle), then live. Debug: stream log → state inspector → definition; never guess.

package/operator/skills/unoverse-create/references/node.md

@@ -119,14 +119,14 @@ package only for a new integration.
 ## Verify
 
 ```bash
-unoverse node lint
-unoverse node test <NodeType>
+Studio → Nodes → your node (the catalog load reports schema errors)
+Studio's Nodes screen (Load sample → Run)
 ```
 
 Both must pass before the node is done. Lint names the rule and the page behind it, so read
 the message rather than guessing.
 
-`node test` calls the real service and needs no platform running. It reads keys from `.env`
+The Studio node runner calls the real service and needs no platform running. It reads keys from `.env`
 as `<CREDENTIAL>_<FIELD>` in upper snake case, so `openAICredential.apiKey` is
 `OPENAI_API_KEY`.
 

package/operator/skills/unoverse-create/references/template.md

@@ -107,7 +107,7 @@ themes `unoverse://theme/<org>/<theme>`.
 
 ## Validate & ship
 
-1. `./unoverse lint` — 0 errors (layout/name-sync rules, widths, reaction rules, tokens).
+1. Publish from Studio — its lint must report 0 errors (layout/name-sync rules, widths, reaction rules, tokens).
 2. Restart unoverse — the node re-synthesizes.
 3. **See it**: Studio — layout pills on top (default first, stateOrder order), local
    states down the left, freely combinable; acting inside the preview transitions like

package/operator/skills/unoverse-create/references/workflow.md

@@ -7,7 +7,7 @@ in the developer's browser as you build.
 
 ## Prerequisites (check before starting)
 
-1. **The platform is running** (`./unoverse start`, or `npm run dev` in the platform
+1. **The platform is running** (`unoverse start`, or `npm run dev` in the platform
    repo). The builder listens on `localhost:4106` — local machine only, by design.
 2. **The MCP is connected**: `canvas` should show connected with 14 tools.
    If it shows failed, the platform wasn't up when the session started — reconnect

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.28",
+  "version": "0.1.29",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",