01
The dossier is the source of truth
When something you are asked to build conflicts with a decision recorded here, the agent surfaces the conflict instead of silently overriding it.
GITHUB INTEGRATION
Most teams open a repo on day one and work out what they should have built somewhere around month four. ProtoVibing holds that step back. You run the loops first, and the repo shows up at the end carrying what those loops actually proved.
WHAT LANDS IN THE REPO
Close a loop and every document you confirmed gets written into the repo, grouped the way you would want to find it six months later.
THE CONSTITUTION
Claude Code and Cursor both look for an AGENTS.md or CLAUDE.md at the repo root before they write anything. ProtoVibing writes both files, so your validated documents become the rules the build runs under. Every copy carries the same three working agreements:
01
When something you are asked to build conflicts with a decision recorded here, the agent surfaces the conflict instead of silently overriding it.
02
The documents record what real validation proved or disproved. Decisions that were already tested do not get re-litigated without new evidence.
03
ProtoVibing re-syncs these documents as the project evolves. Build code goes alongside them, never on top of them.
HOW IT STAYS IN SYNC
Each closed loop opens a pull request and merges it, so you can read your validation history as commit history and review any single loop on its own.
Each run builds a single commit on top of whatever is already on your default branch, and carries every file it does not manage through untouched. Your build code and the synced documents share one repo without fighting over it.
Create one from inside ProtoVibing, or connect a repo you already have. Either way it sits in your own GitHub, and it keeps working if you stop using ProtoVibing.
Right now the repo holds validation documents rather than runnable code. That is deliberate. It gives the build something to answer to. When the Create phase starts emitting prototype scaffolding, that will land in the same repo next to the constitution.
WHAT WE BUILD NEXT
GitHub came first because the handoff to engineering was where teams were losing the most. None of these four are built yet. Design partners get the loudest vote, so tell us which one would change how your team works.
Slack
Post project updates and agent completions to a channel
Linear
Sync loops and phases with Linear issues and cycles
Figma
Import design files and keep assets in sync
Notion
Mirror project briefs and synthesis docs
GitHub sync comes with platform access. Apply and tell us what you are validating.