Choose where each rule applies
Create a standard in the workspace, then explicitly assign it to existing projects. Different projects can use different rulebooks. A shared default does not silently add itself to every project you already have.
Write the rule once.
Use it where it belongs.
Give your projects a common starting point. Manage engineering rules, writing guidelines and business defaults as shared, versioned standards.
One rulebook. Explicit assignments to the projects that need it.
Engineering standard
Release with evidence.
- Run the relevant tests.
- Record the outcome.
- Keep a rollback path.
WebsiteAssigned
APIAssigned
Next projectOnly if defaults are enabled
New defaults do not alter existing project assignments.
Start new projects with your defaults
Enable “Apply automatically to new projects” on an active standard. Projects created afterward receive it at creation, including projects created during agent authorization. Turning the setting off leaves earlier assignments intact.
Deliver the version agents should read
Every MCP read includes the full text and revision of active assigned standards alongside the project’s notes. Edit, archive or restore a rulebook centrally. Assigned projects receive the new active version on their next read, while the history remains available.
Before you connect
Standards are reference material. They do not override higher-priority user instructions, authorize actions or resolve contradictory rules automatically.
Your next agent can start here.
Copy the brief. Connect the same project. Verify the first save.