Unimicro CLI

Build, run and publish plugins for the Unimicro platform, from your terminal or using an AI agent.

A plugin adds pages and components inside the Unimicro web app, running against real business data. unimicro plugin is the command group for building them: create a plugin, add views, run a live dev loop against a real test company, validate, and publish.

Install

npm install -g @unimicro/cli

Node 18+, on Windows, macOS and Linux (x64 and arm64). The binaries are Go, shipped per platform through npm's optional dependencies, so nothing is downloaded at install time.

The loop

unimicro plugin create    # reserve the id, scaffold a working plugin, install deps, git init
unimicro plugin dev       # live dev loop, served from your machine
unimicro plugin slots     # where a slot, tab or column view can render
unimicro plugin add view  # a page, slot, tab or column view: updates manifest.json and scaffolds the source

Sign-in happens when it is needed: with no session the browser opens and the command carries on. The first time through it also asks to set up your developer licence and a test company.

The dev loop

unimicro plugin dev builds as you edit and serves the result straight from your machine, with no upload step. It opens the platform in your browser, which is where a view actually renders.

Skills for AI coding assistants

unimicro plugin create installs skill files into the plugin. They teach an AI coding assistant the platform — the CLI, the manifest and Host API, the business API your views read and write, and the design system — so your agent scaffolds correctly without documentation pasted into prompts. They are found through AGENTS.md and .claude/skills, and unimicro plugin skills update refreshes them without touching any you edited.

Interactive and scripted

Every guided flow has a full flag form, and --json gives machine-readable output, so the same commands work in a terminal, in CI and from an AI coding agent. unimicro plugin help lists what each command takes.

Project configuration

unimicro.config.json sits next to manifest.json and says how the plugin is built and run. It is optional: with no file the CLI infers npm run build and watches src/. unimicro plugin config prints what was resolved.