r/ChatGPTPromptGenius • • 22h ago

Technique A tip to make AI useful without adding another new tool

0 Upvotes

This is a generic tip for starters, but it has helped get me some good initial results.

When experimenting with AI at work, try this to improve yours:

  1. Pick a task you repeat every week.
  2. Know what successful looks like and write it down.
  3. Enter the details of your tasks to AI and then ask it to suggest a simpler process.
  4. Test the output against your actual requirements and what you wrote down as success.
  5. Keep what works and improve what doesn't.

Here's a prompt that I've used that you can adapt:

"I'm trying to improve this recurring work task: [describe task]. My goal is [desired result]. My current process is [steps]. Identify three ways to reduce unnecessary effort without compromising quality. Suggest a practical workflow and explain what a human should still review."

My first post in the group, happy to share more and learn from others.

Disclosure: I'm affiliated with LearnVironment and happy to share the following free resource:
Free Skill Growth Starter Guide | LearnVironment


r/ChatGPTPromptGenius • • 17h ago

Full Prompt I shot a 55-second AI short film — 12 shots, zero reshoots. Full workflow breakdown (all anchor prompts included)

4 Upvotes

Follow-up to my character sheet post from two days ago. A few of you asked how the sheet actually holds up across a whole film, and the comments about fixed seeds and adding jacket texture / eye shape to the "never change" list were genuinely useful — so here's the full breakdown of the finished film.

The film: The Last Lighthouse (55s, vertical). A keeper of 41 years works the last night before his lighthouse goes automatic. A storm kills the main light, his daughter's boat is out in it, and the backup lamp only turns by hand. No dialogue — subtitles and sound carry it. Watch it here first if you want to judge the result before the method: https://youtube.com/shorts/mT4rlyXJbD8

The core method: three anchors, pasted verbatim into every single prompt.

Style anchor (in all 12 shots, never edited):

cinematic photorealism, muted teal-and-amber grade, soft volumetric light, vertical 9:16

Character anchors (same idea — description + outfit + one signature prop):

Elias: a 68-year-old lighthouse keeper, weathered face, short white beard, deep-set kind eyes, oil-yellow fisherman's raincoat, grey wool cap, brass lantern Mara: a 32-year-old fisherwoman, dark brown hair in a braid, freckles, determined expression, dark green waterproof jacket, red scarf

Every keyframe prompt = style anchor + character anchor + one sentence of shot content. Nothing fancy — the discipline is in never retyping or "improving" the anchors mid-project.

Production order matters more than prompt tricks:

  1. Character reference portraits first. If the face isn't right here, nothing downstream saves you.
  2. Generate the hardest shot first. For me that was S07, the climax: Elias cranking the backup lamp in the storm. Full keyframe prompt:

    [style anchor] + [Elias anchor] + top of the lighthouse at night, he turns a heavy brass crank with his whole body, coat whipping in the wind, rain streaking diagonally If S07 had failed, the film design would have changed — better to learn that in hour one than after 11 finished shots.

  3. Remaining keyframes in a batch, checking each against the reference (face, outfit, prop).
  4. Image-to-video per shot, motion prompt kept to one simple instruction per shot ("slow push-in", "static, rain streaking"). Complex motion asks are where generations go to die.
  5. Assembly: hard cuts, subtitles, ambient sound only (wind, mechanism clicks, morning birds), loudness normalized to −14 LUFS. No music — the storm is the score.

The result, honestly: all 12 shots passed on the first generation. Zero rejected clips. Two flaws I'll admit before you spot them: in S07 he turns a brass wheel, not the crank I asked for (the motion still reads correctly, so I kept it), and his cap drifts slightly from the reference in two shots. Neither breaks character continuity at viewing size, but they're there.

Shot list, for anyone who wants to steal the structure: stormy lighthouse wide (5s) → packing a suitcase (5s) → radio close-up (4s) → the light dies (4s) → the boat spotted (5s) → lantern grab, close-up (3s) → the crank (6s) → beam returns (5s) → boat turns home (5s) → exhausted smile (4s) → daughter climbs the steps at dawn with two teas (5s) → father and daughter on the steps, lamp fading behind them (5s).

What breaks first in your projects — faces drifting, or props/hands? For me props are now the #1 failure mode, ahead of faces.

Disclosure: I sell a playbook that documents this whole workflow with all the templates ($24) — everything essential is in this post for free, the paid version just saves you assembling it yourself: https://www.creem.io/product/prod_5D47vS65nFsqtTf9b8untx


r/ChatGPTPromptGenius • • 17h ago

Full Prompt Paste two insurance policies into ChatGPT and it fills the gaps with what policies usually say, not what yours says. Make it quote the exact line for every answer, and turn every blank into a question for the insurer

24 Upvotes

the problem with "which of these two policies is better?" is that chatgpt has read thousands of policies. when yours doesn't mention something, it fills in the usual answer and you can't tell which parts came from your document and which came from its memory. that's how you end up assuming water damage or a waiting period is covered when the policy never said so.

this chain fixes that by building the checklist before it reads anything, making it quote the line for every answer, and writing "not stated" when the line isn't there. works for health, home, car, travel, pet, whatever. also works for phone plans or job offers if you change the wording.

first upload both documents (PDF or pasted text) with a message like "two policies, A and B. don't summarize yet". then run these in order:

Step 1, the checklist:

I'm comparing {{insurance type}} policies. My situation: {{situation}}. Before reading the documents, list the 10 things that decide what I'd actually get paid in a claim for someone like me, like the deductible, coverage limits, exclusions, waiting periods, how claims are paid, and what can change at renewal. Put them in a table with empty columns for Policy A and Policy B.

Step 2, policy A:

Fill the Policy A column using only what document A says. For every cell, quote the exact sentence it comes from and where it is in the document. If the document doesn't say, write "not stated". Don't use what policies like this usually include.

Step 3, policy B:

Do the same for Policy B, with the same rules. Quote the sentence for every cell, or write "not stated".

Step 4, the claims test:

Make up 3 realistic claims for my situation, one small, one large, one in a gray area. Walk each one through both policies using only the quoted lines and say what each one would pay. Where the answer depends on a "not stated" cell, say so instead of guessing.

Step 5, the questions:

List every "not stated" cell and every gray area as a question I can email each insurer. Word each one so the answer has to be yes, no, or a number. Then tell me which policy looks better for my situation based only on what's written, and what would flip that answer.

why it works:

  • step 1 builds the checklist before it sees the documents, so the marketing summary at the top of each policy doesn't decide what gets compared
  • "quote the exact sentence" means you can check every cell yourself in 10 seconds
  • "not stated" is the important bit. the gaps are where the bad surprises are, and step 5 turns them into a written answer from the insurer instead of a guess

don't treat the result as advice, treat it as homework done for you. the insurer's written answer is what counts.

i build AI Toolbox, a browser extension for ChatGPT, Claude, Gemini and Grok. you can save these 5 as a chain: type .. in the chat box, pick it, fill in {{insurance type}} and {{situation}} once, and the steps send one after another, each waiting for the reply. the free plan includes 2 chains.


r/ChatGPTPromptGenius • • 21h ago

Technique Very simply improving your weekly tasks

3 Upvotes

This is a generic tip for starters, but it has helped get me some good initial results.

When experimenting with AI at work, try this to improve yours:

  1. Pick a task you repeat every week.
  2. Know what successful looks like and write it down.
  3. Enter the details of your tasks to AI and then ask it to suggest a simpler process.
  4. Test the output against your actual requirements and what you wrote down as success.
  5. Keep what works and improve what doesn't.

Here's a prompt that I've used that you can adapt:

"I'm trying to improve this recurring work task: [describe task]. My goal is [desired result]. My current process is [steps]. Identify three ways to reduce unnecessary effort without compromising quality. Suggest a practical workflow and explain what a human should still review."

My first post in the group, happy to share more and learn from others.

Disclosure: I'm affiliated with LearnVironment and happy to share the following free resource:
Free Skill Growth Starter Guide | LearnVironment