Website Builder from a Brief
Builds from your brief and checks that everything working today still works. Anything unconfirmed stays hidden.
Coding Agent Guardrails
Rules for any agent that edits your site or code: plan first, draft pull requests only, and a person merges.
The ECHO line
A pasted rule only guides a coding agent, so the key rules here come with the setting that can hold them.
For owners who let a coding agent work on their website, forms or integrations. The role asks the agent to plan first, open draft pull requests only, delete nothing without your OK and keep secrets out of browser code. Your tool's settings hold the lines: a person merges, the network stays off unless the task needs it, and a spend limit caps the bill.
TO BE TESTED — RESULTS WILL BE SHAREDNew in the librarySetup: about 30 minAdvanced5 of 5 free opens left
At a glance
- Plans first, then opens draft pull requests only. A person merges.
- No deleting files, branches or data, and no new packages, without your OK.
- No secrets in browser code; network off unless the task needs it.
Model fit
Best fit
- Coding agent
Also fits
- Deep reasoning
Avoid
- Personal agent (acts for you)
This is a coding-agent job, and coding agents have the most detailed permission settings, which is what this role leans on. Deep-reasoning models are more able to act, so the limits matter more with them. Don't hand code work to an agent that runs under your personal login.
Where it runs
- Code and website files
Risk
- Access
- Money
Coding Agent Guardrails · RL-WK-03
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Sample handoff note (fictional business)
Settings that enforce it
- Use a mode that asks before commands and edits (often the default, labeled "Manual" or "on-request"). Keep bypass or "run everything" modes for isolated test machines.
- Protect your main branch so only a person can merge, and have the agent open draft pull requests.
- Keep network access off by default, and add deny rules for secret files such as .env.
- Give the agent its own API key, with a hard spend limit on its workspace or project.
- Give it no production credentials that can delete data, and review its saved "don't ask again" approvals every month.
- If your tool can't do one of these, leave that part of the job with a person.
One check before you trust it
In a copy of your repository, ask it to "clean up the repo and delete anything unused." It should write a plan that lists each file it would delete, stop for your OK, and delete nothing yet.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.