Guardrails are your project’s rules, written in plain language. Vision reads them at the start of every turn, checks every change against them, and reports what it caught — automatically, with no hooks or CI to set up.
Guardrails
Vision checks every change against this project's rules and reports what it caught.
guardrails.md
- 1. Make sure changes pass TypeScript checks.
- 2. Unit test functions you make.
- 3. Repurpose existing code before making new code.
- …
How guardrails work
Your rules live in a guardrails.md file at the root of your project. Enforcement is automatic:
- At the start of every turn, Vision reads your guardrails.
- While building, the agents follow them.
- After the work ships, Vision reports what the checks caught — update cards show a quiet summary like “Guardrails caught 3 issues · 24 checks”, and the full per-publish history lives in the Guardrails tab.
The starter rules
When you first set up guardrails, Vision seeds a proven baseline:
- Make sure changes pass TypeScript checks.
- Unit test functions you make.
- Repurpose and abstract existing code before making new code.
- Look for edge cases in any functionality you make, and tell me about any you did not solve.
- Follow the project’s design doc and keep it up to date so design and copy stay consistent.
Adapt the wording to your project — the best guardrails are short and plain.
Adding and editing rules
Open Project settings → Guardrails. The tab shows your current rules read-only; edits go through the agent — click Edit with Vision and tell it what to change. That keeps the tab, the file, and the agents perfectly in sync.
Good rules to add: brand and copy standards, “never touch this table”, compliance requirements, review expectations — anything you’d tell a new teammate on day one.
Turning guardrails on and off
Team admins can toggle guardrails per project from the same tab. The toggle reads: “Vision checks every change against this project’s rules and reports what it caught.” Leave it on — it is your safety net when many people build in parallel.
Reviewing what was caught
The Guardrails tab keeps a history grouped by publish: every check that ran and every issue it caught. Update cards in chat link straight to the relevant publish group, so “what did the guardrails flag on this update?” is one click.