Home / Techniques that change the result
Composing a system prompt from several sources
Merging the best rules from several system prompts works like an ordinary piece of writing, provided each imported rule is rewritten for its own context rather than copied as is, and the rules already in force settle any conflict.
A system prompt, or custom instructions depending on the interface used, is the text that frames Claude's behaviour before the first question is even asked, a role, a register, rules to follow under all circumstances. A system prompt found elsewhere, a template shared by someone else or a list of rules published as an example, almost always contains one or two useful sentences amid a lot of detail that does not concern your own use. Copying the whole thing as is also imports what does not apply to your context. Taking a single rule and rewriting it in your own words, for your own situation, is an ordinary piece of writing, the same kind used to draft any instruction meant for Claude.
Rewrite, do not copy
A rule copied word for word often carries vocabulary, examples or constraints specific to the situation of its original author. A rule aimed at a certain type of answer for a given professional audience does not carry the same meaning for a non profit audience. Rewriting the rule forces you to ask what it actually targets, before rephrasing it for the context where it will apply. This rephrasing work is what distinguishes borrowing an idea from copying a text.
Règle trouvée ailleurs : ne jamais utiliser de jargon technique sans le définir.
Règle réécrite pour son contexte : chaque terme métier du secteur associatif, adhérent,
cotisation, assemblée générale, se définit en une phrase à sa première apparition.
Who settles a conflict
An imported rule can contradict a rule already in place. Priority goes to the rule of the system prompt's owner, not to the imported rule: it is the owner who knows their own context and the reasons why their rule exists. Before adding a rephrased rule, you must therefore read it against the rules already in force and check that neither contradicts the other.
Checking that a rephrased rule still triggers the expected behaviour follows the same logic as testing a check before trusting it: a rule never put to the test on a real case has not proven that it works in its new context. Asking a question that should trigger the rule and reading the answer obtained is the simplest way to check it.
A rule copied as is, a rule rewritten for its context
The rule keeps the vocabulary and examples of its original author, which do not always match the situation where it is reused.
The rule is rephrased with the vocabulary and examples specific to the new situation, keeping the original intent.
A non profit manager copies into their account's custom instructions a rule found in a template shared online, phrased for commercial use. He then asks a question that should trigger this rule and reads the answer produced by Claude.
Write in one sentence what this situation establishes, and in one sentence what it does not establish.
What this establishes: That the non profit manager tested the imported rule on a real case before continuing to rely on it.
What this does not establish: That the rule, originally phrased for commercial use, produces the same useful behaviour for his own non profit context as it did for its original context.
The three most common miscalibrations
- Too broad This situation shows that any rule copied from a template shared online works correctly in a new context as soon as it is tested once.
- Too narrow This test proves nothing since it only involves a single question asked a single time.
- Beside the point This situation shows that system prompt templates shared online cover the needs of non profits well.
- Copying a system prompt found elsewhere also imports what does not concern your own context, along with the rule that is actually useful.
- Rewriting an imported rule in your own words forces you to identify what it actually targets before adapting it to your own situation.
- In case of conflict between an imported rule and a rule already in force, it is the rule of the system prompt's owner that settles it.
- Asking a question that should trigger the rephrased rule, and reading the answer obtained, checks that it works in its new context.
Spot a useful rule in a system prompt or custom instructions shared by someone else. Rewrite it in your own words for your own context. Add it to your custom instructions and ask a question that should trigger it, to check on your screen that it produces the expected effect.
These points depend on an interface or a rule that may have changed since this was written. Check them on your own screen before relying on them.
- This rule merging technique is not documented as such by Anthropic, the reference below only covers the general importance of a role in a system prompt. Check on your screen whether custom instructions are available on your own account before applying this exercise.
Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.
- Anthropic, Prompting best practices, section Give Claude a role consultée le 2026-09-02