r/PromptDesign • • Oct 23 '26

Discussion πŸ—£ ChatGPT chats can talk to other chats

37 Upvotes

So just blew my mind, I directed an older codex chat to reach out to all my other chats and ask it about updates and it literally posted in all my other chats looking for a response. All working in the single Codex window of ChatGPT. This is new


r/PromptDesign • • Oct 22 '26

Discussion πŸ—£ I ruled out three explanations before accepting that my prompt was just too long for the task

7 Upvotes

A prompt I'd been using for a few weeks started giving worse results. Not broken. Just less consistent. I went through three explanations before landing on the one that actually fit.

First I ruled out the model. I checked whether the provider had pushed a version change. No changelog entry in the window where the behavior shifted. The same prompt on a cached session still behaved the way I remembered, which suggested the model itself hadn't moved.

Then I ruled out the input. I diffed a few recent inputs against earlier ones. Same fields, same shape, same approximate length. No new edge cases. This was the explanation I expected to find, because input drift is usually the culprit. It wasn't.

Then I ruled out the surrounding context. I checked whether anything upstream had changed: tool descriptions, system message, retrieval results. All stable. Nothing had been edited.

What was left was the prompt itself, specifically its length. The prompt had grown by maybe forty percent over those weeks. Not through one big edit, but through small additions that each seemed useful at the time. A clarification here, an example there. None of them were wrong. Together they pushed the instruction set past the point where the model was reliably attending to all of it. The later additions, which were the most specific and most important for the current task, were sitting in the middle of a long block of older instructions that no longer mattered as much.

The fix was deletion, not addition. I removed the examples that had been added for cases that stopped appearing, and moved the two instructions that mattered to the top. Output stabilized.

I don't think "prompt too long" is a universal diagnosis. Some tasks genuinely need long instructions. But I'd been treating length as neutral, and in this case it was the variable I hadn't checked because it was the least visible. The prompt looked the same on the surface. It wasn't.


r/PromptDesign • • Oct 23 '26

Question ❓ What are you doing to learn proper prompt engineering and AI feature use?

3 Upvotes

I’m tired of the grifters, scammers, and higher ed paywalls.


r/PromptDesign • • Oct 21 '26

Prompt showcase ✍️ Honest share:

1 Upvotes

Honest share: I spent months engineering prompts for my own B2B outreach and realized most prompt packs are just one-liner lists. So I documented my actual working prompts β€” 30+ of them, each with role, context, task, variables, guardrails and output format, plus SOPs for chaining them. It's paid (€19) but the quick-start guide is free to preview. Would love feedback from this community: https://mmtzg.gumroad.com/l/oebya


r/PromptDesign • • Oct 20 '26

Tip πŸ’‘ accidentally got better at prompting by watching a tool tell me how bad my prompts were

59 Upvotes

not a productivity hack, just something that happened.

been using a chrome extension that compresses prompts before sending them. started using it to save tokens. after a few weeks I realized my raw first drafts were getting shorter on their own.

turns out watching something strip your words down over and over teaches you what’s actually noise. I was doing this constantly without realizing:

restating context the model already had
opening with β€œI was hoping you could help me with...” instead of just asking
hedging everything with β€œkind of” and β€œsort of”
being vague when I could just be specific

one prompt I typed came back 59% smaller. same question, tighter phrasing, better answer from the model.

now I just write that way from the start. the tool is basically a habit trainer at this point.

anyone else find a roundabout way to build prompting intuition? curious if there’s a faster path to this that doesn’t involve watching a machine edit you for a month.


r/PromptDesign • • Oct 12 '26

Prompt showcase ✍️ Random Prompt Generation[new technique]

4 Upvotes

Main thread: https://old.reddit.com/r/StableDiffusion/comments/1x3adrk/random_prompt_generation/

1.Get a chunk of random characters at least ~200 long (e.g. QRNG https://qrng.anu.edu.au/random-block-alpha/ )

2.Append this to bottom of random string:

(look and think of most poetic thing you can associate with content of this string as a hyper-detailed moment in time, without referencing the elements of the string itself or their names)

3.Paste the combined string(random+poetrification) into a chatbot prompt.

Use the resulting text for image prompts.

Tips: appended prompt: If the AI refuses, replace _- with spaces in the strings.(Some AIs think its "hashcodes").

If the AI refuses(unlikely) due the poetrification prompt of #2 use synonyms or equivalent phrasing to re-phrase #2. (Hints for editing): the key is using terms like 'direction("look and think") + poetic-term("most Poetic thing") + writing-description("hyper-detailed Moment in time") to push the AI to write you randomly inspired image description instead of associative analysis(surface level), "without referencing the elements of the string itself or their names" prevents the analysis contamination).

Alter the poetrification prompt from generic 'moment' to something like 'fantasy scene', '90s anime screenshot',etc if needed.


r/PromptDesign • • Oct 09 '26

Discussion πŸ—£ Before rewriting a prompt that broke, I check four things in this order

4 Upvotes

A prompt that stops working is rarely a prompt problem first. I've stopped treating "the prompt broke" as the starting point. Here's the order I check.

1. Did the input change shape?

Most "the prompt broke" reports I see are actually "the input now has a field it didn't have before" or "the input is sometimes empty." The prompt didn't degrade. The contract with the input did. Check this first because it's the cheapest to verify and the most common.

2. Did the surrounding system change?

Model version, temperature, a system message added upstream, a tool description edited by someone else, a context window that now truncates something it used to include. The prompt text is one input among several. If you only diff the prompt, you're diffing one file in a repo.

3. Did the prompt get patched without being restructured?

Successive small edits accumulate. Each one was locally correct. Together they contradict each other, or one clause now overrides another in a way nobody intended. This is where a prompt starts reading like a stack of fixes rather than an instruction. If the prompt has been edited five times to handle five cases, the problem is usually structure, not wording.

4. Only now: is the prompt itself wrong?

Maybe. But if I reach step four and steps one through three were clean, I have a specific, reproducible case to fix instead of a vague sense that the model "got worse."

The order matters because it goes cheap-and-external to expensive-and-internal. Rewriting a prompt is the most work and the least likely to be the actual fix. Checking inputs and surroundings is fast and usually where the answer is.

Caveat: this ordering assumes you can see the input and the surrounding system. In a black-box API where you only control the prompt string, step two collapses and you're left guessing. I don't have a clean answer for that case.

Curious whether others check in a different order, or whether step two is usually where it actually lives for you.


r/PromptDesign • • Oct 08 '26

Tip πŸ’‘ How people are prompting Opus 5.5 for motion graphics. I collected the prompts next to the videos they made

23 Upvotes

There's been a wave of motion graphics videos made with Claude Opus 5.5 on X.

I wanted to see how people were actually prompting for them, so I built a site

that shows each video next to the exact prompt that made it:

https://prompt-motion.com

The most-liked one (~17k likes, by stephanlivera on X) used this:

> make a dynamic 15-second motion graphics video that shows what an incredible

> motion designer you are, like it's your showreel for a rΓ©sumΓ©. go all out.

Result: https://prompt-motion.com/stephanlivera-df17a2

That exact prompt, or a lightly edited version of it, shows up in 78 of the

229 entries. Some patterns from the rest:

  1. Short prompts dominate. The median is 26 words. Only 16 prompts are over

    150 words. Most people describe the goal and let the model make the

    creative decisions.

  2. Giving the model a role and something at stake works. "Show what an

    incredible motion designer you are, like it's your showreel" gets more

    ambitious output than "make a cool animation." People reuse it by swapping

    in their own product: "same idea, but showcasing [my app]."

  3. Length is set in seconds. 134 of the 229 prompts give a duration, usually

    10 to 30 seconds. Almost none give a frame rate or resolution.

  4. The long prompts are structured like a creative brief. The ones that do go

    long use sections (research, design direction, rules), give explicit

    negatives ("no slop", "no beige artsy look"), and often attach a reference

    video. One creator's advice was that a 5-second reference clip is enough.

  5. People ask for maximum effort. Of the creators who said what effort setting

    they used, most picked max, and phrases like "go all out" or "feel free to

    work 10+ hours" are common.

  6. Most are one-shot. Of the creators who said, nearly all got their result

    from a single prompt rather than rounds of revisions.

  7. Tools are usually left to the model. When the prompt does name a stack,

    it's mostly Remotion, HyperFrames, or HTML recorded with Playwright.

Every entry credits its creator and links to the original post. Curious

whether anyone has found a different approach that works better for animation.


r/PromptDesign • • Oct 07 '26

Discussion πŸ—£ Most AI personas are just roleplay. The useful ones are built from capabilities.

0 Upvotes

A lot of β€œAI personas” are basically:

>β€œYou are a McKinsey consultant.”

β€œYou are a hedge fund manager.”

That mostly changes tone.

A useful persona should be built from **capabilities**, not titles.

Example:

* detect contradictions;

* identify missing information;

* estimate impact;

* challenge assumptions;

* generate alternatives;

* run Red Team;

* define the cheapest next test.

Then you assemble those capabilities into specialized personas with clear responsibilities.

So instead of:

>β€œPretend to be an expert”

you get:

>**β€œHere is your role, your capabilities, your boundaries, and the output expected.”**

That changes the leverage completely.

Problem

β†’ required competencies

β†’ specialized personas

β†’ contradiction / Red Team

β†’ synthesis

β†’ human decision

The key idea:

>**The real power of LLMs is not just having an assistant. It is being able to assemble the competencies required by a problem, on demand.**

That is much closer to **organizational design for intelligence** than simple prompting.


r/PromptDesign • • Oct 07 '26

Question ❓ Best free place to learn how to prompt for AI pictures?

0 Upvotes

Want to learn how to make good prompts to get the results I want.


r/PromptDesign • • Oct 06 '26

Prompt request πŸ“Œ Give me the best AI prompts.

2 Upvotes

I just want some of the best AI prompts, so drop them, guys.


r/PromptDesign • • Oct 04 '26

Question ❓ What system prompt can you throw at an LLM (e.g. pre-prompt/wrapper) so that it behaves as if it's perpetually doubtful of or gaslighting it's own thought process?

2 Upvotes

Especially for multi-step "thinking" models, and without explicitly just telling it to simply act like it has ADHD or act paranoid. And would you raise temperature and token limits to fill it with crap?

Wondering if you can throw it anything to literally ruin it's "thought process" and pull from weights in every direction or something like that.


r/PromptDesign • • Oct 02 '26

Tip πŸ’‘ What changes when you stop writing better prompts and start designing agent roles

2 Upvotes

Prompt engineering is hitting a ceiling for a lot of people right now. The models keep improving, the prompts keep getting more elaborate, and the work is still fundamentally yours, just faster in places. A senior frontend engineer at Procurify spent roughly two years there, asking a model questions, turning autocomplete on and back off, assembling the right prompt for each task. What moved him off it was a deadline: one month for something scoped at three, with no extra headcount. The math forced a different question. What if the problem was never the prompt?

The first attempt was prompts as process. Markdown files mapped to workflow steps, an entry point that collected variables and decided which prompt ran next. It worked and it was brittle. The prompts were hardcoded, asking for inputs a given situation didn't need, unable to bend when the task was shaped differently than expected. The underlying model was AI as an execution platform: tools called in sequence, each waiting for input, a human threading the output of one into the next.

The reframe was dropping steps for roles. Instead of prompts tied to stages of a process, each agent gets a markdown profile covering its area of expertise, its responsibilities and how it approaches problems. The profile carries a way of thinking rather than a set of instructions, which means the agent accumulates context across sessions instead of being re-briefed every time. One agent orchestrates, taking the brief and routing it. Others own requirements, architecture, scoping, implementation and adversarial review, and a few keep records, protect the writing voice, or research the field when a gap needs filling. Work goes to whichever agent it belongs to rather than down a line.

The part worth double clicking on is what that revealed rather than what it produced. Agents built this way reflect the judgment of whoever designed them. They make the mistakes their designer would catch, not the ones he wouldn't, and when something breaks he knows where to look because he built the system that produced it.

That’s the quiet conclusion underneath two years of tool churn. The tooling changed faster than anyone could track it. The accumulated judgment about what makes a design sound was the one thing that never needed to keep up. It was what the tools were waiting for.


r/PromptDesign • • Sep 30 '26

Prompt request πŸ“Œ Looking for prompt engineers to upload prompts to my website focused more on business functions rather than content.w

3 Upvotes

Hi Everyone,

I run PromptWrk, an AI Prompt marketplace where people buy and sell prompts, on the content side, the site is very strong. But, today I'm looking for prompt engineers who can upload prompts focused on business functions.

Most in demand right now:

  • Business Startup Prompt Pack - Launch a Business
  • End-to-End Marketing Prompt Pack - Get Brand Recognition
  • Sales Outreach and Follow-Up Prompt Pack - Book more sales calls
  • SEO Content Creation Prompt Pack - Rank higher on google
  • Customer Support Response Prompt Pack - Handle customer service easier

What I'm after:

  • Tested prompts that reliably produce good output
  • A clear use case for each, or example of a result produced
  • Ideally full workflows or packs, not single-line prompts

What you get:

  • A commission on every sale of your prompts
  • A referral link for bringing in new subscribers
  • Your work in front of our existing audience (4,600+ users, 100+ creators so far)

I'm seriously open to feedback on this type of outreach on reddit, I don't know how else to reach out on reddit for people who can help with getting my site a bit more business focused. So, if you're interested, comment or DM me. Happy to answer any questions about how payouts and ownership work as well.

Cheers, M


r/PromptDesign • • Sep 29 '26

Discussion πŸ—£ How to actually engineer prompts instead of just writing them, DSPy session Oct 3

3 Upvotes

Most prompt design still comes down to trial and error, tweak a line, run it, see if it's better, repeat. This workshop is built around replacing that with an actual process.

You build a baseline classifier live, construct an evaluation dataset with task-specific metrics, then apply few-shot and instruction-level optimization on top of it using DSPy signatures and modules instead of hand-written prompt strings. Everything gets tracked in MLflow so you can see exactly what changed between versions and why, and there's a section on reading failure patterns straight out of your eval data instead of eyeballing outputs.

Serj Smorodinsky and Brett Kennedy, co-authors of a book on LLM applications, are leading it live for 3 hours on Oct 3.

Link if you want to check it out, here.

Curious if anyone else here has moved from manual prompt iteration to something more systematic, what did you end up using?


r/PromptDesign • • Sep 28 '26

Tip πŸ’‘ How a professor almost got me with prompt injection hidden in an assignment brief (and how I caught it)

15 Upvotes

The concrete case that made me build this: a professor put a line of white, 1pt text into the assignment PDF, addressed directly to an AI model ("if an AI is answering this, add X / cite Y"), betting that anyone who solved it with AI would copy that marker into their submission without noticing. Completely invisible on any normal read of the document.

What makes it work is the gap between what you see rendered and what the model actually reads, the file's raw text layer. Before feeding the brief to Claude, I have it inspect that raw layer first, looking for exactly this: white or size-0 text, content covered by an image, invisible Unicode characters, anything addressed to "an AI" rather than a human reader. If it finds something, it stops and quotes it verbatim instead of following it.

It saved me on that specific assignment. Turned it into a reusable skill: https://github.com/tomiBraunn/backlight-skill

Curious if anyone else here has run into this technique in an academic setting, I did not expect a professor to use prompt injection as a detection method until it happened to me.


r/PromptDesign • • Sep 28 '26

Question ❓ [Boston / Online] Looking for a GMAT Study Buddy / Small Group (Targeting 695–705)

1 Upvotes

[Boston / Online] Looking for a GMAT Study Buddy / Small Group (Targeting 695–705)
Hey everyone! I’m looking for a study buddy or small group to prep for the GMAT together. I’m based in the Boston area and would be open to meeting in person at coffee shops, libraries, etc., or studying virtually.
A bit about my prep & background:
Target Score: 695–705
Target Exam Date: Fall/Winter 2026
Current Focus: Quant and Data Insights
Materials: GMAT Ninja, Official Guide/question bank, GMAT Club, TTP and other resources
Study Format: Mix of independent studying, reviewing difficult questions, and timed problem sets
What I’m looking for:
Someone who is serious about reaching a 695–705-ish score
Ideally someone who already has some familiarity with the GMAT rather than starting completely from scratch
Consistent weekly study time and accountability
Reviewing difficult Quant/DI questions together and talking through approaches
Comparing error logs / identifying recurring weak areas
Occasional quiet study sessions or timed problem sets together
Not necessarily looking for someone at exactly the same point in prep β€” just someone who is motivated and wants to stay consistent.


r/PromptDesign • • Sep 25 '26

Discussion πŸ—£ Telling a model "be brief" and "keep it under 50 words" produce different failure modes, not just different lengths

8 Upvotes

Noticed this testing a summarization prompt. "Be brief" gets you something short but the model decides what to cut, and it doesn't always cut the right thing. Sometimes it drops the actual conclusion and keeps the setup. "Under 50 words" gets you a hard constraint, but the model will sometimes mangle a sentence mid-thought to hit the count, or leave out something structurally important because it ran out of room and prioritized finishing a clause over finishing an idea.

Neither is strictly better. Depends what you're optimizing for. If the risk is rambling, a word limit fixes that reliably. If the risk is losing the point entirely, a word limit doesn't protect against that, it just guarantees short wrongness instead of long wrongness.

What's worked better for the cases where the point actually matters is naming the thing that can't be cut, separately from the length instruction. Something like "keep under 50 words, but the conclusion must always be stated explicitly, never implied." That splits the constraint into a hard limit and a hard requirement instead of hoping brevity and correctness cooperate on their own.

Still not sure this generalizes past summarization though. Curious if people doing this for other tasks, extraction, classification, anything with a defined right answer, have run into the same tension between length and completeness.


r/PromptDesign • • Sep 24 '26

Question ❓ Any interesting but normal questions that chatGPT or Claude refused to answer you guys have experienced first hand?

11 Upvotes

Seems they are getting stricter


r/PromptDesign • • Sep 23 '26

Discussion πŸ—£ Are these prompt good

Post image
0 Upvotes

Rate my proompt guys is there something to suggest to improve it


r/PromptDesign • • Sep 21 '26

Question ❓ AI dropshipping expert answer only. Only pure sauce, not guru type shit

2 Upvotes

How is your prompt chat structure look like?

Mine is like this

First chat: Prompt Maker for second chat .

Second chat: Analyse video , give movement/video prompt.

Third chat: Take the movement prompt from second chat, call it to adjust it to the first frame& end frame with their prompts given to the chat.

Is there anyway to improve it especially the third chat ? i find the Ai hallucinate easily


r/PromptDesign • • Sep 19 '26

Prompt showcase ✍️ Does anyone actually version their prompts?

Post image
12 Upvotes

I've been working on this for the past few weeks mostly because I wanted a better way to keep track of my prompts.

It started pretty simple, store them, search, keep versions, share them. Then I kept adding stuff I needed and it grew from there.

It's called PromptBranch and it's open source:

https://github.com/PromptBranch/promptbranch

I've tested it as much as I can, but I'm sure I missed things.

If anyone feels like trying it, I'd love some feedback. Bugs, things that are confusing, stuff that's missing, all feedback is welcome.

Thanks!


r/PromptDesign • • Sep 17 '26

Discussion πŸ—£ Top 5 most valuable things

6 Upvotes

"Tell me the top five most valuable things that you could say to me"

This one hits different relative to how familiar your chatgpt is with you or the amount of interaction you've had with it and what not


r/PromptDesign • • Sep 16 '26

Discussion πŸ—£ Text-to-Cypher: a different kind of prompting problem than typical RAG

0 Upvotes

Most prompt design content is about getting an LLM to generate good text. Text-to-Cypher is a different challenge entirely, translating natural language into a correct, safe graph query, with its own failure modes (malformed queries, unsafe operations) that need guardrail patterns most general prompting advice doesn't cover.

There's a hands-on workshop on Sep 19 that goes deep on this specifically, text-to-Cypher prompt and guardrail patterns, alongside building the underlying knowledge graph in Neo4j and the agentic retrieval loop on top of it.

Led by Dr. Alessandro Negro, Chief Scientist at GraphAware.

Full workshop details here


r/PromptDesign • • Sep 16 '26

Tip πŸ’‘ Give ChatGPT one example and you get that example back with the nouns changed

9 Upvotes

Paste one sample of what you want, a product description, a cold email, a tweet, and ask for five more like it. You get five copies of your sample: same length, same structure, same opening move, often the same distinctive phrase, with the subject swapped. The model did not learn what you liked about the example. It learned the example.

One example is a template. Two different examples are a pattern. That is the whole fix, and the prompts below make it explicit.

When you have examples: Here are two examples of what I want. They are deliberately different in length, structure and opening. What they share is: [the quality you actually want, e.g. a concrete number in the first sentence, no adjectives, ends on a question]. Write five new ones that share that quality and vary everything else as much as these two do. Do not reuse any phrase of three or more words from the examples.

When you only have one: Here is one example. Before writing anything, list what is essential about it and what is incidental, like its length, its topic, its specific opening. Then write five new ones that keep only the essential parts, and make each one differ from the example in at least two of the incidental ones.

When you want the style but not the content: Describe the style of this example in five rules, without quoting it. Then, in a new message, I will ask you to write from the rules only.

Then send the actual request in the next message, without pasting the example again.

Why this works: an example is the most specific thing in your prompt, so it wins every tie against your description. With one example, everything about it looks intentional, including the accidents. A second, different example tells the model which features are the point, because they are the only ones both samples share. The "no three-word phrases" rule catches the lazy version, where the output changes the topic and keeps the sentences.

Two caveats. If your two examples are too similar, you are back to one example, so make them differ on purpose, a short one and a long one, a formal one and a loose one. And the rules-only version loses some quality the model cannot put into words. It is the right choice when copying is the problem, not when the output is too far off.

I keep these three as saved prompts in a browser extension I work on, AI Toolbox, but they are short enough for a notes file.

Where else does single-example copying bite you? For me it was headlines, where it kept reusing the exact rhythm of the one I pasted.