Lesson 1557 of 2116
How prompt portability differs between Claude, GPT, and Gemini
A prompt that hits 95% on Claude can hit 70% on GPT — design for portability or pick one.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1The premise
- 2prompt portability
- 3vendor differences
- 4prompt engineering
Concept cluster
Terms to connect while reading
Section 1
The premise
Each model family has prompt idioms that maximize its quality — copy-pasting across vendors leaves performance on the table.
What AI does well here
- Identify prompt patterns each family prefers (XML for Claude, role-tags for GPT)
- Maintain per-vendor prompt variants when quality matters
What AI cannot do
- Find a single prompt that is best on all three
- Promise equivalent behavior across vendors
Key terms in this lesson
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “How prompt portability differs between Claude, GPT, and Gemini”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 40 min
When to Fine-Tune vs When to Just Prompt: A Decision Framework
Fine-tuning is expensive and slow to iterate on. Prompting is fast and free. Knowing when fine-tuning actually pays off saves teams from premature optimization.
Creators · 40 min
Prompt Caching Comparison: Anthropic, OpenAI, Gemini
How prompt caching works across vendors and where it pays off.
Creators · 11 min
How Image Input Pricing Varies Across Vendors
Image tokens cost wildly different things on different providers; budget accordingly.