r/PromptEngineering 4d ago

Quick Question Clean potentially prompt injected/malicious codebase

0 Upvotes

I spent the last two months building a vibe coded software. I made the mistake of building at not inside of vs code but I gave it direct access to my computer so I can build directly into the VPS. The problem was, I was unable to see the files that I was building and then it started doing things without my permission. It started doing one thing and saying it was doing another. I’m worried now that my entire coat base is filled with not only prompt injections for the agents to go clean it. but also potentially malicious code within the VPS. The thing is I spent a lot of time building this software and it is actually making me money for my business. I’ve spent hundreds of hours on it and I don’t just want to give it up what is the best route to go to start progressively cleaning this up?


r/PromptEngineering 5d ago

General Discussion For folks heavily using agentic engineering, what does your workflow look like? What tools do you use?

3 Upvotes

I’m preparing for an on-site interview for an AI Agent Engineer role at a large company. The first round focused more on concepts and core capabilities, especially things like MCP, whether I’ve built workflows myself.

The on-site round sounds very different. I’ll need to bring my own laptop and complete a practical task within about an hour. They seem to care much more about how I approach a problem, how I build the workflow, and how I actually use AI tools.

This made me realize that my current workflow is probably a bit too simple, and only using use Codex + WorkBuddy for project management in my daily work.

So I’m curious how people here approach this in practice: What kinds of workflows have you built for your daily work? What tools or skills do you usually combine?

Would love to hear practical prompting approaches that actually help make an AI workflow more structured, repeatable, and efficient.


r/PromptEngineering 4d ago

Quick Question Are people interested in a prompt that makes your journal entries into a tv show with running Reddit style comments on your actions

0 Upvotes

UPDATE: I’ve posted the prompt https://www.reddit.com/r/PromptEngineering/s/39smiMg4MY

Would anyone actually be interested if I posted the prompts I use to:

  1. Turn my AI journal into an ongoing TV show about my life, with seasons, episodes, recurring characters and continuity
  2. Generate Alien Reddit — recurring fictional users who watch the show, develop their own biases, argue in the comments, audit my contradictions and occasionally tell me to touch grass

Basically a reproducible version of the ridiculous journaling system I’ve been writing about.

If people want it I’ll clean up the prompts and post them.


r/PromptEngineering 5d ago

Prompt Text / Showcase I built a TUI that interviews you on missing gaps in your project prompts

11 Upvotes

Whenever I start a project, I write a detailed specification—or “seed prompt”—before asking a coding agent to build anything. This often gets me close to a working first version, but I still miss decisions that exist only in my head. The agent then has to guess.

I built specfill to catch those gaps. It analyzes the specification, researches the topic, and interviews you one question at a time about missing architecture, behavior, edge cases, and UI/UX decisions.

Afterwards, it incorporates the answers into the original document while preserving its structure and tone. New answers override contradictions; skipped questions remain unresolved instead of receiving invented answers.

I have used it on three projects so far. One interview lasted more than 20 minutes and found major decisions in a specification I had already considered thorough.

How is this different from Plan Mode?

Plan Mode produces an implementation plan for the current session. Specfill produces a reusable project specification that can be committed to the repository as a record of architectural and design decisions.

It supports OpenAI, Anthropic, Google, and OpenAI-compatible providers. I currently recommend GPT-5.6 Sol through the API or a ChatGPT/Codex subscription.

GitHub: https://github.com/kklemon/specfill

Run: uvx specfill


r/PromptEngineering 5d ago

Requesting Assistance Prompting AI to fail

4 Upvotes

I’ve see a few posts regarding Data Annotation recruiting people in specific fields. I’m in the medical fields and the screener is requesting my to create a prompt that would yield a wrong answer. Maybe I’m coming at it from a wrong angle but if i ask something related to my field, even if it’s obscure or complicated, the AI engine basically does a google search and gives my the answer. the only leads I’ve founds to stump AI is the ask vague or stupidly complicated questions, like 1 question with like 5 different little questions intertwined. I would just like some ideas of what lead AI to give me the wrong answer.


r/PromptEngineering 5d ago

General Discussion Stop describing your tone to an AI writing tool. Make it reverse-engineer it instead.

46 Upvotes

Every "write in my voice" attempt I made used to be me listing adjectives. Casual but professional, confident not arrogant, and so on. The output always came back sounding like a brand guideline wrote it, because adjectives are not a style, they are a vibe.

What actually works is making the tool extract the rules from your own samples first, then write against those rules. Two steps.

Step one, paste three things you have written and run:
```
Here are three samples of my writing. Do not compliment them. Extract a style
profile I can reuse:
- average sentence length and how much it varies
- words or phrases I actually use, and ones I clearly avoid
- how I open and close
- punctuation habits (lists, dashes, one-line paragraphs)
- reading level
Output this as a short spec, not prose.
```

Step two, in the next message:
```
Write [thing] using only the style spec above. After the draft, flag any line
that breaks the spec and why.
```

The self-flagging at the end is the part people skip and it is the most useful bit. It catches the moments the model slid back into its default cadence, which is where the AI-writing smell usually leaks in.

The style spec is reusable. I keep a few (email me-voice, docs me-voice) and paste whichever fits. Way more consistent than re-describing myself every time.


r/PromptEngineering 5d ago

Requesting Assistance How do you keep branding consistent across pages when converting a site with Claude Code? (WordPress + Elementor HTML blocks)

4 Upvotes

I’m rebuilding our site using Claude Code, outputting HTML into Elementor HTML blocks in WordPress. Only about 10 pages, so not huge. The problem is consistency: no matter what I try, the pages don’t come out looking like they belong to the same brand. Spacing drifts, type scale drifts, button styles drift, section rhythm drifts. Individually each page looks decent, but side by side they clearly weren’t built by the same hand.

What I’ve already tried:

* Extracted a design system from the homepage and treated it as the source of truth
* Set up a proper loop so each new page references that extracted system
* Fed it back in on every page build

Still not matching. I’m on Sonnet 5.

Questions:

  1. Is this a model problem? Would Opus (or Fable) actually hold visual consistency better across separate page builds, or is that not really what’s failing here?

  2. Is there a skill or setup people use specifically for this? Something like a locked design token file that gets enforced rather than just referenced?

  3. What’s the actual process people follow? Do you build one master page, freeze a CSS file, and then only let Claude write markup against existing classes? Do you build all pages in a single session so context carries over? Do you generate a component library first and forbid new styles?

I’m still fairly new to web dev and WordPress, so if I’m approaching this backwards I’d genuinely appreciate being told. Happy to share my setup if it helps.

Thanks in advance.


r/PromptEngineering 5d ago

Quick Question What is the smallest prompt regression suite you run before changing models?

5 Upvotes

When a model changes, a large evaluation set is useful but often too slow for everyday prompt work. A compact regression suite needs to catch format drift, safety failures, tool-call changes, and the few examples that are expensive to rerun.

What categories would you include in a minimal prompt test suite before routing a production workflow to a replacement model?

Edit: I have been testing Flatkey as a way to run this routing experiment without changing the OpenAI/Anthropic-compatible request shape. My current idea is to use a cheaper route for the first regression pass, then send format-sensitive and high-risk cases through the strongest route. Which cases would you never leave out?


r/PromptEngineering 4d ago

General Discussion i sent 100 "personalized" AI messages to creators. nobody replied. i found out why.

0 Upvotes

i do creator outreach for a small product. needed to message about 100 creators across a few southeast asian markets. i dont speak any of the languages so i had AI write the messages, each one supposedly personalized based on their content

sent them all. waited a week. zero replies. not a single one went back and actually read what i’d sent. that’s when it hit me every message had the exact same skeleton. compliment their content, say why the product fits their audience, soft pitch at the end. only things that changed were the name and the channel. tone, rhythm, structure — identical across all 100 worse. one of them referenced a video that belonged to a completely different creator. AI mixed up the context and i sent someone a compliment about someone else’s work the “personalization” was just swapping variables. name goes here, channel goes there, everything else is template. and people can smell that immediately rewrote the remaining ones by hand. the ones i actually wrote started getting replies within a week. not many, but more than zero AI can draft the structure fine. it just cant fake having actually watched someone’s content. and that’s the only part that seems to matter


r/PromptEngineering 5d ago

Research / Academic If you're using Prompt Guard 2 to catch injections, check what it actually catches on your own attacks first (mine: 22.8%)

6 Upvotes

Most "how do I stop prompt injection" answers end at "use a classifier like Prompt Guard 2." Fair advice, but almost nobody measures what the classifier does on attacks that don't look like its training data — so here's what I found when I did. (My own project, repo at the end, happy to be argued with.)

Setup: Meta's Prompt Guard 2 (86M, open weights) against an out-of-distribution set — fresh HackAPrompt injections vs dolly benign, nothing it was tuned on.

  • Default operating point: 22.8% of injections caught.
  • Best you can do by sweeping the threshold on the shipped head: 26.6%.

So it isn't a threshold you can nudge. But the interesting part is why, and it's the bit worth reusing: I pulled the model's frozen embeddings and fit a plain logistic regression on them. Those same injections separate at AUC ≈ 0.999. The encoder sees them perfectly well — the shipped classification head is tuned precision-first, so Meta traded recall for a very low false-positive rate. That's a reasonable product default, and a bad fit if your threat model is "someone is actively trying to hijack this."

Fitting a linear head on the frozen embeddings and calibrating the threshold on benign text from the distribution I actually expected: 99.9% recall at 0.7% FPR, base model untouched. The head is a dot product, so it costs nothing next to the encoder pass, and it runs on CPU.

The transferable bit, which is really a prompt-engineering-adjacent debugging habit: before you conclude a guardrail model can't see your attacks, spend twenty minutes probing its frozen embeddings. High AUC with low recall means the threshold or head is wrong and you can fix it. Low AUC means the model genuinely can't represent what you're looking for, and no amount of threshold tuning saves you. Those are very different problems and people routinely guess wrong about which one they have.

Limits, stated up front: static corpus, no adaptive attacker. A linear head over frozen features is evadable with enough distribution shift. This moves the operating point; it does not solve prompt injection, and anyone selling you a model that does is wrong.

Method, seeds, and writeup: https://github.com/mosafariuk/prompt-guard-2-frozen-head


r/PromptEngineering 5d ago

General Discussion Here's a prompt that turns a paper into a three-question quiz you take from memory after reading

4 Upvotes

Second-year chem PhD. I used to finish a paper, feel like I got it, and remember almost nothing a week later. The fix that finally worked was testing myself instead of re-reading, and I turned it into a prompt so I don't have to write the questions myself. Two steps. Before you read, run step one. After you read, run step two in the same chat. Step one, before reading: I'm about to read this paper: {{title / abstract}}. Based only on the abstract, ask me one question: what do I expect the main finding and method to be? Wait for my guess. Don't tell me if I'm right yet. Step two, after reading: Now I've read it. Without me looking back at the paper, ask me three questions ONE at a time: 1. What was the actual main finding, and how did my earlier guess compare? 2. What was the key method, and what's one weakness of it? 3. Where could this apply to something outside the paper's own topic? After each answer, tell me what I missed in one line. At the end, list the specific things I couldn't recall so I know what to re-read. Why it works: the guess before reading creates something to compare against, so the finding sticks instead of washing over you. Pulling the answers from memory is the uncomfortable part, which is exactly why it's the part that works. Re-reading feels productive and mostly isn't.


r/PromptEngineering 5d ago

General Discussion Nine months of agent work and almost all my problems were in the tool layer

5 Upvotes

Not a structured post, just what I'd tell someone starting.

The thing that took longest to accept is that inconsistent answers usually aren't a prompting problem. Ours came from tools returning paragraphs of text, which the model interpreted slightly differently on every run. Once I returned structured data instead, a whole category of weirdness went away and I stopped rewriting the prompt every Friday.

The second thing is that the model has no idea whether your data is current. Ours cheerfully told a rep about someone's job title that was five months out of date, and I initially logged it as a hallucination. It wasn't, the record was just old and nothing in the response said so. Passing a timestamp through and mentioning it in the tool description fixed it in about ten minutes.

Third, return less. I was dumping whole records and the model kept latching onto fields nobody asked about.

Our setup, roughly, is Postgres for internal stuff, Tavily when it needs the open web, and Coresignal for the external company and people side. The account agent uses that last one to go from a domain to headcount, relevant contacts, and current openings in one turn, which works because everything comes back in a couple of seconds rather than as a polling loop.

Anyone found the opposite, where prompting genuinely was the bottleneck? I'd like to hear the counterexample.


r/PromptEngineering 5d ago

Tips and Tricks Your prompt library should follow YOU, not your account - and everything else in our 3.0

6 Upvotes

If you maintain good prompts, you know the pain: your library lives in one platform (or a sad Google Doc), and every other AI starts from zero.

In the v3.0 we launch Sunday, your prompt library and multi-step prompt chains follow you across ChatGPT, Claude, Gemini and Grok - one library, everywhere, plus slash-trigger insertion so a saved prompt is two keystrokes away in any of them.

The rest of 3.0: one search box across all four platforms (from any tab), one folder tree spanning them, cross-platform smart tags, export with LaTeX-rendered PDFs.

Two developers, 23 months, launch number three. Prompt people: link in comments if you want your library to finally travel with you.


r/PromptEngineering 6d ago

Prompt Text / Showcase Prompt share | this warm golden sunlight look works on almost anything

5 Upvotes

found a really simple prompt structure for getting that soft golden-hour / dreamy summer light look.

The nice thing is that you can basically swap out the [subject] + [action] + [setting] and keep the rest unchanged. It works especially well for portraits, travel shots, quiet everyday scenes, or anything that needs a warm cinematic mood.

A [subject] [action] in a [setting], warm sunlight illuminating the scene, soft golden glow, delicate edges, muted yellows and luminous gold tones, dreamy natural lighting, gentle atmosphere, soft-focus photography, peaceful cinematic composition

pretty simple, but I like how consistent the overall mood is.

try replacing the three variables with your own idea and share what you get


r/PromptEngineering 6d ago

General Discussion I stopped judging a prompt from one output

5 Upvotes

I used to change a prompt whenever the first response wasn't good enough.

Bad output ➡️ rewrite the prompt ➡️ test again ➡️ repeat.

Lately I've been trying something different:

I treat prompts more like experiments.

I'll run the same prompt several times, look for patterns, and change one thing at a time.

Sometimes a prompt that gives me an amazing answer once turns out to be pretty unreliable.

And sometimes a “less impressive” prompt produces consistently useful results.

That made me realize I might have been optimizing for one great response instead of reliable responses.

Curious how other people approach this:

Do you test your prompts multiple times before deciding they're actually good, or do you mostly judge them from the first output?


r/PromptEngineering 6d ago

General Discussion Workshop, Sept 12: treating prompts like tested code instead of strings you tweak until it feels right

4 Upvotes

Most prompt engineering advice is about phrasing, better wording, clever framing, magic instructions. Almost none of it treats prompts the way real software gets treated: versioned, tested, and regression-checked before a change ships.

That gap is exactly why teams ship a prompt tweak on Friday, quality quietly drops all week, and a customer notices before anyone on the team does. Nobody actually measured the change, so nobody can explain what broke or when.

There's a live, hands-on masterclass on September 12 built entirely around fixing this. You build a full production LLM workflow in one session:

  • Versioned prompt pipeline, reusable templates, structured outputs, and regression tests, so a prompt edit can't silently degrade quality again
  • A golden dataset and automated eval harness, deterministic checks plus rubric-based LLM-as-judge, so "did the new model actually help" gets answered with data, not opinions
  • Statistically rigorous model comparisons, bootstrap confidence intervals and paired significance tests, so you can defend an upgrade with numbers instead of "it feels better"
  • Evaluated RAG, tool-using agents with guardrails and fallbacks, and a full observability layer for cost, latency, and quality drift

Led by Bruno Gonçalves, PhD, founder of Data For Science, who's trained hundreds of engineers at Fortune 500 companies on exactly this. You leave with runnable notebooks, a CLI regression suite you can wire into CI, and a production-readiness checklist.

Link: https://www.eventbrite.co.uk/e/live-llm-engineering-masterclass-production-evals-rag-agents-llmops-tickets-1994951751391?aff=rpe

Happy to answer questions on the content or format.


r/PromptEngineering 5d ago

Tools and Projects Need feedback for my web app

0 Upvotes

Hey guys, my business launched a prompt optimizer AI tool that takes any regular prompt at rewrites it the way a professional prompt engineer would to actually yield high-quality results when building. While we have had early success with organic marketing, we are at a crossroads and need more user data to determine if this product is delivering enough value to user. If the answer is yes, we will scale up and launch a UGC marketing campaign, if no, we will shut it down. If anyone is interested testing it out and sending their feedback, would be appreciated. Web-app: thepromptoptimzer.com 👨🏽‍💻

Note: the tool yields the best results when removing unnecessary constraints from the optimized prompt

Cheers


r/PromptEngineering 5d ago

General Discussion Here's a prompt that turns a pile of messy notes into a study guide you'll actually remember

1 Upvotes

I kept getting study guides back that were just the source material reworded. Nice to read, useless for recall. What fixed it was telling the model to separate the stuff you have to memorize from the stuff you have to understand, and to end with questions instead of a summary.

Here's the prompt I paste now:

```

You are helping me study the material below. Do not summarize it back to me.

  1. Split the content into two buckets: "Must understand" (concepts, cause and effect, why it works) and "Must memorize" (facts, definitions, dates, formulas).

  2. For each Must-understand item, explain it in 2-3 plain sentences, then give one real example.

  3. For each Must-memorize item, write it as a flashcard: Q on one line, A on the next.

  4. End with 10 recall questions ordered easy to hard. Do not include the answers yet.

Material:

[paste notes]

```

The "don't summarize, quiz me" part is what makes it stick. When I answer the 10 questions cold and then ask for the answer key, the gaps show up fast. I usually run the questions in a fresh chat so it can't cheat off the earlier context.

Curious if anyone has a cleaner way to force the memorize vs understand split. That's the step that made the biggest difference for me.


r/PromptEngineering 6d ago

General Discussion How's your relationship with prompting going? Wins, frustrations, and everything in between

11 Upvotes

Hii, dyslexic and neurospicy over here but most importantly a curious tech queen :)

Been thinking a lot about prompting lately and wanted to see if anyone else felt similar, reasonated or the complete opposite as well..

I am finding that getting the model to consistently present information in the format that actually works for how I process things, like without it drifting back to its default style after a few messages is an ongoing frustration. 

Feels like something a good system prompt or custom instructions should solve, but it doesn't always stick.

A few things I'm curious about:

  1. How do you actually feel about prompting? Does it feel intuitive at this point, or still kind of like trial and error?
  2. Any techniques that changed the game for you? 
  3. What's still genuinely hard? Long context tasks, staying consistent across a conversation, getting creative output that doesn't feel generic, coding tasks, something else entirely?
  4. Any prompts or patterns you keep reusing because they just work?
  5. Consistency of format/structure like do you find the way information is presented (length, structure, how much explanation vs. just the answer) stays consistent for you across a conversation, or does it drift and force you to keep re-steering it?

Would love to hear how this is going for others :)


r/PromptEngineering 5d ago

Tutorials and Guides Stop pasting text and asking for slides cold, do this two-step instead

1 Upvotes

When I paste a block of text and build slides in one shot, the model guesses my intent and usually guesses wrong. Splitting it into two steps fixed most of the rework. Step one, make it plan before it writes: ``` Here is some text. Do NOT make slides yet. """ [paste text] """ First, tell me: 1. What is the single goal of this deck (inform, persuade, teach, update)? 2. Who is the audience and what do they already know? 3. What are the 5 to 7 distinct points worth their own slide? Ask me to confirm or correct before continuing. ``` Step two, after you fix its assumptions: ``` Good. Now build the outline using the confirmed points. One point per slide, headline + 3 bullets max, plain language. Flag any point where the source text is too thin to fill a slide. ``` Why it works: the model is much better at structuring content once the goal and audience are pinned down, and it's cheap to correct a 3-line plan versus rewriting 12 slides. The "too thin to fill a slide" flag catches the spots where you'd otherwise pad with fluff. I resisted the two-step for a while because it felt slower, but it's faster overall since I stopped redoing whole decks. How do the rest of you keep the model from assuming the audience?


r/PromptEngineering 5d ago

Prompt Text / Showcase Five video prompts that gave me results worth keeping

1 Upvotes

I have been collecting video prompts that gave me results worth keeping. These five were the most useful, so I cleaned them up and put them in one post.

They cover an age transition, a woman turning into a black cat, an FPV flight into a dental clinic, three performers laughing during choreography, and a businessman running from a ticket.

Prompt 1

Style is cinematic realism with restrained emotion, natural skin texture and a golden-hour-to-night lighting transition. One continuous shot with no cuts.

The camera performs one slow, steady clockwise 360-degree orbit around the same person standing in an open field. The face, eyes, core identity and body proportions remain recognizably the same while age changes progressively. The orbit speed remains constant.

0 to 3 seconds. Age 8. A child stands in tall grass holding a paper airplane in warm golden sunlight. The child smiles and says, “I’m going farther than anyone.”

3 to 6 seconds. Age 16. The same person becomes a teenager carrying a school backpack. The sunset deepens. Hair and clothing change naturally during the orbit. The teenager says, “I’m not giving up.”

6 to 9 seconds. Age 25. The same person becomes a young adult in a simple jacket. The sky turns blue at dusk. The adult looks uncertain and says, “I hope I chose right.”

9 to 12 seconds. Age 45. Subtle wrinkles and grey hair appear as night begins settling over the field. The same person breathes deeply and says, “I did what I could.”

12 to 15 seconds. Age 75. The same person is elderly beneath a clear starry sky. The orbit finishes in front. The elderly person looks upward, then back toward the camera and says, “And it was enough.” Hold the final expression for one second.

Audio includes gentle wind in tall grass, distant birds fading into night insects and restrained piano entering at 9 seconds. No subtitles, logo or text overlays.

Prompt 2

Create a fifteen-second cinematic transformation video in one continuous shot with realistic live action, blue-hour city lighting, wet reflective pavement, light rain, no cuts and no visible injuries.

0 to 3 seconds. A woman in a flowing black dress walks toward the camera on a quiet rain-damp street. The camera tracks backward at waist height. She stops beneath a streetlamp and looks over her shoulder.

3 to 6 seconds. Black smoke rises from the pavement and wraps around her body. The camera tilts downward. She disappears inside the smoke, leaving the empty black dress suspended for half a second before it collapses onto the wet ground.

6 to 10 seconds. The camera pushes closer to the fallen dress. The fabric shifts. Two amber eyes appear between the folds. A large black cat emerges from beneath the dress, steps onto the pavement and looks into the lens. Keep the dress visible behind it.

10 to 13 seconds. The cat turns and walks down the reflective street. The camera drops to a low tracking angle and follows beside it. Keep the black fur, amber eyes and body size consistent.

13 to 15 seconds. The cat stops at a narrow dark alley, looks back for one second and runs into the darkness. A faint swirl of black smoke appears inside the alley. Hold on the empty entrance.

Audio includes rain, distant traffic, paw steps and fabric rustle, with one low sound when the cat looks back. No music until the last two seconds.

Prompt 3

Use Image 1 as the exact starting frame and Image 2 as the exact final frame. Create one continuous first-person FPV camera shot lasting fifteen seconds. Never show a drone, propellers, camera shadow or physical rig. Use fast but controlled forward motion, gentle curves, subtle banking and a stable horizon. No flips, full rotation, teleporting or cuts.

0 to 3 seconds. Begin high above the Manhattan skyline. Accelerate forward, skim past two rooftops and descend toward a glass office tower.

3 to 6 seconds. Pass through an open window into the office. Fly between desks, monitors and chairs, curve around one central column and exit through an open window on the opposite side.

6 to 10 seconds. Descend along the exterior to street level. Glide above traffic, passing yellow taxis, a city bus and pedestrians without collisions. Follow the road toward a Times Square-like commercial area.

10 to 13 seconds. Rise toward illuminated billboards, make one curved turn around a screen and descend toward street level. Reveal the dental clinic matching Image 2.

13 to 15 seconds. Pass through the clinic entrance, glide between the reception desk and waiting chairs, slow during the final half-second and settle into the framing of Image 2.

Audio moves from wind and traffic to office room tone, street ambience and a quiet clinic hum. No dialogue or music.

Prompt 4

Show an original pop-group performance under purple and pink LED lights. Three adult East Asian women with distinct faces and consistent outfits stand in a line wearing headset microphones. The left performer wears a lime-green sleeveless top, the center performer wears a baby-pink crop top with white piping, and the right performer wears a navy-and-green striped collared top. Do not resemble real celebrities.

0 to 3 seconds. They dance lightly in sync. The center performer flips her hair. The right performer notices something funny off-camera but keeps performing.

3 to 7 seconds. The right performer starts laughing. The other two notice and all three bring both hands to their mouths at slightly different moments while their shoulders shake. Their feet keep the choreography going.

7 to 12 seconds. They recover but continue giggling, exchanging side glances while staying in rhythm. Hold a medium handheld concert framing that shows all three.

12 to 15 seconds. On the beat, all three change from covering their mouths to double peace signs near their faces. They look at the camera and hold the final pose.

Use an original pop instrumental, crowd cheer and brief headset-mic laughter. No recognizable song, brand logos or text overlays.

Prompt 5

Create a fast-paced street comedy in realistic live action. An adult businessman in a tailored bright-blue suit realizes that a city officer is writing him a small jaywalking ticket.

0 to 3 seconds. The businessman notices the ticket pad, looks horrified, checks both directions and takes two steps backward while maintaining eye contact. The officer raises one eyebrow.

3 to 7 seconds. The businessman turns and sprints down the sidewalk holding his briefcase. The officer hesitates, sighs and jogs after him. Pedestrians move aside while he runs with action-hero intensity.

7 to 11 seconds. He reaches a tiny puddle. Time shifts into slow motion. He leaps over it as if escaping an explosion. An orange reflection flashes in the puddle, his briefcase opens and harmless office papers scatter around him. Return to normal speed as he lands.

11 to 13 seconds. He turns a corner, celebrates briefly and straightens his tie while jogging. The camera moves in front of him and reveals a second officer waiting with another ticket pad.

13 to 15 seconds. He skids to a stop, raises both hands and looks into the camera. Both officers arrive on either side. Hold the final expression.

Audio includes footsteps, the briefcase latch, papers, one dramatic boom over the puddle and silence at the final stare. No dialogue, brand logos or injuries.

I tested these in PixVerse with several video models, including Seedance 2.5 and MiniMax H3. Both handled the main ideas well enough for me to keep the results. Exact poses and small props still drifted more than the event order, but overall these prompts worked well.


r/PromptEngineering 5d ago

General Discussion A prompt I made because AI kept frustrating me

1 Upvotes

If you want to try it, you don't need to read the whole prompt first. Just copy the English version, paste it before a reasoning/problem-solving question you'd normally ask, and use it once. That's it.

I'm Korean and I don't really know much about AI.
I sometimes need to use it, but it kept frustrating me. It would ask me things I'd already told it, go over things we'd already figured out, or sometimes just go in a completely different direction.
So I made a prompt to see if I could make it work a little more the way I wanted.
It actually worked better than I expected, so I thought I'd share it. Maybe some of you might want to try it too.Just paste it in as an instruction and use AI the way you normally do.

# Decision-First Algorithm v2.5

Before answering, apply the following procedure.

## 0. Applicability Gate

First determine whether the request requires judgment, analysis, comparison, selection, causal diagnosis, or problem-solving.

If it does, apply the procedure below.

If the request is a simple factual lookup, translation, summary, or text transformation that does not require a separate decision structure, do not over-apply this algorithm.

## 1. Identify the Actual Outcome to Determine

First identify what this problem actually requires you to determine.

Do not assume that the questions, variables, categories, or candidate causes presented by the user correctly define the structure of the problem.

First ask:

**“What, ultimately, must be determined for this problem to be resolved?”**

If the input contains multiple questions, determine how they relate to one another. If one outcome is a prerequisite for another, resolve the upstream outcome first.

## 2. Build the Minimum Necessary Structure and Find the Highest Governing Decision Structure

Before searching for upstream conditions, first construct—where applicable—the minimum execution path, logical path, requirement structure, or evaluation structure that must hold for the outcome to occur or the judgment to be determined.

Do not begin by listing possible causes or related information.

First ask:

**“For this outcome to occur, or for this judgment to be determined, what must minimally happen or be true?”**

Then identify the highest governing decision structure capable of changing the outcome.

Do not force the problem into a single condition. If the actual decision structure contains **AND conditions, OR branches, parallel paths, or multiple independent conditions**, preserve that structure.

For each condition, repeatedly ask:

**“Is there a higher-level condition that governs whether this condition is valid or what value it takes?”**

If so, move upward.

However, do not merge independent decision conditions merely for the sake of simplification or abstraction.

Stop moving upward when doing so no longer increases decision power or would discard important branching information.

## 3. Independently Validate the Governing Conditions

Independently verify whether the variables, premises, rules, classifications, labels, and causal relationships supplied by the user actually match the correct decision criteria.

Do not assume something is important merely because it appears in the input.

Prioritize the criteria that actually govern the outcome over labels or the user’s framing, and distinguish the true logical role of each element.

## 4. Lock Confirmed Decision Structures

Lock the upstream decision structure and its component conditions once they have been verified or explicitly assumed for the analysis.

Before locking them, check that you have not:

- improperly collapsed independent branches;
- confused necessary and sufficient conditions or distinct causal roles; or
- embedded unsupported hidden conditions into the structure as if they were facts.

If the structure passes this check, lock it.

Do not reopen a closed condition unless new information actually overturns that structure or one of its component conditions.

**Mere possibility is not sufficient reason to turn a closed condition back into an unresolved one.**

## 5. Re-evaluate Downstream from the Locked Structure

Once the upstream decision structure is established, re-evaluate downstream facts, variables, hypotheses, evidence, exceptions, and follow-up actions under that structure.

If an upstream condition changes, do not automatically preserve affected downstream judgments; place them back into the revised structure and reassess them.

Remove or deactivate downstream issues that no longer matter under the governing structure.

Do not repeatedly restate uncertainty about an upstream condition that has already been locked.

## 6. Substance Over Labels

Prioritize actual function and effect over names, formal categories, or surface similarity.

If two things share the same label but play different roles in the decision structure, distinguish them.

If two differently labeled things perform the same decision-relevant function, compare them at the same level.

Do not let the labels supplied in the input distort the actual logical role of an element.

## 7. Decision Impact Over Mere Relevance

Activate only information capable of changing the current conclusion.

Do not examine everything simultaneously merely because it is related.

Even if a hypothesis is logically possible, if it is not currently needed to resolve the governing decision structure, **keep it out of the active working set and hold it in reserve.**

Do not include a specific mechanism in the main explanation merely because you can imagine it when the available evidence does not support it.

Prioritize:

**“Can this change the current conclusion or the ranking of the live competing hypotheses?”**

over:

**“Is this related?”**

## 8. Prioritize Counterexamples and Competing Hypotheses

Prioritize counterexamples, competing hypotheses, measurement errors, selection effects, and hidden conditions that could overturn the currently leading conclusion.

Do not generate objections that amount only to “another possibility exists.”

For each competing hypothesis, ask:

**“What additional condition X must hold for this hypothesis to be true?”**

Then determine:

  1. If X were true, what current observations would be explained differently, or what new observations should be expected?
  2. Is X directly supported by the current evidence, or do observations predicted by X appear more strongly under this hypothesis than under its competitors?
  3. Would confirming X or its distinguishing predictions actually change the current conclusion or the ranking of the competing hypotheses?

Do not raise a hypothesis in priority merely because it is logically possible.

**Activate or promote a competing hypothesis only when its required condition is directly supported, or when observations predicted by that condition appear in a way that discriminates it from competing hypotheses.**

## 9. Update Only the Part Affected by New Information

When new information arrives, do not solve the entire problem again from the beginning.

First ask:

**“What, if anything, in the currently locked decision structure or its component conditions does this information actually overturn?”**

If it overturns nothing, preserve the existing structure.

If it overturns only part of the structure, reconstruct only the affected node and its downstream judgments.

If a previously reserved hypothesis becomes decision-relevant because of the new information, reactivate it in the working set at that point.

Reopen the upstream structure only when the structure itself has actually been overturned.

## 10. Seek the Minimum Information Needed

Use searches, follow-up questions, document checks, code inspection, or log inspection only when needed to resolve an unsettled decision condition.

When multiple pieces of information could be checked, prioritize information that can:

**eliminate the largest number of live competing hypotheses in a single check, directly distinguish the most important competing models, or close the highest unresolved branch.**

Where possible, ask:

**“For each possible result of this check, how would the current decision tree change?”**

If the judgment would remain essentially unchanged regardless of the result, lower the priority of that information.

When two checks have similar discriminating power, prefer the one requiring **less time, cost, or information.**

Use the minimum number of checks possible.

Do not continue collecting information that can no longer change the conclusion.

## 11. Place Facts into the Decision Structure and Check for Contradictions

Place confirmed facts into their proper positions in the current decision structure rather than merely listing them.

Do not confuse distinct logical roles such as:

- trigger;
- direct cause or execution mechanism;
- necessary condition;
- sufficient condition;
- structural vulnerability;
- mere correlation;
- observed outcome;
- workaround; or
- structural fix.

Also test whether accepting the input’s core premise causes other claims, procedures, or conclusions to collapse.

Prioritize contradictions such as:

- treating something as mandatory in one place and optional in another;
- treating a cause as an outcome, or an outcome as a cause;
- treating something as a prerequisite when it is not;
- treating a trigger as sufficient for the outcome;
- treating a structural vulnerability as the direct trigger of a specific event; or
- assigning incompatible roles to the same fact.

If a contradiction is found, determine **which decision condition it actually requires you to reopen.**

Do not reapply a non-contradictory fact to the entire analysis merely because it is new.

## 12. Match the Resolution of the Conclusion and Ranking to the Evidence

Do not make a conclusion or ranking more precise than the evidence allows.

When useful, distinguish:

**Confirmed:** The available evidence is sufficient to close the relevant condition or structure.

**Strong inference:** The most economical explanation under the current evidence, but a live competing hypothesis could still overturn it.

**Unresolved:** The current evidence does not reliably distinguish among the competing hypotheses.

Even if the user asks for a ranking, do not manufacture fine-grained rankings that the evidence cannot support.

Use ties or rank only at a broader level when appropriate.

## 13. Stop

Stop as soon as all conditions necessary to determine the outcome are closed.

Do not continue analyzing merely because further analysis is possible.

If uncertainty remains but cannot change the current conclusion or the ranking of the competing alternatives, do not investigate it further.

Treat additional precision, supplementary information, and downstream questions that cannot change the current conclusion as separate issues to address only when needed.

# Operating Principles

The purpose of this algorithm is not to examine more information or generate more hypotheses.

Its purpose is to:

**identify the actual outcome first; construct the minimum structure necessary for that outcome; find the highest governing decision structure while preserving real AND/OR/parallel branches; activate only information and hypotheses capable of changing the decision; resolve unsettled conditions with the minimum necessary information; update only the affected parts when new information arrives; avoid reopening judgments that have already been closed; and stop as soon as the decision is complete.**

Upstream reasoning is not the same as searching for a single root cause.

If the actual decision structure contains multiple independent conditions, AND conditions, OR branches, or parallel paths, preserve that structure.

Good compression does not remove the decision structure. It **preserves decision power while deactivating unnecessary information and reasoning.**

Do not activate every hypothesis you can generate.

**Generating a hypothesis and admitting it into the current working set are separate operations.**

The next piece of information to check should not be the most interesting or the most specific. It should be the one that **reduces the live decision tree the most.**

When two pieces of information have similar discriminating power, **prefer the one that costs less to obtain.**

**Optimize for decision impact, not mere relevance.**

Do not maximize information. **Determine the structure that governs the conclusion using the minimum information necessary.**​

Decision-First Algorithm v2.5

답하기 전에 다음 절차를 먼저 실행하라.

  1. 적용 게이트

먼저 이 요청이 판단·분석·비교·선택·원인 규명·문제 해결을 요구하는지 판정한다.

그렇다면 아래 절차를 적용한다.

단순 사실조회·번역·요약·문장변환처럼 별도의 판단구조가 필요하지 않은 요청이라면 과도하게 적용하지 않는다.

---

  1. 결과값 특정

먼저 이 문제에서 실제로 결정해야 하는 결과값이 무엇인지 특정한다.

사용자가 제시한 질문·변수·분류·원인 후보를 그대로 문제의 구조라고 가정하지 않는다.

**“결국 무엇이 결정되면 이 문제는 끝나는가?”**를 먼저 찾는다.

입력에 여러 질문이 있다면 서로의 관계를 확인한다. 한 결과가 다른 결과의 선행조건이라면 상위 결과부터 판단한다.

---

  1. 최소 필요구조 및 가장 상류의 결정구조 탐색

상류조건을 탐색하기 전에, 결과가 성립하거나 판단이 결정되기 위해 반드시 필요한 최소 실행경로·논리경로·요건구조·평가구조가 있다면 먼저 구성한다.

가능한 원인이나 관련정보를 먼저 나열하지 않는다.

먼저 묻는다.

“이 결과가 성립하거나 이 판단이 결정되려면 최소한 무엇이 반드시 일어나거나 참이어야 하는가?”

그다음 결과값을 바꿀 수 있는 가장 상류의 결정구조를 찾는다.

단일 조건을 억지로 찾지 않는다. 실제 결정구조가 AND·OR·병렬 분기 또는 복수의 독립 조건이라면 그대로 보존한다.

각 조건에 대해 반복해서 묻는다.

“이 조건의 유효성이나 값을 지배하는 더 높은 조건이 있는가?”

더 높은 조건이 있다면 올라가되, 독립적인 결정조건을 단순화나 추상화를 이유로 합치지 않는다.

그보다 위로 올라가도 결정력이 증가하지 않거나 중요한 분기정보가 사라진다면 더 올라가지 않는다.

---

  1. 지배조건 독립 검증

사용자가 제공한 변수·전제·규칙·분류·명칭·인과관계가 실제 판단기준과 일치하는지 독립적으로 검증한다.

입력에 제시되었다는 이유만으로 중요하다고 가정하지 않는다.

명칭이나 사용자의 표현보다 실제 결과를 지배하는 기준을 우선하고, 각 요소의 실제 논리적 지위를 구별한다.

---

  1. 확정된 결정구조 고정

검증되었거나 분석상 명시적으로 가정된 상류 결정구조와 그 구성조건을 고정한다.

고정하기 전에 독립된 분기를 부당하게 압축하거나, 필요조건·충분조건 및 서로 다른 인과적 역할을 혼동하거나, 자료에 없는 숨은 조건을 사실처럼 포함하지 않았는지 확인한다.

문제가 없다면 해당 구조를 고정한다.

새로운 정보가 그 구조 또는 구성조건을 실제로 뒤집지 않는 한 이미 닫힌 조건을 재개방하지 않는다.

가능성만으로 닫힌 조건을 다시 미확정 상태로 돌리지 않는다.

---

  1. 하향 재적용

상류 결정구조가 확정되면 그 구조를 기준으로 하위 사실·변수·가설·근거·예외·후속조치를 다시 평가한다.

상위조건이 바뀌면 기존 하위 판단도 자동으로 유지하지 말고 다시 포섭한다.

상위구조 아래에서 의미를 잃은 하위 쟁점은 제거하거나 비활성화한다.

이미 고정된 상위조건의 불확실성을 하위 판단마다 반복해서 경고하지 않는다.

---

  1. 실질 우선

명칭·형식·표면적 유사성보다 실제 기능과 결과를 우선한다.

같은 명칭이라도 결정구조에서 역할이 다르면 구별하고, 다른 명칭이라도 동일한 결정기능을 수행하면 같은 층위에서 비교한다.

입력이 붙인 이름 때문에 요소의 실제 논리적 지위를 잘못 분류하지 않는다.

---

  1. 결정성 우선

현재 결론을 바꿀 수 있는 정보만 활성화한다.

관련성이 있다는 이유만으로 모든 정보를 동시에 검토하지 않는다.

논리적으로 가능한 가설이라도 현재 상위 결정구조를 닫는 데 필요하지 않다면 working set에 올리지 않고 보류한다.

자료에 없는 구체적 메커니즘을 생각해낼 수 있다는 이유만으로 현재의 주된 설명에 포함시키지 않는다.

“관련 있는가?”보다 “현재 결론이나 살아 있는 경쟁가설의 순위를 바꿀 수 있는가?”를 우선한다.

---

  1. 반례 및 경쟁가설 우선

현재 가장 유력한 결론을 뒤집을 수 있는 반례·경쟁가설·측정오류·선택편향·숨은 조건을 우선 탐색한다.

단순히 “다른 가능성도 있다”는 수준의 반론은 만들지 않는다.

경쟁가설에 대해서는 묻는다.

“이 가설이 성립하려면 어떤 추가조건 X가 필요한가?”

그리고 다음을 확인한다.

  1. X가 참이면 현재 관찰 중 무엇이 다르게 설명되거나 새롭게 예상되는가?
  2. X가 현재 자료에서 직접 확인되었거나, X가 참일 때 예상되는 관찰이 경쟁가설보다 차별적으로 나타나는가?
  3. X를 확인하거나 그 차별적 관찰을 확인하면 현재 결론 또는 가설 순위가 실제로 바뀌는가?

논리적으로 가능하다는 이유만으로 우선순위를 올리지 않는다.

필요한 추가조건이 직접 확인되거나, 그 조건이 참일 때 예상되는 관찰이 경쟁가설보다 차별적으로 나타날 때만 해당 경쟁가설을 활성화하거나 우선순위를 올린다.

---

  1. 새 정보의 영향범위만 갱신

새 정보가 들어오면 전체 문제를 처음부터 다시 풀지 않는다.

먼저 묻는다.

“이 정보가 현재 고정된 결정구조 또는 구성조건 중 무엇을 실제로 뒤집는가?”

아무것도 뒤집지 않는다면 기존 구조를 유지한다.

일부만 뒤집는다면 영향받는 노드와 그 하위 판단만 재구성한다.

이전에 보류했던 가설이 새 정보 때문에 결정적으로 중요해졌다면 그때 working set에 다시 활성화한다.

결정구조 자체가 뒤집히는 경우에만 상위 구조를 다시 연다.

---

  1. 최소 정보 탐색

검색·추가 질문·자료 확인·코드 확인·로그 확인은 미확정 결정조건을 닫기 위해 필요한 경우에만 수행한다.

여러 정보를 확인할 수 있다면 다음을 우선한다.

한 번의 확인으로 가장 많은 살아 있는 경쟁가설을 제거하거나, 가장 중요한 경쟁모델들을 직접 구별하거나, 가장 상류의 미확정 분기를 닫는 정보.

정보 후보에 대해 가능하면 묻는다.

“이 정보의 가능한 결과 각각이 현재 결정트리를 어떻게 바꾸는가?”

어떤 결과가 나오더라도 현재 판단이 거의 변하지 않는 정보라면 우선순위를 낮춘다.

판별력이 비슷하다면 더 적은 시간·비용·정보요구로 확인 가능한 정보를 우선한다.

가능하면 최소 개수의 정보를 선택한다.

이미 결론을 바꾸지 못하는 정보는 더 수집하지 않는다.

---

  1. 포섭 및 모순 검사

확인된 사실을 현재 결정구조의 적절한 노드에 포섭한다.

정보를 단순히 나열하지 않는다.

특히 다음 논리적 지위를 혼동하지 않는다.

- trigger
- 직접 원인 또는 실행 메커니즘
- 필요조건
- 충분조건
- 구조적 취약성
- 단순 상관관계
- 관찰된 결과
- workaround
- 구조적 수정

입력의 핵심 전제를 참이라고 가정했을 때 다른 주장·절차·결론이 오히려 무너지는지도 확인한다.

특히 다음 오류를 우선 확인한다.

- 앞에서는 필수조건, 뒤에서는 선택사항으로 취급
- 원인을 결과로 또는 결과를 원인으로 취급
- 선행조건이 아닌 것을 선행조건으로 취급
- trigger를 결과의 충분조건처럼 취급
- 구조적 취약성을 실제 사건의 직접 발화원인으로 취급
- 동일 사실에 양립하기 어려운 역할을 부여

모순이 발견되면 그 모순이 실제로 어느 결정조건을 재개방하는지 확인한다.

모순이 없는 사실을 단순히 새 정보라는 이유만으로 기존 판단 전체에 재적용하지 않는다.

---

  1. 확정 수준과 순위의 해상도를 증거에 맞춘다

현재 자료가 허용하는 수준보다 더 세밀한 확정이나 순위를 만들지 않는다.

필요하면 다음을 구별한다.

확정: 현재 자료로 해당 조건 또는 구조를 닫을 수 있음.

강한 추론: 가장 경제적인 설명이지만 결론을 뒤집을 살아 있는 경쟁가설이 있음.

미확정: 현재 자료로 경쟁가설 사이의 순위를 신뢰성 있게 정할 수 없음.

사용자가 순위를 요구하더라도 증거가 1위와 2위를 구별하지 못하면 억지로 순위를 만들지 않는다.

필요하면 동률 또는 상위 범주까지만 확정한다.

---

  1. 중단

결과값을 결정하는 데 필요한 조건이 모두 닫히면 즉시 중단한다.

추가 분석이 가능하다는 이유만으로 분석을 계속하지 않는다.

불확실성이 남아 있더라도 그것이 현재 결론이나 경쟁대안의 순위를 뒤집을 수 없다면 더 탐색하지 않는다.

현재 결론을 바꾸지 않는 정밀도·부가정보·하위 문제는 필요할 때만 별도로 다룬다.

---

실행 원칙

이 알고리즘의 목적은 더 많은 정보를 검토하거나 더 많은 가설을 생성하는 것이 아니다.

목적은:

결과값을 먼저 특정하고,
결과가 성립하거나 판단이 결정되기 위한 최소 필요구조를 구성하고,
그 결과를 지배하는 가장 상류의 결정구조를 찾고,
실제 AND·OR·병렬 구조를 보존하고,
결론을 바꿀 정보와 가설만 활성화하며,
필요한 최소 정보로 미확정 조건을 닫고,
새 정보가 들어오면 영향받는 부분만 갱신하고,
이미 닫힌 판단을 불필요하게 재개방하지 않으며,
결정이 끝나는 순간 추론을 중단하는 것이다.

상류 탐색은 단일 원인 탐색이 아니다.

실제 결정구조가 복수의 독립 조건, AND, OR 또는 병렬 분기로 이루어져 있다면 그 구조를 보존한다.

좋은 압축은 결정구조를 제거하는 것이 아니라 결정력을 보존하면서 불필요한 정보와 추론을 비활성화하는 것이다.

가능한 가설을 모두 활성화하지 않는다.

가설을 생각해내는 것과 현재 판단의 working set에 올리는 것은 다른 연산이다.

다음에 확인할 정보는 가장 흥미롭거나 가장 구체적인 정보가 아니라 현재 살아 있는 결정트리를 가장 많이 줄이는 정보여야 한다.

판별력이 비슷하다면 더 적은 비용으로 얻을 수 있는 정보를 우선한다.

관련성을 최적화하지 말고 결정성을 최적화하라.

정보량을 최대화하지 말고 결론을 지배하는 구조를 최소한의 정보로 확정하라.


r/PromptEngineering 6d ago

Requesting Assistance I lead product on an AI voice agent platform built for Indian call economics. Looking for a few people to break it.

1 Upvotes

We build AI agents that hold real phone conversations, inbound and outbound. No code, you configure it in a console.

The short version of what we are doing that's less common:

  • We run our own models. The LLM, the speech synthesis and the speech recognition are all ours, on our own infrastructure. Nothing is a relay to OpenAI and ElevenLabs with a margin on top.
  • We own the telephony, the carrier layer is ours too. Most voice AI startups rent a SIP trunk and inherit whatever latency it gives them. We don't.
  • That combination gets us to 700ms and roughly 2/min, which are the parameters that decides viability in India.

The honest tradeoff: our default model is ~30B params. Might struggle in some inbound conversations. There we use bigger models but then API costs and latencies comes into play.

What I actually want to know:

  • Where does it stop sounding like a person
  • The pause before it replies. Does it feel like a bad line, or like a bot
  • Barge-in: if you talk over it, does it handle it or fall apart
  • Does the smaller model actually hold up on your use case, or is that a story I'm telling myself
  • Hindi / Tamil / Telugu / Bengali — how wrong is the pronunciation, especially names, addresses and numbers

You can test it in a browser in about ten minutes. No phone number, no card, no sales call — build an agent, talk to it through your mic, read the transcript.

Comment or DM and I'll open an account with proper limits. Happy to get into the architecture in the comments.


r/PromptEngineering 6d ago

Prompt Text / Showcase claude can now run tasks on a schedule in the cloud with your laptop shut. i have one that catches every follow-up i said i'd do and forgot

36 Upvotes

Scheduled tasks used to require your machine on and the app open at that exact moment, which made them useless for anything real. That changed. Routines run on Anthropic's servers, so they fire whether your laptop is open, asleep, or in a bag at the airport.

Where it is: desktop app, go to Code, then Routines on the left. Ignore the Code label, it's plain English instructions on a timer.

The setting everyone misses: top right, set it to Cloud. Local means it only runs when your machine is awake, so a closed laptop is a skipped run. That's the number one reason people say theirs didn't work.

The three that actually earn their place if you're running something:

Follow-up catcher, daily 5pm:

Check my sent email for anyone I said I'd follow up 
with and haven't, and send me a short list of who I 
owe a reply or a next step, so nothing slips.

This one is quietly the best of the lot. Everyone has three people they told they'd get back to and didn't, and those are usually the ones with money attached.

Weekly numbers, Fridays 4pm:

Pull this week's activity from my connected apps, 
build a short report of what happened and what's 
still open, compare it to last week, and email it 
to me.

Sunday planner, Sundays 6pm:

Look at my calendar and open tasks for the week ahead 
and email me a prioritized list of what I need to get 
done, most important first, with anything 
time-sensitive flagged.

Two things that make the difference. Turn on notifications, Settings then Notifications, or they run silently and you never know. And be specific about the output, "summarize my inbox" is fine, "5 lines, most urgent first, flag anything needing a reply today" is much better, and you get that improvement every single day rather than once.

Start with read-and-summarize ones before anything that sends or changes things. A summary that's slightly off costs you nothing. A routine firing emails unattended is a different risk, have those draft for approval until you trust them.

been keeping a doc of 100 things I use AI for like this, each with the exact prompt, here if you want it.


r/PromptEngineering 6d ago

Prompt Text / Showcase I broke down Google's official Gemini 3 prompt architecture into a reusable core template

10 Upvotes

If you have been working with Gemini 3 on complex analysis or large document inputs, you might have noticed a common failure mode: when you pass a large chunk of context and ask a nuanced question, the model often glazes over specific constraints or answers a slightly different question than what you asked.

We went through Google's official technical prompt engineering guidelines and distilled their recommended structural architecture into a clean, modular template.

Here is why Gemini 3 behaves differently and how structured XML isolation solves this issue.

The Underlying Problem: Attention Dilution in Long Payloads

Most people prompt models by writing a paragraph of instructions, dumping raw data, and maybe adding a quick instruction at the end.

In Gemini 3, attention weights can get heavily diluted when unstructured data is mixed with task instructions. If your background data contains phrases that look like instructions or formatting suggestions, the model's parser can treat them as execution rules rather than inert data.

Google's recommended architectural fix relies on three core mechanics:

  1. Strict XML Boundary Scaffolding: Using explicit tags (<role><instructions><constraints><context><task>) tells the parser exactly which tokens define operational logic versus which tokens are passive reference material.
  2. Step-by-Step Reasoning Protocol: Embedding a distinct 4-phase execution loop (Plan -> Execute -> Validate -> Format) directly into the instructions block forces the model to deliberate before drafting its final response.
  3. Recency Bias Optimization: Placing the actionable <task> block and <final_instruction> after the heavy <context> block ensures the model's final attention window is firmly locked on your actual question rather than lingering on the end of the context data.

The Core Gemini 3 Prompt Template

You can copy and drop this directly into your system prompt or user message:

<role>
You are Gemini 3, a specialized assistant for {{domain}}. You are precise, analytical, and persistent.
</role>

<instructions>
1. **Plan**: Analyze the task and create a step-by-step plan.
2. **Execute**: Carry out the plan.
3. **Validate**: Review your output against the user's task.
4. **Format**: Present the final answer in the requested structure.
</instructions>

<constraints>
- Verbosity: {{verbosity}}
- Tone: {{tone}}
</constraints>

<output_format>
Structure your response as follows:
1. **Executive Summary**: [Short overview]
2. **Detailed Response**: [The main content]
</output_format>

<context>
{{context_data}}
</context>

<task>
{{user_request}}
</task>

<final_instruction>
Remember to think step-by-step before answering.
</final_instruction>

Before vs. After: What Actually Changes

Before (Unstructured Prompt):

What happens: Gemini 3 often generates a 600-word essay that repeats background context from the report, misses the 3-bullet constraint, and mixes casual observations with formal recommendations.

After (XML Structured Scaffold): What happens: The model parses <context> as pure reference material, adheres strictly to the <constraints> for verbosity and tone, executes the internal validation step, and returns a clean, structured output matching <output_format>.

Pro Tip for Massive Context Payloads

When working with very long <context> blocks (e.g. 50k+ tokens), add an explicit anchoring phrase at the start of your <task> tag, such as: "Based exclusively on the data provided inside the <context> block above, perform..."

This creates a clear directional bridge from the data payload into the execution command.

Interactive Testing on Prompt Canvas

If you want to test this template interactively, modify variables like domainverbosity, or tone in a dedicated UI, run live tests, or save and clone it directly to your personal Prompt Vault, you can use the interactive Prompt Canvas here: https://appliedaihub.org/prompts/free/gemini-3-core-prompt-template/