vibeprint GitHub

The sketch is the spec.

Draw your architecture on an iPad. Claude Code or Codex marks it up in blue, then builds against it.

in your repo, then npx vibeprint and scan the QR code with your iPad

A Vibeprint session on an iPad Black ink, drawn by the user: a web app connected to an api, which connects to postgres and an email worker; a cron box also feeds the worker. After Submit, the agent's blue marks appear: faint tags under each box, a proposed redis cache in dashed blue, a strike through cron with the note "the worker can run this on a schedule", and the question "retries with backoff?" beside the email worker. web app api postgres email worker cron frontendservicedatabaseworker redis cachecache1 the worker can runthis on a schedule2 retries withbackoff?? building
claude
1 add, 1 strike, 1 question

Your ink stays yours

The agent writes beside your shapes, never on them. One tap hides everything it drew.

Claude Code and Codex

One MCP server. Agents read the approved architecture before they build, and ask before they change it.

Lives in your repo

The sketch, the graph and every mark are plain JSON in .vibeprint/, committed with your code.