If you're out of ideas on what to try, here's a shelf full of tried-and-tested prescriptions. Copy them, swap the [BRACKETED] parts for your own, and paste them into any AI app. Most of these will still work 3 years from now.
These prescriptions work in Midjourney, ChatGPT / Nano Banana, Flux, and Ideogram. Swap the [BRACKETED] parts for your own.
Create a portrait of a [AGE]-year-old [MAN/WOMAN], [OCCUPATION]. Natural light, neutral background, photo style.
Photorealistic product photo: [PRODUCT NAME], clean white background, soft shadow, slight top-down angle, studio lighting, 4K detail.
Hand-drawn, minimalist sketchbook illustration: [WHAT SHOULD BE IN IT]. Thin black ink lines, a few pastel splashes, white background, loose artistic style.
Ad poster for an A/B test. Product: [PRODUCT]. Main message in large letters: "[SLOGAN]". Style: modern, clean, [COLOR SCHEME]. Small CTA button at the bottom: "[BUTTON TEXT]". The text must be SHARP AND READABLE.
The same character in 4 different poses in one image: [CHARACTER DESCRIPTION: hair, clothes, build, age]. 1) standing and smiling, 2) sitting at a laptop, 3) waving, 4) thinking. Consistent style, lighting, facial features.
Take this image and change the mood: make it [rainy / sunset / early-morning fog / neon night]. Keep the character, composition, and style — only the light and weather should change.
Create a 6-image moodboard for the following brand: [BRAND + 1-sentence description]. Target audience: [WHO]. Feel: [3 adjectives]. Include 1 portrait, 1 close-up product shot, 1 landscape, 1 texture, 1 typography detail, 1 abstract shot. Unified color palette.
Transform this photo into [Studio Ghibli / Pixar 3D / 90s anime / watercolor] style. Keep the facial features recognizable and render the background with atmosphere. Don't alter the pose.
Storyboard, 2x2 layout, 4 panels. Story: [3-sentence scene]. Main character: [DESCRIPTION]. Add a short caption below each panel. Style: thin ink + muted colors, comic-book feel.
In Suno, put the description in the style field and the lyrics separately. These prescriptions use exactly that structure.
acoustic guitar, soft female vocals, morning coffee mood, warm, slow tempo, english
[Verse] Happy birthday, [NAME] Today you're the star of the show The cake is yours, and so is the smile [Chorus] Long live [NAME], long may you shine We're all here celebrating with you today STYLE: upbeat pop, cheerful, acoustic + light drums, english, 90 bpm
instrumental lofi hip hop, no vocals, rainy window mood, warm jazz piano, subtle vinyl crackle, 70 bpm
LYRICS: [Verse] 9am, coffee in hand / [COMPANY NAME] team, everyone's at their post [Chorus] We are [COMPANY NAME] / One family, one team, one vision STYLE: epic anthem, rock, choir backing vocals, uplifting, english, 120 bpm
Cross between [bossa nova] and [80s synthwave], female vocals, night city vibe, mysterious, english lyrics about [TOPIC], 100 bpm
short intro jingle, 15 seconds, instrumental, energetic, brand-friendly, ends on a clean hit, modern electronic + acoustic guitar
LYRICS: [full verse + chorus on a topic of your choice, at least 12 lines, verse/chorus/bridge marked] STYLE: indie folk with cinematic strings, male vocals, melancholic but hopeful, dynamic build from quiet intro to full band by 2:00, english
LYRICS: [16-line verse where you speak to yesterday's You, 4 rhyming couplets per quatrain] STYLE: boom bap hip hop, jazzy sample, dusty drums, confident male voice, english, 88 bpm
These architect-doctors design better on their own if you don't micromanage every detail. Describe the GOAL and the MOOD, not the technology.
One-page landing page for the following product: [1-sentence description]. Target audience: [WHO]. Include: a hero, 3 headline benefits, a short 3-step "how it works", and 1 CTA (email signup). Modern, clean, lots of white space.
Build a 1-page portfolio for a [OCCUPATION]. Sections: 2-sentence intro, 6 project cards (image + title + 1 line), about me, contact. Style: [e.g. minimal black-and-white typographic / warm pastel].
A [CUISINE] restaurant website. Include: hero with a reservation button, menu in 3 categories (starters, mains, desserts) each with 4 items with photo + price, address + opening hours + embedded Google Maps, a reservation form (name, date, party size).
A SaaS product marketing website. Product: [WHAT AND FOR WHOM]. Structure: hero with product video mockup + CTA, 3 main problems it solves, "how it works" with 4 screenshots, pricing table with 3 tiers, FAQ with 6 questions, footer. Design: trust-inspiring, slightly technical, with a [COLOR] accent.
Build a simple internal tool: there's a form with [FIELDS], submitted data appears in a table below, it can be filtered by [WHAT], and there's a CSV export button. Save to local storage, no backend needed.
Build a [PRICE / SAVINGS / LOAN / CALORIE] calculator. Inputs: [FIELDS with a slider or input]. Calculate live on every change. Show the result visually too (card, progress bar, mini chart). Include a "share link" button that encodes the inputs into a URL.
Build a [WHAT]-app. Pages: public landing page, /app dashboard, /app/[items] list, /app/[items]/[id] details, /settings. Login (email + password). Everyone should only see their own data. Should look good on mobile too. Design: [MOOD].
This is my website: [URL or screenshot]. Target audience: [WHO]. Main problem right now: [WHAT'S WRONG]. Redesign it: bring in a new mood, improve the hierarchy, reduce cognitive load. First describe your decisions IN TEXT in 5 points, then build it.
The most everyday use case. The trick: always say WHO you are, WHO the other person is, and WHAT the goal is.
Shorten the following text by half while keeping the essence and tone: [TEXT HERE]
Rewrite this in a more polite, slightly more formal tone, but don't make it sound fake: [TEXT HERE]
Fix the grammar and punctuation and make the sentence structure more natural. Don't rewrite the content, just polish it: [TEXT HERE]
Write an email to [WHOM] politely declining [WHAT]. Reasoning: [1 line]. Keep it short, warm in tone, and leave the door open for later. Signature: [NAME].
My colleague: [ROLE]. Problem: [WHAT HAPPENED specifically]. Write a 4-6 sentence message to prepare for a 1:1 — it should address the specific behavior, not the person, and include a question too. Avoid passive-aggressive phrasing.
Write a quote email. I [WHAT I DO], client is [WHO], project: [1 sentence]. Packages: [Basic $X / Plus $Y / Premium $Z], each with 3 line items. End with 2 next steps + a response deadline. Friendly-professional.
Customer complaint: [TEXT PASTED HERE]. Write 3 response versions: 1) empathetic + quick solution offer, 2) factual + compensation, 3) escalate to a manager. Add 1 sentence under each on when to use it.
Create a 4-part onboarding email series for new subscribers. Product: [WHAT]. Target audience: [WHO]. E1: welcome + quick win, E2: deeper use case, E3: social proof, E4: soft CTA to purchase. For each, include subject + short body + P.S.
Here are 3 emails I wrote: [PASTED HERE]. Analyze my style: sentence length, characteristic phrases, tone, typical structure. Then write a new email about [TOPIC] in exactly this style. Don't compliment me, just do the work.
ChatGPT Tasks, Gemini Scheduled Actions, n8n / Make workflows. Describe when + what + where. If the doctor doesn't know how: ask it for a JSON or a Make blueprint description.
Every morning at 7:30, send me a 5-point summary of yesterday's most important [TOPIC] news. Sources only, no fluff. Don't compliment me, don't ask follow-up questions.
Every Friday at 5:00pm, ask me 3 questions: 1) What did I accomplish this week? 2) What went wrong? 3) What's next week's main focus? From my answers, write a 5-line summary and save it in the conversation.
Every day at 8:00am, send a short, funny message reminding me to take my vitamins. Keep it varied, don't repeat yourself — use at least 30 different messages in rotation.
Every Monday at 9:00am, check these 3 competitor websites: [URLS]. Summarize what changed over the past week (new product, new price, new messaging). If nothing changed, say that too.
Help me build an n8n workflow. Goal: [WHAT SHOULD HAPPEN]. Trigger: [WHEN]. Steps I can see: [LIST]. Describe node by node which nodes to add, with what parameters, and where an API key is needed. At the end, give me a JSON I can import.
When a new email arrives with [LABEL], check whether it contains a date/time/meeting. If yes: create a Google Calendar event (title = email subject, description = link to the email, attendees = sender). If unsure, follow up with a Telegram message.
Every day at 6:00am: 1) pull yesterday's data from [SOURCE], 2) calculate [METRICS], 3) compare against the previous 7-day average, 4) if anything deviates by ±20%, flag it with a red/green arrow, 5) send it to Slack in the #daily channel in markdown format.
Every Friday: 1) find 5 recent articles on [TOPIC] from the last 7 days, 2) extract 1 takeaway from each, 3) build 1 LinkedIn post draft from this (hook + 3 points + question), 4) add it to the "Draft posts" database in Notion with status "review".
In video, camera movement and second-by-second timing matter most. Describe: WHAT's in frame, WHAT it's doing, HOW the camera moves.
Close-up shot of [OBJECT] rotating slowly on a matte black surface, soft studio lighting, camera fixed, 5 seconds, cinematic.
Slow motion pouring of hot coffee into a white ceramic cup, morning window light, steam rising, shallow depth of field, 5 seconds.
A [AGE]-year-old [PERSON] sitting in a [ENVIRONMENT], looking at the camera and smiling. Natural light, medium shot, subtle camera drift forward, 6 seconds.
Product ad shot: [PRODUCT] on a modern kitchen counter, hand enters frame from the right and picks it up, camera follows in a smooth arc, warm golden hour light through window, 8 seconds, ends on the product in focus.
Two people at a café table, [PERSON A DESCRIPTION] on the left listening, [PERSON B DESCRIPTION] on the right speaking with hand gestures. Camera slowly dollies from wide to over-the-shoulder on person A. Warm afternoon light, 8 seconds.
Start from the uploaded image. Animate: [WHAT SHOULD MOVE] — with [CAMERA MOVEMENT: slow zoom in / pan left / static]. Keep character and style identical. 5 seconds, subtle motion only.
Cinematic sequence, 3 shots × 4 sec each: 1) wide establishing shot of [LOCATION] at dawn, 2) medium shot of [CHARACTER] doing [ACTION], 3) extreme close-up of [DETAIL] with a subtle reveal. Consistent color grade: [teal & orange / muted pastel]. No music, no text.
60-second product video plan. Product: [WHAT]. Audience: [WHO]. Vibe: [3 adjectives]. 1) Describe 6 scenes, each 10 sec, each with shot type + camera move + main action. 2) Write the voiceover script. 3) Note which scene should be generated with which AI video tool, and why.
These days you no longer write "build me feature X". You describe WHAT THE PROBLEM IS, WHAT YOU SEE, and WHAT GOOD WOULD LOOK LIKE. The coding doctor often comes up with a better solution than what you had in mind.
This project: [1 sentence, what it does]. Stack used: [language/framework]. Review the files and summarize in 5 points how it's structured before changing anything. Don't code yet.
PROBLEM: when I [DO WHAT], then [WHAT HAPPENS] — but [WHAT SHOULD HAPPEN INSTEAD]. What I've already ruled out: [WHAT I TRIED]. Files that seem relevant: [PATHS or "not sure, find it"]. Diagnose first — list 3 possible causes, then suggest the most likely one and WHY. Only fix it after that.
As a user, I want to be able to [DO WHAT], so that [WHY]. Don't ask me what database table is needed or where the button should go — you're the expert, suggest it yourself. First describe in 5 points what you're going to do, wait for me to say "go", then start.
This file / component has gotten too complex: [PATH]. Goal: [more readable / more testable / faster / less duplication]. Constraint: the public API / component props must NOT change. First describe what you're going to restructure and why. Ask if anything's unclear.
New feature: [WHAT]. First write [unit / integration] tests describing the expected behavior including edge cases (at least 5 cases). RUN them too — the tests should fail right now. Only implement the code after that, until all tests pass.
My idea was to [SOLUTION I HAD IN MIND]. The actual goal I want to achieve: [REAL GOAL]. Before you build it: tell me if this is the best approach. If there are 1-2 better approaches, list them with pros/cons, then recommend the best one. I'll choose.
Task: [BIG CHANGE in one sentence]. Step 1: map out the affected files and describe what connects to what. Step 2: give 2 possible solution plans with pros/cons. Step 3: wait for feedback on which one to choose. Step 4: break it into small, reviewable commits and run tests separately for each. For now, only do steps 1 and 2.
There was a production incident: [DESCRIPTION + LOG]. I've already fixed it like this: [FIX]. I'd like: 1) Describe the root cause (not the symptom). 2) What assertion / test / monitoring would have caught this earlier? 3) What 3 code patterns exist in the project that could cause a similar bug elsewhere — find those spots.
The doctor isn't an expert, a friend, or a therapist. But it's a shamelessly good sounding board — if you ask it good questions to reflect back at you.
I'll describe a problem, DON'T solve it. Just ask me 5 short questions that help me see it more clearly. At the end, summarize what you understood. Problem: [TEXT].
I'm facing a decision: [A or B]. List 5 arguments for each side. Then ask me 3 things I should clarify before deciding.
Give me 20 different ideas for the following problem: [WHAT]. Don't explain them, just list them. Include 5 obvious ones, 10 creative ones, and 5 completely absurd ones. Then mark the 3 you think are best with a * and say why.
Analyze the following decision using the Six Thinking Hats method: [DECISION]. White: facts. Red: feelings. Black: dangers. Yellow: benefits. Green: creative alternatives. Blue: summary + next step.
I have a conflict with [WHOM] about: [WHAT]. 1) Describe how a lawyer would argue FOR ME. 2) Describe how a lawyer would argue FOR THE OTHER SIDE — take their position seriously. 3) What would a neutral judge ask? 4) What would be a solution acceptable to both of us?
Problem: [WHAT'S HAPPENING]. Let's go through the 5 Whys method. Ask "why?" 5 times in a row to my answers, until we reach the real root cause. Then suggest 1 concrete experiment I can test it with.
Imagine it's 1 year from now and everything went well. Ask me 10 short questions about what this future-Me is like (work, relationships, health, money, learning). From my answers, build a 1-year plan draft split into 4 quarters, with 1 main focus + 3 milestones per quarter.
I have a recurring thought: "[NEGATIVE THOUGHT]". 1) Describe what cognitive distortions you see in it (max 3). 2) Reframe it in 3 different, more realistic ways. 3) Give 1 small behavioral experiment for the week that would test whether the thought is true. Don't be a therapist, be a practical companion.
The best prompt is the one you've rewritten three times already. Tweak it, experiment, compare two doctors' answers to the same question. That's what AI likes best: when you talk with it, not order it around.