Originally published on Medium.

Sharing what actually works (and what doesn’t) when using ChatGPT to plan real-world frontend features.

---

How I Use ChatGPT to Plan Features as a Frontend Developer (And Where It Falls Short)

When I start building a new feature, my biggest challenge isn’t the code — it’s deciding where to start.

I used to open my editor with a vague idea like: “Build login page.”

Ten minutes later, I’d have five tabs open, three half-written files, and no direction.

Then I started using ChatGPT — not as a boss, but as a planning partner.

Here’s how I use it to move faster without getting lost, and also where it sometimes fails.

---

✅ What Works

1. Turning vague ideas into clear steps

Instead of: “Build dashboard,”

I ask:

“Break down steps to build a responsive dashboard in Next.js.”

It usually gives me:

• Set up layout
• Add sidebar, header
• Fetch data from backend
• Render UI components
• Handle empty/loading/error states

It’s not always perfect, but it gives structure when I have none.

---

2. Getting quick perspective on decisions

“Should I use a modal or a separate route?”

“What’s the difference between SSR and CSR in this context?”

ChatGPT helps me compare options. I don’t treat it as absolute truth, but it saves time in decision-making.

---

3. Scoping features

“What’s the minimal functional version of this feature?”

It helps me stop overbuilding.

Not every MVP it suggests is ideal — but it gets me thinking lean.

---

❌ Where It Struggles

1. Shallow answers if I’m not specific

If I ask too generally, the answers are too generic.

"How to build a dashboard?"

→ “Use components, fetch data, handle errors.”

No real value.

🔧 Fix: I learned to be very specific in my prompts.

---

2. It can hallucinate steps or concepts

Sometimes it lists tools or methods that don’t quite apply to my stack.

Or suggests unnecessary complexity.

I’ve seen it recommend:

• State libraries I don’t need
• Folder structures that aren’t relevant
• APIs that don’t exist

🧠 I treat its advice as a starting point, not a roadmap.

---

3. It doesn't understand my exact context

ChatGPT doesn’t see my project code.

It doesn’t know which files exist, what logic is already in place, or how I name components.

So, I have to filter its suggestions — always.

---

🧠 Final Thoughts

ChatGPT helps me plan faster and think clearer — but only when I guide it properly.

It’s a powerful assistant, not a replacement for my judgment.

It gives structure, not certainty. And that’s still valuable.

---

💬 What About You?

Do you use ChatGPT in your planning process?

What helps? What backfires?

Let’s compare notes — drop a comment.

---

✍️ Written by @denizgokbudak

Frontend developer sharing practical AI workflows and real-world dev experiences.