It has been such a Long time since I’ve written a blog post but there’s so much going on the world right now I thought it might be useful only for myself but others as well.
Today wanna talk about AI models and whole idea of best practices? These models produce different companies so only makes sense for there to be nuances between them plus AI is evolving at such a rapid rate. He cannot honestly expect something that well a year ago to work well today.
I’ve been trying to keep up with all source of influencers and newsletters on the essential of good prompting and it is near possible so here’s my attempt to show the new answers at least for the time being. I expect this block post the details in this post to be completely irrelevant in six months time, but at least you will see the differences between how one model and another can differ.
Simplified Model‑Specific Prompting Chart
| Model | Say What You Want vs Don’t Want | How Explicit to Be | Prompt Style That Works Best | Common Failure Mode |
|---|---|---|---|---|
| GPT‑4 / GPT‑4.x | ✅ Strongly prefer what you want | Medium–High | Outcome‑first with clear constraints | Over‑verbosity if length isn’t specified |
| GPT‑4o | ✅ What you want | Medium | Outcome‑first, minimal micromanagement | Adds extra context if prompt is vague |
| GPT‑4o Mini | ✅ What you want (critical) | High (but simple) | Short, focused prompts | Drops constraints when overloaded |
| Claude Sonnet 4.6 | ✅ What you want + alternatives | High | Structured, step‑based prompts | Skips unstated requirements |
| Claude Opus 4.7 | ✅ What you want (very literal) | Very High | Clear success criteria, fewer steps | Won’t infer intent you didn’t state |
| Gemini 1.5 Pro | ✅ What you want | High | Role + task + constraints upfront | Loses focus with mixed intent |
| Gemini 1.5 Flash | ✅ What you want (essential) | Medium | Simple, direct requests | Degrades in long or complex prompts |
| Gemini 2.x | ✅ What you want | Medium | Outcome‑driven with light structure | Still sensitive to ambiguity |
One‑Line Takeaways (for memory)
- All models: Positive instructions beat negative ones.
- Flagship models: Describe success, not steps.
- Smaller models: Fewer rules, clearer focus.
- Claude (especially Opus): If it matters, say it.
- Gemini: Be explicit early; don’t bury intent.
Shared task
“A countdown retro flip clock with just mins and seconds web app”
GPT‑4 / GPT‑4.x
Strength: outcome‑first, balanced guidance
Build a portfolio-quality **retro flip clock countdown** (mm:ss) using **React + Tailwind CSS**. Emphasise a calm, nostalgic aesthetic with smooth flip animations on digit changes (eased transitions). Include working start/pause/reset controls. Deliver clean, functional code with minimal commentary.✅ Why this works
GPT‑4 infers how to get there. You describe what good looks like, not the steps.
GPT‑4o
Strength: designer‑friendly, fast iteration
Design and implement a **retro flip clock timer** (minutes:seconds) in **React & Tailwind** — showcase quality. Aim for a gentle vintage style and subtle, realistic flip animations on the digits. The countdown should have start/pause/reset functionality. Provide the complete, maintainable code solution.✅ Why this works
GPT‑4o responds well to taste language (“polished”, “mature”) and doesn’t need micromanagement.
GPT‑4o Mini
Strength: simple, explicit, narrow
Task: Build a countdown flip clock (MM:SS) in React + Tailwind.
Requirements:
- Retro-style UI (calm look & feel)
- Smooth flip animation for digit changes (with easing)
- Start, pause, and reset controls
- Clean, simple code
Finally, output the full React component code.Requirements:
✅ Why this works
Mini models drop constraints when overloaded—keep it short, concrete, and narrow.
Claude Sonnet 4.6
Strength: structure + clarity
You are a creative front‑end developer with a keen design eye.
Goal: Build a **retro flip clock countdown** (minutes & seconds) web app.
1. Use React + Tailwind for implementation.
2. Apply a calm, vintage aesthetic (tasteful colours, soft contrasts).
3. Implement subtle flip animations for digit changes (smooth easing).
4. Include fully functional start, pause, reset controls.
Deliver the complete code for this component.✅ Why this works
Sonnet likes ordered structure and benefits from numbered steps.
Claude Opus 4.7
Strength: literal, precise, high‑fidelity execution
You are designing a portfolio-ready **retro flip clock countdown** (MM:SS).
**Success criteria:**
- Implement with React + Tailwind
- Nostalgic, **calm retro aesthetic** (clean typography, subtle styling)
- Smooth, realistic “flip” animations on digit change (ease-in timing)
- Fully functional timer (start, pause, reset)
Provide the final, production-quality code accomplishing this.✅ Why this works
Opus will not infer missing intent. Clear success criteria = excellent results.
Gemini 1.5 Pro
Strength: explicit role + task + constraints
You are a design-savvy front-end engineer.
**Task:** Build a **retro flip clock countdown** web app (minutes & seconds) using React + Tailwind CSS.
**Design cues:** Calm, nostalgic look and feel; smooth flip animations on digit transitions.
**Functional requirements:** Timer with start/pause/reset controls, accurate countdown behaviour.
**Deliverable:** Well-structured, shippable code (include brief comments if helpful).✅ Why this works
Gemini Pro performs best when role, task, audience, and constraints are explicit up front.
Gemini 1.5 Flash
Strength: fast, direct, scoped
Create a **retro flip clock** countdown (MM:SS) in **React** with **Tailwind**.
- Calm retro aesthetic UI
- Smooth flip animation for each second/minute change
- Start, pause, reset buttons
**Output just the React component code.**✅ Why this works
Flash excels at short, direct instructions and degrades with long context.
Gemini 2.x
Strength: outcome‑driven, slightly more flexible
Design & code a **retro flip clock countdown** (minutes:seconds) using **React + Tailwind**. Focus on a calm, vintage aesthetic and realistic flip-card animations for the seconds/minutes (smooth easing transitions). Ensure it’s fully functional (start/pause/reset), and produce clean, production-ready code.✅ Why this works
Gemini 2.x handles high‑level outcomes better than earlier versions, but still needs clarity.