zing

Zing gives your harness design super powers. Give it a brief; it generates several design variations, serves them in a live picker in your browser, and hands your pick back to the coding agent to keep building.

/zing Redesign our existing landing/login page to be a full-fledged landing page

Works in Claude Code · Cursor · OpenCode · Codex.

What

• explore — branch a fresh divergent set of new directions. based on initial prompt or a variation.
• remix — deepen a variation with your feedback. add refinements.
• pick — send one back to the agent to integrate into your codebase, or save it for later.

Generation is live — a placeholder spins in the browser while the agent writes each variant. For how it works under the hood (architecture, files, data contracts), see AGENTS.md.

Requirements

Bun >=v1.3.6

Install

# bun (recommended)
bun add -g @tenorxyz/zing
# npm
npm i -g @tenorxyz/zing

# drop the /zing stub into each harness's command dir
zing setup

Then /zing <brief> in Claude Code · Cursor · OpenCode · Codex.

Develop

To develop zing locally and test changes end-to-end:

bun dev:setup     # bun link (live global `zing`) + zing setup --link (symlinked stubs)
bun dev:cleanup   # remove the stubs + unlink

This symlinks the local setup so all changes should be immediately live. Already installed globally via bun or npm? dev:setup overrides it — no uninstall needed.

After dev:cleanup, restore the published CLI:

bun add -g @tenorxyz/zing   # or: npm i -g @tenorxyz/zing
zing setup

Publish

npm version patch        # bump + commit + tag (minor/major as needed)
npm publish              # access:public is set in package.json
git push --follow-tags