Troubleshooting and Optimization·Task 7.2·Bloom: apply·Difficulty 3/5·8 min read·Updated 2026-07-14

Choosing the Right Lever: Prompt, Context, or Configuration

Adjust approach based on feedback and results

SUBy Solomon UdohReviewed by Solomon UdohAI-assisted · human-reviewed
In short
Choosing the right lever means mapping a translated critique to the correct place to apply it: a single prompt tweak for a one-off wording fix, the context or knowledge base for a missing piece of reference material every run needs, or a standing Project-level instruction for a rule that should apply to every future output. Picking the wrong lever, such as a one-time prompt edit for a rule that should always apply, causes the same correction to recur.

Where a fix lives decides whether it sticks

Having translated a reaction into a specific instruction, you face a choice that determines whether the fix holds: where to apply it. The same named change can go into the immediate prompt, into the context or knowledge base, or into a standing Project-level instruction, and the right choice depends on how often the change is needed. The Claude Certified Associate - Foundations (CCAO-F) exam treats this as an apply-level skill because getting the lever wrong is the single most common reason a correct fix fails to stick and the same correction keeps returning.

The judgement turns on a question about scope: is this a one-time adjustment, a piece of material every run consults, or a rule that should always apply. Each answer maps to a different lever. Misroute the fix, put a recurring rule in a one-off prompt, and you will re-apply it every cycle, which is exactly the correction treadmill the previous knowledge points warned about.

Choosing the right lever
Mapping a translated critique to where it should be applied: the prompt for a one-off wording fix, the context or knowledge base for reference material every run needs, and a standing Project-level instruction for a rule that should apply to every future output. The lever is chosen by how often the change is needed.

The three levers and what each is for

The prompt is the lever for a one-off. If the change matters only for this specific request, a wording tweak in the prompt is the right, lightweight home for it. Nothing about it should apply next time, so there is no reason to make it permanent. Using the prompt for genuinely one-time adjustments keeps the standing configuration lean and uncluttered.

The context or knowledge base is the lever for missing reference material that every run needs. If the fix is "the output was missing information the model should have had", a brand guide, the current product list, a policy document, that material belongs in the knowledge base where every run can consult it, not pasted into each prompt by hand. The standing instruction is the lever for a rule that should govern every future output: a tone constraint, a required section, a formatting standard. A rule is short and always-applies, which is exactly what a standing instruction is for. This three-way split is the same one formalised in the rule-reference-procedure placement test.

Matching the lever to how often the change is needed

The deciding question is frequency. Ask: will this same change be needed again, and if so, does every run need it or only some? A change needed once goes in the prompt. A change every run needs, if it is reference material, goes in the knowledge base; if it is a rule, goes in a standing instruction. That single question routes almost every fix correctly, and it connects directly to the promotion test in promoting a working fix into a standing instruction or Skill.

Two mismatches are worth naming because they are the exam's favourites. Putting a recurring rule in a one-off prompt means you re-add it every cycle, which is the correction that keeps recurring. Putting bulky reference material into a short standing instruction bloats every future prompt with content that belonged in the knowledge base, making every run heavier than it needs to be. The lever is not just where the fix technically works, it is where it works without creating a new problem.

Prompt
one-off wording fix for this request only
Knowledge base
reference material every run needs
Standing instruction
a rule that should always apply

What the CCAO-F exam trips candidates on

The first trap is fixing a rule that should apply to every future report by editing just the current prompt. It works for this one output, which makes it feel done, but next cycle the rule is gone and the same correction is needed again. The exam rewards recognising that an always-applies rule belongs in a standing instruction, so the fix survives every future run rather than evaporating with the conversation.

The second trap is loading reference material into a standing instruction meant for short rules. A standing instruction is for concise, always-on rules; stuffing a full brand guide or product catalogue into one bloats every prompt with content that should live in the knowledge base and be consulted as needed. The credited answer routes reference material to knowledge and keeps standing instructions lean. Both traps are the same mistake in mirror image: matching the lever to the content type and the frequency, not to whichever home is closest to hand.

Worked example

A consultant identifies three fixes for her client-report workflow. First, this week's report should reference a specific new regulation, relevant only to this client this quarter. Second, every report she writes must always open with an executive summary. Third, every report needs to draw on the firm's current service catalogue, which she keeps pasting in by hand. Where does each fix belong?

Each fix is already a named instruction; the task is routing, and the deciding question is how often each change is needed.

The new-regulation reference is a one-off: relevant only to this client, this quarter. Nothing about it should apply to next week's report for a different client. So it belongs in the prompt for this specific request. Making it a standing instruction would wrongly impose it on every future report; the prompt is the right lightweight home for a genuine one-time adjustment.

The executive-summary requirement is a rule that should always apply: every report she writes must open with it. That is exactly what a standing instruction is for. Placing it in the current prompt would fix this report and lose the rule next time, forcing her to re-add it every cycle, the recurring-correction trap. As a standing instruction, it governs every future report automatically.

The service catalogue is reference material every run needs, and she is currently pasting it in by hand. It belongs in the Project knowledge base, where every report can consult it without manual pasting. Crucially, it should not go into a standing instruction: it is bulky reference content, and cramming it there would bloat every prompt. Three fixes, three levers, each chosen by frequency and content type, one-off to the prompt, always-applies rule to a standing instruction, reference material to knowledge.

Common misreadings to avoid

Misconception

A fix that works in the current prompt is done; the prompt is a fine home for any correction.

What's actually true

The prompt is only the right home for one-off changes. A rule that should apply to every future output belongs in a standing instruction; left in a single prompt, it vanishes next cycle and the same correction recurs.

Misconception

Reference material the model needs can just be written into a standing instruction so it is always available.

What's actually true

Standing instructions are for short, always-applies rules. Bulky reference material like a brand guide or product list belongs in the knowledge base; putting it in a standing instruction bloats every future prompt with content that should be consulted as needed.

How this shows up on the exam

Domain 7 questions describe a fix and ask where it should be applied, or explain why a correction keeps recurring. The credited answer matches the lever to frequency and content type: one-off to the prompt, always-applies rule to a standing instruction, reference material to the knowledge base. When a scenario says "the same correction is needed every cycle," the diagnosis is almost always that a recurring rule was placed in a one-off prompt.

This knowledge point builds on turning a reaction into a specific instruction, which produces the named change to route, and it feeds promoting a working fix into a standing instruction or Skill, where the promotion decision is made. It shares its three-way logic with the rule-reference-procedure placement test in the optimization task statement. Choose the lever by frequency, and fixes stop recurring.

Check your understanding

Every weekly report a team produces needs the same correction: it must always include a risk section, which the model keeps omitting. What is the most durable place to apply the fix?

People also ask

Should a fix go in the prompt or the configuration?
It depends on frequency. A one-off wording change belongs in the prompt; a rule that should apply to every future output belongs in a standing instruction so the correction is not needed again.
When does a rule belong in a standing instruction?
When it should apply to every future output in a Project. Putting an always-applies rule in a single prompt means re-adding it every time.
Where does reference material every run needs belong?
In the context or knowledge base, not a standing instruction. Cramming bulky reference material into a short instruction bloats every future prompt.

Watch and learn

Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.

No videos curated for this concept yet

We are still curating the best official and community videos for this topic.

Official prep for this domain

Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.

References & primary sources

Adaptive study

Master this concept with Archie

Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.

Start studying