How I Actually Use ChatGPT: My Daily Workflow for Writing, Coding, and Thinking

I've been using ChatGPT almost every day for 18 months. Not dabbling—actually integrating it into real work. Writing, coding, research, thinking through problems.

Most "how to use ChatGPT" articles give you generic tips. "Be specific!" "Give context!" Sure. But what does that actually look like in practice?

This is my real workflow. The actual prompts I use, the patterns I've developed, and the mistakes I've learned to avoid. If you're already past the basics and want to see how someone uses ChatGPT professionally, this is for you.

My Setup: ChatGPT Plus + Custom Instructions

First, the basics. I pay for ChatGPT Plus ($20/month). The free tier is too limited for serious work—slower responses, usage caps, no GPT-4. If you're using ChatGPT for actual productivity, the subscription pays for itself in the first week.

More importantly: I've configured Custom Instructions. This is the most underrated feature. Here's roughly what mine say:

About me:

I'm a developer and writer. I work on web applications (React, TypeScript, Node.js) and write articles about productivity and AI. I prefer concise, direct communication. I value accuracy over speed—I'd rather you say "I'm not sure" than guess.

How I want responses:

Be direct and concise. Skip the preamble ("Great question!"). When I ask for code, give me production-quality code with proper error handling. For writing help, match my voice—conversational but substantive. If my request is ambiguous, ask one clarifying question before proceeding.

These instructions shape every conversation. ChatGPT stops adding fluff, gives me better code by default, and asks for clarification instead of guessing. It took me months to realize how much Custom Instructions improve the experience.

Writing Workflow: Not What You'd Expect

Here's the thing: I don't use ChatGPT to write for me. I use it to think with me.

Starting an Article

When I'm planning a new piece, I don't say "write an article about X." That produces generic AI slop. Instead:

I'm writing an article about [topic]. My main argument is [thesis].

Before I start writing, help me stress-test this idea:
1. What's the strongest counterargument?
2. What am I probably overlooking?
3. What evidence would make this more convincing?

Don't write the article. Just help me think through it.

This is the key insight: ChatGPT is a thinking partner, not a writing machine. The output I want isn't text—it's better thinking.

Editing and Tightening

After I write a draft (myself, not AI), I use ChatGPT to edit:

Here's a paragraph from my draft. It feels flabby. Identify:
1. Words I can cut without losing meaning
2. Sentences that repeat the same idea
3. Where I'm telling instead of showing

Don't rewrite it. Just point out the problems so I can fix them.

[paste paragraph]

Notice the pattern: I ask ChatGPT to identify problems, not fix them. This keeps my voice intact while benefiting from a second perspective.

Headlines and Hooks

One area where I do use ChatGPT for generation: headlines. I'm too close to my own work to see it fresh.

Here's my article about [topic]. The main takeaway is [key point].

Give me 10 headline options. I want:
- Specific, not generic ("7 Tools" not "Some Tools")
- Benefit-focused when possible
- No clickbait or exaggeration

[paste first 500 words]

I never use the headlines verbatim, but they spark ideas I wouldn't have found alone.

Coding Workflow: Where ChatGPT Shines

Coding is where ChatGPT has genuinely transformed my work. Not for writing entire applications—but for specific, targeted tasks.

Debugging

My most common use case. When I hit an error I don't immediately understand:

I'm getting this error in my React app:

[paste error message]

Here's the relevant code:

[paste code]

What's causing this, and what's the fix? Explain why the error happens so I understand it, not just how to make it go away.

The "explain why" part is crucial. I want to learn, not just copy-paste a fix. This approach has taught me more about React edge cases than any tutorial.

Writing Utility Functions

For well-defined, isolated functions, ChatGPT is excellent:

Write a TypeScript function that:
- Takes an array of objects with 'date' and 'value' properties
- Groups them by week
- Returns the sum of values for each week

Include:
- Proper TypeScript types
- Handle empty arrays
- Handle invalid dates gracefully
- JSDoc comments

I'm specific about requirements upfront because vague prompts produce vague code. The more constraints I give, the better the output.

Code Review

Before committing complex code, I ask for a review:

Review this function for:
1. Potential bugs or edge cases I'm missing
2. Performance issues
3. Readability improvements

Be critical. I want to catch problems before they ship.

[paste code]

ChatGPT won't catch everything a human reviewer would, but it catches enough to be valuable. It's especially good at spotting off-by-one errors and null pointer issues.

Learning New Tech

When I'm picking up a new library or framework:

I'm learning [technology]. I already know [relevant background].

Explain the core mental model I need. Not a tutorial—just the key concepts that, once I understand them, will make everything else click.

Then give me one small, practical example that demonstrates those concepts.

This approach is faster than reading documentation because it's targeted to what I already know. ChatGPT bridges the gap between my current knowledge and the new thing.

Thinking Workflow: The Underrated Use Case

This is where most people underuse ChatGPT. It's a surprisingly good thinking partner.

Decision Making

When I'm weighing a significant decision:

I'm deciding whether to [decision]. Here's the context:

[brief background]

Help me think through this:
1. What are the second-order consequences I might be missing?
2. What would I need to believe for each option to be correct?
3. What's the reversibility of each choice?

Don't tell me what to do. Help me see the full picture.

This pairs well with keeping a decision journal. ChatGPT helps me think more systematically before I commit to a choice.

Problem Framing

Often the real problem isn't the one I think I'm solving:

I'm trying to solve [problem as I currently see it].

Before I jump to solutions, help me question the framing:
1. Am I solving the right problem?
2. What assumptions am I making?
3. Is there a simpler version of this problem I should solve first?

This has saved me weeks of work on multiple occasions. Problem framing is an underrated skill, and ChatGPT is good at pressure-testing my framing.

Explaining My Own Thinking

Sometimes I use ChatGPT as a rubber duck—but a smart one:

I'm going to explain my reasoning for [decision/approach]. 

Listen, then poke holes in my logic. Where am I being inconsistent? Where are the weak points?

[explain reasoning]

Articulating my thinking to an AI often reveals gaps I couldn't see internally. The act of explaining is itself valuable.

What I Don't Use ChatGPT For

Just as important—where I've learned ChatGPT isn't helpful:

• First drafts of important writing. AI-written text lacks voice. I write first, then use AI to edit.
• Anything requiring current information. ChatGPT's knowledge cutoff matters. For recent events, libraries, or news, I use other sources.
• Final decisions. ChatGPT helps me think, but I make the call. It's an advisor, not a decider.
• Tasks I should learn myself. If I'll do something repeatedly, I learn it properly rather than outsourcing to AI.

Patterns That Took Me Months to Learn

Ask for critique, not creation

"What's wrong with this?" produces better output than "Write this for me." ChatGPT is better at improving than creating from scratch.

Request explanations, not just answers

Adding "explain why" or "help me understand" produces responses that actually build my knowledge instead of creating dependency.

Give examples of what you want

"Write it like this example: [paste example]" is more effective than describing the style you want. Show, don't tell.

Iterate in the same conversation

Follow-up prompts in the same chat are better than starting fresh. ChatGPT has context about what you're trying to do.

Save prompts that work

When I find a prompt structure that produces good results, I save it. My notes app has a "ChatGPT prompts" folder with templates for common tasks.

The Meta-Lesson

After 18 months, here's what I've learned: ChatGPT is not a shortcut. It's a tool that amplifies your existing skills.

If you're a mediocre thinker, ChatGPT won't make you a good one. But if you already think carefully, it helps you think faster and more systematically.

If you write poorly, ChatGPT will produce poor writing for you. But if you write well, it helps you refine your work more efficiently.

The people getting the most value from AI aren't using it as a replacement for skill—they're using it as leverage on top of skills they've already built.

Don't ask "how do I get ChatGPT to do my work?" Ask "how do I use ChatGPT to do my work better?"

That shift in framing changes everything about how you approach the tool. And it's the difference between getting generic AI output and getting genuinely useful assistance.

Start with one workflow from this article. Try it for a week. Adapt it to your needs. That's how you build a real AI workflow—through actual use, not theory.