I look at prompts all day. Not because I'm some kind of prompt engineer. But because using AI well is how I get my work done faster than I ever have before.

After enough reps, you start to notice something. When a prompt doesn't work, most people just rewrite it. Change some words, add more detail, & try again. Sometimes the 3rd version works. But you can't tell what actually fixed it, so you can't repeat it next time.

I got tired of guessing. So I started paying attention to what kept going wrong. After a while, the same 5 things kept showing up. Not a checklist I run before every prompt. More like a mental shortcut for when something's off and I can't tell why.

1. Can you state the task in 1 sentence?

If you can't say what the prompt is asking the model to do in 1 sentence, the model can't figure it out either. Long prompts aren't the problem. Buried asks are.

To clarify, a prompt can have 3 or 10 asks. That's fine.

What matters is that you can explain each one simply. If you can't state it, the model can't follow it, and you won't even notice when the output misses it.

2. Does the framing actually change the output?

"Act as a world-class marketing strategist" sounds like it should matter. Paste the prompt with and without that line. If the output doesn't change, the framing is decoration.

I still use roles though. When I write "act as a financial advisor," I'm not expecting the model to suddenly have a CFP license. I'm putting myself in a headspace where I ask better questions. The role shifts my thinking, not the model's.

Just know which one you're doing.

3. Did you specify what the answer should look like?

Format, length, structure, & sections. If you leave the output shape wide open, the model picks for you. Sometimes that's fine.

Usually it's not.

4. Does the prompt handle failure before it happens?

I'll be honest. I don't write failure instructions on the first try most of the time. I don't know what bad output looks like until I see it. The model does something wrong, & then I say "don't do that." Like correcting a kid. You don't know what they're going to do until they do it.

So this question is less "did you build in guardrails" & more "the prompt keeps giving you bad output, did you think to tell it what to stop doing?"

5. Will you get a real answer or generic advice?

Ask the model, "how do I get better at my job" & you get 10 bullet points that apply to everyone and help no one. A good prompt forces a specific answer that the model wouldn't give unprompted.

The exception is when you want generic. Sometimes I want the model to just throw ideas at the wall. Not accurate, not tailored, just a pile of options I can react to.

That's brainstorming, not a prompting failure. The question is whether you got generic output on purpose or by accident.

---

I'm still learning. If you've got something that works for you that I didn't cover, I'd rather hear it than assume I've figured this out.

I write a lot of decision prompts. Money stuff. Career stuff. "Should I leave this person" stuff.

I used to get stuck at the start.

Financial planner? Career coach? Relationship coach?

I'd sit there picking the role like it mattered. Sometimes I'd open another tab & search for the exact job title of the person who handles this kind of thing.

It doesn't matter.

The model gives you roughly the same answer either way. Roles in prompts are mostly theater.

But naming the role got me to actually explain my situation. Once I typed "you're a financial planner," I started talking like I was talking to a financial planner. I gave context. I said what I was trying to figure out. I mentioned what I was worried about.

The role wasn't doing anything for the model. It was doing something for me.

So I stopped picking it. I made the prompt pick it. 1 prompt, saved once, reused for every decision.

What I use now:

I'm trying to decide whether to [X] or [Y]. First, name the type of person who makes this kind of decision well and what they pay attention to. Then list the steps they'd take. Then tell me where most people get it wrong, and what they end up regretting a year later. End with one sentence: based on the steps and the failure mode, what would this person actually tell me to do?

4 moves, in order:

1. Name the expert and what they watch for. You don't have to know.
2. List the steps that person would take.
3. Name where most people screw it up and what they regret a year later.
4. 1 sentence verdict so you get an actual answer, not a framework.

The regret line is the one that does the work. Ask a model to weigh a decision & it hedges. You get pros, cons, "it depends." The regret framing forces it to commit. It has to name the thing you actually needed to hear.

And if the model can't name a real regret, that tells you something too. The decision probably isn't as big as you're making it. Move on.

Works for "pay off the car or invest." Works for "take the job or stay." Works for "should I leave this person or try harder."

The role changes. You don't have to.

Save it once. Use it for every decision.

You're closing your laptop for the day & your brain is still running. The client's email you forgot to send. The task you started but never closed out. That thing someone mentioned in a meeting that you know matters & you don't want to forget.

You know yourself. By the next work morning, half of it is gone.

Your phone's mic button is right there.

You know it exists. Are you using it?

I open Claude, tap the mic icon, and ramble for 2 minutes about where things stand. What's done, what's not, what needs to happen next.

No organizing. No filtering. Just a brain dump.

Then I paste 1 prompt under the whole mess. (This works the same way in ChatGPT or Gemini)

It comes back sorted, prioritized, & ready to follow in the morning. Whether it's a daily recap or a weekly review.

You are a planning assistant. Everything above this prompt is a dictated brain dump. It might cover one day or an entire week.

Step 1: Figure out the timeframe. If the dictation covers a single day, treat it as a daily reset. If it covers multiple days, treat it as a weekly review. If you can't tell, ask me.

Step 2: Go through the dictation & extract these details. Present them to me for confirmation.

- Tasks completed
- Tasks started but not finished (& where they stalled)
- Tasks that got dropped or pushed
- New things that came up that weren't on the original plan
- Deadlines or commitments mentioned
- Anything I flagged as important, frustrating, or urgent
- Anything blocked or dependent on someone else

If something isn't mentioned, mark it as [NOT MENTIONED].

Wait for me to confirm or correct before moving on. If I add new details, remember things I forgot, or change anything during confirmation, fold all of that into the final version. Treat the confirmation step as a second pass, not just a yes/no.

Step 3: After I confirm, structure everything into a plan.

If daily reset:
- First thing tomorrow (the 1-2 tasks to start with)
- The rest of the day, ranked by priority
- Waiting on (anything blocked)
- Can wait (tasks that won't hurt if they slip another day)

If weekly review:
- What got done (bullet points)
- What's carrying over & why (bullet points)
- Next week's priorities, ranked by urgency
- Anything to drop or delegate if the week gets tight

Present this to me for confirmation before finalizing. If I make changes, update & present again.

Rules:
- Pull every specific detail from the dictation. Task names, project names, people, deadlines, status.
- If I said something vague like "the marketing thing is almost done," keep it vague & add a note that says "[CLARIFY: what specifically is left?]"
- Do not invent details that aren't in the dictation.
- Match the tone & language of how I speak. Write like I talk.
- If I wouldn't say it out loud, don't write it.
- For task lists & priorities, keep it plain. Just list them.
- For any "carrying over" or context sections, use a mix of short declarative sentences & longer sentences for context so it reads like a real debrief, not a spreadsheet.
- Output in clean markdown.

Am I the only one who gets annoyed when I have to type now? Once you start dictating, the keyboard feels slow.

If your ChatGPT output sounds robotic, the fix isn’t stacking a bunch of adjectives like “natural,” “warm,” “organic,” and “authentic.”

Those are vibes, not instructions. The model can’t measure them.

This prompt does the job:

Rewrite this so it reads like one person explaining it to another. Write at an 8th grade reading level. Short sentences. No filler. Cut any phrase I wouldn't say out loud. Keep the meaning, lose the performance.
[paste text]

Why it works:

2 constraints doing 2 different jobs.

“Cut any phrase I wouldn’t say out loud” gives the model a test it can apply to every sentence.

Would a person say this?

No? Cut it.

That catches filler transitions (“furthermore,” “it’s worth noting”), hedging stacks (“could potentially,” “might arguably”), and the performative phrasing nobody uses in real life.

“Write at an 8th grade reading level” catches a different problem: word choice. It kills words like “utilize,” “facilitate,” and “leverage” that nobody uses in conversation either.

Simple words sound human. Complex words sound like a machine trying to impress you. Or foreigners who don’t understand the nuances of the native language.

You don’t need a complicated setup for this. You need 2 constraints that force the model to evaluate its own output.

One Prompt, One Full Animated Website

I went through a ton of website prompts, tested what worked, threw out what didn't, and combined the best parts into one prompt.

You paste it into Claude, ChatGPT, or whatever model you use. It asks you 6 questions about your project, then one-shots a full animated website as a single HTML file. Responsive, real copy, scroll animations, the works.

Here's one I started with: promptteardown.com. I've built on it since, but the homepage took about 11 minutes to get going.

The One Shot Website Prompt:

You are a frontend developer building a complete, production-ready single-page website.

Before writing any code, ask me these questions one at a time. Wait for my answers before proceeding:

1. What is this website for? (portfolio, business, landing page, event, restaurant, personal blog, etc.)
2. Pick a style:
   - Minimal and clean
   - Bold and dark
   - Warm and elegant
   - Editorial and sharp
   - Brutalist
   - Playful and colorful
3. Light mode or dark mode?
4. What's your brand color? (say a color name like "blue" or "forest green." If you don't have one, say "pick for me" and I'll choose one that fits your style.)
5. Tell me about your business or project:
   - What do you do?
   - Who is it for?
   - What's the goal of this website? (get bookings, sell a product, show off your work, etc.)
   - What makes you different from competitors?
   I'll use your answers to write all the copy.
6. What sections do you need? (hero, about, services, portfolio, testimonials, pricing, contact, FAQ, etc. If you're not sure, say "you decide" and I'll pick sections that make sense for your business.)
7. (Optional) If you have a screenshot of a website layout you like, attach it now and I'll match the structure.

After I answer, build the entire website as a single index.html file with these rules:

Structure and styling

- All CSS inline in a <style> tag. All JS inline in a <script> tag.
- Responsive at 375px, 768px, and 1440px.
- Build a cohesive color system from my brand color and mode. For light mode: light neutral background, dark text, brand color for accents and CTAs. For dark mode: dark background, light text, brand color for accents and CTAs. Generate a darker shade and a lighter tint of the brand color automatically.
- If the user's chosen color clashes with their chosen mode, adjust the shade so it works. Don't use a color that makes text unreadable.
- Modern CSS: flexbox and grid. No frameworks.
- Google Fonts loaded via CDN.
- Include a favicon emoji that fits the site.
- Write real, specific copy based on the business description. No lorem ipsum. No generic placeholder text. Every headline and paragraph should sound like it was written for this specific business.
- The site should look like a real website, not a template. Whitespace, typography hierarchy, and visual rhythm matter.

Font pairing (match to style automatically)

- Minimal and clean: Inter + Inter
- Bold and dark: Space Grotesk + Inter
- Warm and elegant: Playfair Display + Lato
- Editorial and sharp: Sora + Source Sans 3
- Brutalist: Space Mono + Space Grotesk
- Playful and colorful: Poppins + Nunito

Animations

- Load GSAP and ScrollTrigger via CDN.
- Every section fades up from 30px below with a 0.6s duration as the user scrolls into it.
- Cards, list items, and grid children stagger in with a 0.1s delay between each.
- Hero headline and subheadline fade in on page load with a slight upward motion.
- Keep all animations subtle. Nothing should bounce, spin, or overshoot.

Output the complete index.html file and nothing else. No explanations before or after the code.

Why This Prompt Works

This one makes the model gather context first. It asks your style, your color, your audience, and your business before it writes a single line of code. That's why the output actually fits your project instead of looking like a generic template.

How to Deploy It for Free in 10 Seconds

1. Save the output as index.html.
2. Go to app.netlify.com/drop.
3. Drag the file in.
4. Done. Live URL, free, no account needed.

Want to Add More Pages After?

Once your site is live, go back to the same conversation and say "now add an about page and a contact page in the same style." It'll build them matching the same design, fonts, and colors. Drag the folder into Netlify instead of a single file. Same process.

What's the best site you've built with a prompt? Curious what people are making.

You're trying to eat healthy. Maybe you're cutting weight, maybe you're building muscle, maybe you just want to stop eating garbage.

Either way, you know what happens.

You open the fridge. Stare at it. Close it. Google "healthy dinner ideas." Get a recipe that needs 14 ingredients you don't have.

Give up. Order food.

Or you ask ChatGPT to make you a meal plan, and it gives you a 45-minute salmon quinoa bowl for a Tuesday night when you have chicken thighs and rice.

A real nutritionist would ask you what your goals are, what you actually have in the kitchen, and how much time you feel like spending.

This prompt does the same thing.

I want you to create a recipe for me. Ask me these questions one 
at a time and wait for my answer before moving on:

1. Meal type (breakfast, lunch, or dinner)
2. What ingredients do you already have? (list what's in your 
   fridge and pantry right now, or say "anything" if you're 
   open to shopping)
3. Height and weight
4. Age and sex
5. Fitness goal (fat loss, muscle gain, maintenance, or something 
   else)
6. Allergies (or "none")
7. Strong dislikes (or "none")
8. Cuisine. Some examples: Chinese, Greek, Persian, Korean, 
   Japanese, Mexican, Italian, Indian, Thai, American, 
   Mediterranean, barbecue, comfort food, street food. Pick one 
   of these or tell me something else.
9. How much time and effort do you want to spend? (quick and easy, 
   moderate, or I have time to cook something involved)

Before generating anything, sanity check my fitness goal. If it's 
dangerous, unrealistic, or implies a crash diet, push back. 

Explain why in 1-2 sentences, suggest a safer alternative, and ask if I want to continue with the revised goal.

Build the recipe around the ingredients I listed. If I'm missing 
something small (a spice, a sauce, oil), that's fine. But don't 
build a recipe that needs a grocery run unless I said "anything."

Allergies and dislikes are both dealbreakers. Treat them the same. 
If I say "no coconut," that means no coconut milk, no coconut oil, 
no coconut cream. If I say "no soy," that means no soy sauce, no 
tofu, no edamame. 

Think about every form that ingredient shows up in and cut all of them. Don't suggest "just leave it out" or mark anything as optional. The recipe has to work without these ingredients from the start.

Match complexity to my effort level:
- Quick and easy: under 15 minutes, 5 ingredients or fewer, 
  minimal cleanup
- Moderate: under 30 minutes, up to 10 ingredients
- Involved: no time limit, full recipe

Then create one recipe that hits my macro targets for that meal and matches the cuisine. Include ingredients with quantities, steps, prep time, and a macro breakdown (calories, protein, carbs, fat).

What's actually going on here:

The ingredients question is what makes this usable on a Tuesday night. Most recipe prompts spit out something that sounds great, and then you realize you need 6 things you don't have. This one works with what you already have in your kitchen.

The goal check matters too.

Without it, the model will happily plan meals around "eat 500 calories a day," as if that's a normal request. It pushes back before it cooks.

You say "no coconut" and somehow coconut milk ends up in the recipe. You say "no dairy" and ghee sneaks in. That's because the model only checks the exact word, not every form it comes in. This rule fixes that.

And the effort question keeps it honest. You want quick and easy Tuesday night eggs, not a brunch spread with homemade hollandaise.

This works beyond recipes.

2 things make any prompt better:

• Tell the model to push back when your input is bad
• Ask what you're working with before it starts building

---

What's your go-to lazy dinner when you don't feel like cooking but you're trying to eat clean? I need new ideas.

I see dozens of prompts in this sub. A lot of them do the job.

But there are a few things I almost never see people do, and when you add them, the output changes completely.

No personas. No 12-step templates. Just lines you add to what you're already doing.

---

1. Tell it to push back on you before it helps you.

What people type:

I keep procrastinating on important tasks. Give me a productivity system.

You get a morning routine with 6 steps, a Pomodoro timer, and a journal prompt. You try it for 2 days, and you're back to doom scrolling.

What to type instead:

I keep procrastinating on important tasks. Before you give me a solution, red team my assumption. 

What if procrastination isn't the real problem? Push back on how I'm framing this and ask me questions until we find what's actually going on.

What changes: instead of handing you another system you won't follow, it starts asking what specifically you're avoiding.

Maybe it's not all your tasks. Maybe it's the ones with no clear next step. Now you're fixing the actual problem instead of collecting another productivity hack you'll forget about by Thursday.

---

2. Ask it to rip apart its own work.

Seems like everyone's applying for jobs right now. Most people paste a job description and say "write me a cover letter."

The model gives you something that sounds professional. You send it. It never makes it past the ATS because it's full of generic filler and misses the keywords the system is scanning for.

What to add after any first draft:

Now rip this apart. Be brutally honest. What's the weakest line? What would a hiring manager roll their eyes at? Does this match the keywords in the job posting or did you just write something that sounds good? Pressure test every sentence.

What changes: it catches the stuff you miss when you're reading your own work.

It'll tell you that "passionate team player with a track record of driving results" says nothing and won't pass ATS filters.

Then it asks you:

• What results?
• How much revenue?
• How many people did you manage?
• What changed because you were there?

It takes your generic lines and makes you fill in the specifics that actually get you past the scanner and in front of a human.

---

3. Ask for 2 versions at different tones.

Your landlord hasn't fixed a leaking faucet in your apartment for 3 weeks. You need to send a message that gets results without torching the relationship.

What people type:

Write a message to my landlord about a repair that hasn't been done.

What to type instead:

My landlord hasn't fixed a leaking faucet in my apartment for 3 weeks. I've asked once already over text and got no response. Write me a follow-up message.

Version A: direct, firm, and references my rights as a tenant. Mention that I've documented the issue with photos and dates and that I expect a response within 48 hours.

Version B: friendly but makes it clear this needs to happen this week. Keep it neighborly but don't let them off the hook. Mention that I'm happy to work around their schedule but the leak is getting worse.

What changes: you take the firm language and the tenant rights from Version A, then soften the delivery with the tone from Version B. Mix and match until it sounds like you.

Faster than rewriting the same message 3 times because you can't tell if you're being too nice or too harsh.

Works for emails to coworkers, messages to clients, anything where tone matters.

---

4. Ask for a plan so small you can't say no.

What people type:

Give me a workout plan. I'm 31, haven't worked out in over a year.

They get a 5-day split with warm-ups, cooldowns, and progressive overload. They do Monday and Tuesday. By Wednesday they're tired and it's over.

What to type instead:

I'm 31, haven't worked out in over a year. Don't give me a full program. Give me a plan so small I'd feel stupid not doing it. One thing I can do every morning for 2 minutes. Just the starting point, nothing else.

What changes: you're clamping the output. Without that line, the model gives you a full 5-day program because it thinks that's what you need.

But the right answer doesn't matter if you quit on Wednesday.

Instead of a full program, you get "do 10 pushups after your morning coffee." Nothing to quit.

Once that sticks, go back and ask for the next step. It'll add one thing.

That's how you build a routine without the model vomiting a full program at you on day 1.

---

5. Ask it what's in your blind spot.

What people type:

Should I go back to school for a second degree? Here's my situation. [details]

The model glazes you with a confident 5-paragraph yes. You feel good about it. That's the problem.

What to add:

Now be my devil's advocate. Based on everything I told you, what's in my blind spot? What's the biggest thing I might be getting wrong? Where does this fall apart? Be brutally honest, don't glaze me.

What changes: It brings up 2 years of lost income, not just tuition. Opportunity cost you hadn't considered. Trade-offs that actually matter.

Went from telling you what you wanted to hear to actually being straight with you.

Same model. One extra line. And now you're making the decision with the full picture, not just the side that feels good.

---

None of these are frameworks. None of them need a persona. They're just questions most people don't think to ask.

I'm curious what you guys do. What's one line you've added to a prompt that actually got you better results?