Opus 4.5 Prompting
Opus 4.5 behaves differently from earlier Claude models—more literal, more responsive to system prompts. This skill provides patterns for optimizing prompts accordingly.
Key Behavioral Changes
| Behavior | Implication |
|---|---|
| Literal instruction following | Be explicit about desired behaviors |
| Sensitive to "think" word | Use consider, evaluate, reflect instead |
| Highly responsive to system prompt | Dial back aggressive language |
| Tool trigger sensitivity | Replace MUST use with Use when... |
| Context awareness | Model tracks remaining token budget |
Quick Migration Checklist
When upgrading prompts from Claude 3.7/4.0:
- •Remove aggressive language (
CRITICAL,MUST,NEVER,ALWAYS) - •Replace
think step by stepwithconsiderorevaluate - •Add context/motivation ("because..." explanations)
- •Match prompt formatting to desired output style
- •Remove over-specified examples (trust the model)
- •Use gentler tool invocation language
- •Add XML tags for agent workflows (
<current-state>,<blocked>,<workflow>)
Reference Files
| File | Use When |
|---|---|
| patterns.md | Optimizing any prompt—comprehensive transformation rules and examples |
| agentic-patterns.md | Building agents, MCPs, long-horizon workflows with Opus 4.5 |
Utility Script
The scripts/analyze-prompt.py script analyzes prompts for deprecated patterns:
bash
echo "Your prompt text" | python3 scripts/analyze-prompt.py
Configure thresholds in scripts/config.json:
- •
min_words: Minimum words to trigger analysis (default: 1) - •
enabled: Enable/disable the analyzer (default: true)
Pattern Categories
The patterns.md reference covers:
- •Aggressive language — Soften
MUST,NEVER,CRITICAL - •Think variants — Replace when extended thinking disabled
- •Tool invocation — Prevent over-triggering
- •Formatting — Match prompt style to output style
- •Context/motivation — Add "because..." explanations
- •Over-specification — Trust the model more
- •Verbosity — Optimize for conciseness
- •XML structure — Use semantic tags for agent workflows
Agentic Best Practices
The agentic-patterns.md reference covers:
- •Context management — Progress summaries at 20% remaining
- •Sub-agent delegation — Preserve main context
- •Tool design — Avoid over-triggering in descriptions
- •State tracking — JSON for structured, text for notes
- •Long-horizon workflows — Incremental progress patterns
- •Parallel execution — When to parallelize vs sequence
- •Error handling — Fail fast, document blockers