---
id: "action-front-load-intent"
type: "action-item"
source_timestamps: ["00:00:00"]
tags: ["prompt-engineering", "best-practices"]
related: ["concept-literal-instruction-following"]
action: "Explicitly state all constraints, formatting, and intent at the start of prompts for Opus 4.7."
outcome: "Prevents the model from generating literal but unhelpful outputs that lack necessary formatting or context."
speakers: ["Nate B. Jones"]
sources: ["s12-opus-47"]
sourceVaultSlug: "s12-opus-47"
originDay: 12
---
# Front-load intent in prompts

## Action

**Explicitly state all constraints, formatting, and intent at the start of prompts for [[entity-claude-opus-4-7-d12|Opus 4.7]].**

## Outcome

Prevents the model from generating literal but unhelpful outputs that lack necessary formatting or context.

## Why

Because [[entity-claude-opus-4-7-d12|Opus 4.7]] operates in a highly literal mode (see [[concept-literal-instruction-following]]), prompt engineers must:

- Explicitly state context.
- Explicitly state constraints.
- Explicitly state exact formatting requirements.
- Place all of the above at the **very beginning** of the prompt.

Do **not** rely on the model to infer what a 'good' output looks like based on vague instructions.

## Practical Pattern

```
[ROLE / CONTEXT]
You are a [...]. The user is a [...].

[CONSTRAINTS]
- Output must be exactly [...] sentences.
- Use [...] formatting (markdown / plain / JSON).
- Do NOT include [...].

[SUCCESS CRITERIA]
A correct response will: [...].

[TASK]
Now, [...]
```

## Cross-References

- Concept: [[concept-literal-instruction-following]]
- Claim: [[claim-combative-model]]
- Prerequisite: [[prereq-prompt-engineering]]
- Framework: [[framework-migration-decision]] (Step 4)