@pixelvibing/cli

The command line for PixelVibing: pixel art for your game, generated on the platform and pulled into your repository, and the Skills that teach Claude Code and Codex to do the same.

npm install -g @pixelvibing/cli
cd my-game
pixel-vibing-cli setup

setup goes a step at a time: it signs you in in the browser, makes the directory a local project, which means a pixelvibing.json and a pixelvibing/ folder, links it to one of your platform projects — picked from a list, or made there from an idea — keeps that project's own token, the one its Install tab in the web app shows, and installs the Skills — a hub, the style guide's, and one for each kind of art — into the coding assistants you mark, as many as you like: Claude Code, Codex, Cursor, Gemini CLI, OpenCode and GitHub Copilot. --harness names them instead; without a terminal it takes those the repository has, else Claude Code. It then asks whether the Skills are yours, for every project, in each harness's directory in your home (~/.claude/skills/, ~/.agents/skills/, ~/.cursor/skills/, ~/.gemini/skills/, ~/.config/opencode/skills/, ~/.copilot/skills/), which is the default, or this repository's alone (.claude/skills/, .agents/skills/, .cursor/skills/, .gemini/skills/, .opencode/skills/, .github/skills/); --scope user|project answers it. A block in AGENTS.md, and in CLAUDE.md when there is one, names which Skill to load for which request. A coding assistant reaches the platform through the CLI, so setup writes no MCP entry. A client that needs the remote MCP server copies its entry, with the project's token, from the project's Install tab in the web app, into a file kept out of git; logout removes the token from such entries. Each step it finds done already is skipped.

| Command | What it does | |---|---| | login, logout, whoami | Keep an account token for this machine in the system's credential store, or remove it | | init, link | Make a directory a local project, and name the platform project it generates for | | generate object\|creature\|concept-art | Make art on the platform, after saying what it uses of the account's limit, then pull it | | list, pull | List the project's assets by kind or tag, and pull one by id or name into pixelvibing/out/ | | tag | Set or show a concept art's tags, which say what it is for | | guide pull\|push\|revise\|show\|versions | Read and write the project's style guide | | seal | Seal pixelvibing/out/ into pixelvibing/build/assets.eac | | export default\|pixi\|phaser\|godot | Pack the art into sprite sheets and the map into placed sprites, for an engine | | update | Replace the installed Skills with the ones this version ships, add those it ships since, rewrite their block in AGENTS.md, leaving any MCP server entry as it is | | mcp headers | Print the header for the remote MCP server, from the kept token, for an entry written by hand | | editor | Open the PixelVibing desktop app on the project |

Every command takes --help, and --json for an answer a script reads. On a machine with no credential store, such as a CI job, set PIXELVIBING_TOKEN to a token made in the dashboard.