A rule is a short instruction the project remembers: “no exclamation marks”, “always give prices with tax”, “address customers as you, never as dear”. Where the profile describes who you are, rules are the specific corrections that came out of using Acme.
How rules appear
Two ways, and both end in the same list:
Say it once
Correct a draft in plain words.
When you say “shorter” or “no emoji”, Acme offers to save it as a rule. Accept, and the next draft already follows it.
Write it yourself
For things you already know.
Open Profile → Rules, choose Add rule and write one sentence. One rule, one instruction.
Manage them
Keep the list short and useful
Open the list
Choose Profile → Rules. Newest rules are on top, with the draft that produced each one.
Switch off, do not delete
Turn a rule off to see how a draft changes without it. Turn it back on in one click.
Merge duplicates
Two rules that say almost the same thing slow every answer down. Keep the clearer one.
Good and bad rules
| Works well | Works badly |
|---|---|
| Never use exclamation marks | Be nicer |
| Write prices with the currency sign before the number | Make it professional |
| Start replies with the customer’s name | Sound like us |
| Keep subject lines under 50 characters | Keep it short |
The difference is that a good rule can be checked: you can look at a draft and say whether it was followed.
If a rule keeps being ignored, it is probably too vague. Rewrite it with a concrete example of what you want.
Frequently asked questions
How many rules can a project have?
There is no fixed limit, but a list of five to ten rules works best. Long lists make answers slower and contradictions more likely.
Do rules apply to every project?
No. Rules belong to the project where you saved them. To reuse a set, copy the workflow into another project and add the rules there.
What if a rule conflicts with my request?
Your request wins for that answer. Acme will mention the conflict and ask whether to change the rule.