How do I keep my brand guidelines in one place instead of in every agent?
7 min read · Updated
If your brand guidelines are pasted into every agent, there are as many versions as agents, and no one can say which one an agent follows. Put the guidelines in your catalog once and have every agent read them from there.
1. Split the guidelines by concern
Write one rule for each concern the guidelines cover: tone, claims, naming and terminology, disclaimers, formatting. One rule per concern keeps each result attributable. When the naming rule fails, you know which standard was broken and who owns it. If you want a head start, look for a public rule on the same concern and adapt it.
How to write a rule covers the fields and the draft workflow.
2. Tag and test the rules
Give every rule the tag brand. Test each one on an output that should pass and one that should fail, then set it to active. The testing guide has the steps.
3. Group them in a rule set
Ask your agent to find the rules tagged brandand put them together as a rule set called “Brand guidelines.” The set pins the version of each rule. One call then checks an output against all of them, for the price of one call. See how to build a rule set.
4. Point every agent at the rule set
Name the rule set in each agent’s standing instructions, so every agent knows to check the same thing. The standing instructions guide has the text.
5. Update the set when the guidelines change
Upload a new version of the affected rule and test it. Set it to active. A rule set pins versions on purpose, so it does not change until you move it: list_rulesetsshows “newer version available” for the pin, and update_ruleset saves the next version of the set in draft. Test the set, then set it to active. Every agent that runs the set without naming a version gets the change, with no redeploy and no pasted copy to find. Agents that name an earlier version keep it.
Give every agent the same rules.
Write a rule, connect your agent, and run a critique in a few minutes. A new account includes 100 free critique credits.
Related guides
Pick one concern, write it the way you would brief a careful reviewer, and save it as a draft rule. Your agent can draft the Markdown and upload it for you.
Use the test status, run one output that should pass and one that should fail, then set the rule to active.
Pin rules to versions in a rule set. One call checks the output against all of them, for the price of one.
