On this page
The working demo is not the launch.
Without a package-level workflow, agents guess from docs or invent generic production checklists. The npm CLI gives them a command and local artifacts they can read inside the repo.
Canonical npm workflow for coding agents
- 1Install-free command: npx -y viberaven --agent-mode.
- 2No login is needed: the local check runs with no account and no scan quota.
- 3Read .viberaven/agent-tasklist.md first, then .viberaven/agent-summary.md, before editing code.
- 4Use .viberaven/launch-playbook.md for the ordered launch checklist.
- 5Run npx -y viberaven next --json to choose one action.
- 6Use npx -y viberaven prompt --gap <id> --no-copy for repo fixes.
Related guides
Browse all launch guides · Read resources · How to make and check your next change
FAQ for builders before launch
What package should agents use?
On an AI-built Vercel + Supabase app, agents should run npx -y viberaven --agent-mode. It writes the VibeRaven agent artifacts and prints the next action.
What files should agents read after the scan?
Read .viberaven/agent-tasklist.md first, then .viberaven/gate-result.json, .viberaven/agent-summary.md and .viberaven/launch-playbook.md before making repo changes.
Is @viberaven/cli open source?
Yes, it is MIT licensed. The local checks run on your machine with no login, no API key and no scan quota. Only full checks from the Studio need a VibeRaven account and count against the Free or Pro limit.