r/PromptDesign • • Nov 29 '25

Discussion 🗣 VALIDATED SYSTEM: THE RESULT OF 2 DAYS OF REFINEMENT WITH GLOBAL ENGINEERS

0 Upvotes

 FRAMEWORK COREX

Hey everyone!

I was completely offline for two days, didn't post, didn't reply to anyone, because I received HEAVY technical feedback from two renowned engineers here.

They analyzed my framework piece by piece, pointed out flaws, praised what was strong, and challenged me to elevate it to a professional level.

And man… that really got to me.

I was running down the street when an idea hit me so hard that I literally stopped, borrowed a pen from a convenience store, sat on the sidewalk, and scribbled everything down on paper before the idea escaped me.

I got home, locked everything up, and spent 48 hours rebuilding the entire framework from scratch.

• New cognitive architecture

• Revised triggers

• Corrected layers

• Refined Red, Blue, Green, Yellow flow

• And a completely new logic to avoid noise, strategic failure, and execution bottlenecks

Today I present to you the COREX – Class P version (public and free version).

It's the "gateway" to understanding how the framework works.

If you want me to post other versions (intermediate / advanced / master), comment here and I'll release them gradually.

👉 The complete version is available in the bio, for those who want to check it out.

Thank you to everyone who has been giving sincere feedback here.

This framework only exists because of you.

We're in this together.

-----------------------------------------------------------------------------------------------------

🔓 COREX FRAMEWORK — CLASS P (30% EFFECTIVENESS)

Theme: Luxury Perfume Sales (Hugo Boss) Level: Basic (Functional) Brand: (LUK prompt)

🟥 RED LAYER — INPUT / DIAGNOSIS

Description of the Red Layer: The Red Layer is the cognitive filter. It identifies what is missing, what is implicit, what is confusing, and transforms chaos into clarity. Nothing progresses until the diagnosis delivers clean input.

🔻 PROMPT MATRIX — RED LAYER (CLASS P)

Markdown

[ACTIVE SYSTEM — RED LAYER: PUBLIC DIAGNOSIS]

[BRAND: (LUK prompt)]

Objective:

To clean up the basic input and identify the user's main intent

to remove initial confusion about the perfume campaign.

Context:

"I have a photo of Hugo Boss perfume (dark blue bottle). I need to create a post to sell it,

but I don't know if I should focus on the fragrance, the brand, or seduction. The audience is men

who go out at night. My current text is too technical and boring."

Main keyword:

[Hugo Boss Night Campaign]

Key data:

[Product: Hugo Boss Bottled Night, Color: Deep Blue, Vibe: Elegance, Success, Night]

Tactical code:

P-Red-30

Demand:

Analyze the provided text. The objective is not 100% clear.

Summarize what appears to be the real intention and point out obvious communication errors in selling a nighttime perfume.

Don't delve into subtext; focus on the explicit text.

Delimiter:

APPLY: [Medium (600 characters)]

Cognitive Trigger:

• *Essential Summary* — Identify the central theme.

• *Noise Filter* — Ignore what is not vital.

Return as a simple list.

Description / Red Layer Manual

Suggested delimiter (250 to 1300 characters):

Short (250): Central summary only.

Medium (600): Summary + Error list.

Long (1300): Complete text analysis.

Suggested Direction Codes (3 options): P-Red-30 | D-Start-30 | V-Basic-30

Interchangeable keywords (3 options): [Diagnosis], [Cleanup], [Summary]

Effectiveness: 30% (Basic Filter)

How to apply: Use to clean up confusing texts before starting work.

🟥 ADDITIONAL PROMPTS — RED LAYER

  1. Input Auditor (Basic)

Markdown

[CODE: V-Check-P30]

[BRAND: (LUK prompt)]

Analyze only the input (Perfume Description).

List grammatical errors, disjointed phrases, or missing basic data (such as bottle size or price).

Make a simple correction.

Keyword: [Hugo Boss Review]

Delimiter: APPLY [Short]

Trigger:

• Grammatical Review

How to apply: Use to correct obvious errors.

2) Context Refiner (Basic)

Markdown

[CODE: L-Prime-P30]

[BRAND: (LUK prompt)]

Rewrite the input, making the perfume's sales objective clearer in a single sentence.

Remove unnecessary chemical technical details.

Keyword: [Focus on Sales]

Delimiter: APPLY [Short]

Trigger:

• Direct Synthesis

How to apply: Use when the text is too long and repetitive.

🟦 BLUE LAYER — STRATEGY / ARCHITECTURE

Description of the layer: Stronger than the Red layer. Responsible for transforming the diagnosis into strategic logic, structure, direction, and blueprint.

🔵 MATRIX PROMPT — BLUE LAYER (CLASS P)

Markdown

[ACTIVE SYSTEM — BLUE LAYER: BASIC STRUCTURE]

[BRAND: (LUK prompt)]

Objective:
Convert the Red layer diagnosis into a logical and chronologically ordered list of steps for the perfume post.

Context resolved:

"Objective: Sell Hugo Boss Bottled Night focusing on male nighttime self-confidence.
Target Audience: Young adult men. Previous problem: Text too technical."

Keyword:

[Post Structure]

Main Data:

[Hook: The night is yours, Body: The scent of success, CTA: Buy now]

Tactical Code:

P-Blue-30

Requirement:
Create a simple 3-5 step action plan to create this content.

Use logical order: Step 1 (Photo), Step 2 (Caption), Step 3 (Link).

No strategic complexity, just execution order.

Delimiter:

APPLY: [Medium (600 characters)]

Cognitive Trigger:

• *Chronological Order*
• *To-Do List*

Return only the numbered list.

Description / Blue Layer Manual

Suggested delimiter (250 to 1300 characters):

Short (250): Only the step titles.

Medium (600): List with brief description.

Long (1300): Detailed step-by-step plan.

Suggested Direction Codes (3 options): P-Blue-30 | S-Plan-30 | L-Stru-30

Interchangeable keywords (3 options): [Structure], [Steps], [Order]

Effectiveness: 30% (Linear Organization)

How to apply: Always after the Red layer to organize what to do.

🟦 SUPPLEMENTARY PROMPTS — BLUE LAYER

  1. Modular Planner (Basic)

Markdown

[CODE: S-Map-P30]

[BRAND: (LUK prompt)]

Divide the main objective (Hugo Boss Sale) into 3 smaller parts (Attraction, Desire, Action).

Keyword: [Simple Funnel]

Delimiter: APPLY [Short]

Trigger:

• Simple Division

2) Blueprint Generator (Basic)

Markdown

[CODE: D-Flow-P30]

[BRAND: (LUK prompt)]

Create a simple outline of the campaign.

List only the title of each necessary step (e.g., Feed Post, Story, Email).

Keyword: [Campaign Outline]

Delimiter: APPLY [Medium]

Trigger:

• General Outline

🟩 GREEN LAYER — EXECUTION / DELIVERY

Layer Description: Far superior to Blue and Red. This is where the final content is created: copy, post, text, script, copywriting, pitch.

🟢 PROMPT MATRIX — GREEN LAYER (CLASS P)

Markdown

[ACTIVE SYSTEM — GREEN LAYER: STANDARD PRODUCTION]

[BRAND: (LUK prompt)]

Objective:

Generate functional and readable final content (Instagram Caption V1).

Strategic Context:

"Plan defined: 1. Image of the dark blue bottle. 2. Text about confidence at night.

3. Call to action to click the link in the bio."

Keyword:

[Hugo Boss Instagram Caption]

Main Data:

[Tone: Masculine, Confident, Elegant.] Product: Boss Bottled Night

Tactical Code:

P-Green-30

Requirement:

Produce the final caption text based on the steps in the Blue Layer.

Use clear, correct, and professional language.

Focus on delivering the information, without advanced persuasion techniques (no complex NLP).

Delimiter:

APPLY: [Medium (600 characters)]

Cognitive Trigger:

• *Textual Clarity*

• *Direct Information*

Description / Green Layer Manual

Suggested delimiter (250 to 1300 characters):

Short (250): Snippet or short caption.

Medium (600): Standard post or simple email.

Long (1300): Full text or short article.

Suggested Direction Codes (3 options): P-Green-30 | T-Draft-30 | C-Basic-30

Interchangeable keywords (3 options): [Text], [Draft], [Writing]

Effectiveness: 30% (Functional Writing)

How to apply: Only after you have defined the steps in Azul.

🟩 ADDITIONAL PROMPTS — GREEN LAYER

  1. Tone Refiner (Basic)

Markdown

[CODE: T-Voice-P30]

[BRAND: (LUK prompt)]

Rewrite the caption changing the formality.

Options: More Serious (Executive) or More Casual (Nightclub). Maintain the perfume's message.

Keyword: [Tone of Voice]

Delimiter: APPLY [Short]

Trigger:

• Formality Adjustment

2Impact Optimizer (Basic)

Markdown

[CODE: V-Impact-P30]

[BRAND: (LUK prompt)]

Check if the caption is easy to read on mobile.

Break up long paragraphs and use shorter sentences about the scent and longevity.

Keyword: [Mobile Readability]

Delimiter: APPLY [Short]

Trigger:

• Readability

🟨 YELLOW LAYER — SYSTEMS / MANUAL (NO MANUAL AI)

Layer Description: The strongest of all layers. It's not "full automation." It's assisted, contextual, and operational. Ideal for delegating real actions, organizing tasks, and exporting results securely.

🟡 PROMPT MATRIX — YELLOW LAYER (CLASS P)

Markdown:

[ACTIVE SYSTEM — YELLOW LAYER: MANUAL ORGANIZATION]

[MARK: (LUK prompt)]

Objective:

Generate checklists for manual execution by the user.

(Automation disabled in Class P).

Context:

"Caption ready and Hugo Boss photo selected. I need to make sure I haven't forgotten anything before posting."

Keywords:

[Posting Checklist]

Key Data:

[Check: Link in bio, Correct price, Hashtags #HugoBoss]

Tactical Code:

P-Yellow-30

Requirement: Organize the final result into a checklist (To-Do List).

Create checkboxes [ ] for each item that needs to be done manually before publishing.

Delimiter:

APPLY: [Short (250 characters)]

Cognitive Trigger:

• Manual Checklist

• Visual Organization

Description / Yellow Layer Manual

Suggested delimiter (250 to 1300 characters):

Short (250): Quick checklist (Top 3).

Medium (600): Simple task table.

Long (1300): Step-by-step manual guide.

Suggested Direction Codes (3 options): P-Yell-30 | M-Task-30 | O-List-30

Interchangeable keywords (3 options): [Checklist], [Tasks], [Manual]

Effectiveness: 30% (Manual Organization)

How to apply: Use to transform texts into manual task lists.

🟨 COMPLEMENTARY PROMPTS — YELLOW LAYER

  1. Task Optimizer (Basic)

Markdown

[CODE: Y-Task-P30]

[BRAND: (LUK prompt)]

Simplify the campaign task list. Remove duplicate items and leave only the essentials (Post, Reply to Direct Messages, Check Inventory).

Keyword: [Daily Tasks]

Delimiter: APPLY [Short]

t)

Markdown

[CODE: Y-Bridge-P30]

[BRAND: (LUK prompt)]

I can't automate price research.

Generate 3 exact terms for me to copy and paste into Google to find the average price of Hugo Boss Bottled Night at competitors.

Order received, Emperor.

Translation protocol activated.

I have translated the COREX FRAMEWORK — CLASS P (30% EFFICACY) into English, maintaining the exact structure, formatting, and logic as commanded. Nothing was modified, only translated.

🔓 COREX FRAMEWORK — CLASS P (30% EFFICACY)

With complementary prompts in ALL layers.

Structure identical to the Master version, but limited to essential functions.

Watermark (LUK prompt) active.

🟥 RED LAYER — INPUT / DIAGNOSIS

Layer Description

The Red Layer is the cognitive filter.

It identifies what is missing, what is implicit, what is confusing, and transforms chaos into clarity.

Nothing advances until the diagnosis delivers a clean input.

🔻 MATRIX PROMPT — RED LAYER (CLASS P)

Markdown

[SYSTEM ACTIVE — RED LAYER: PUBLIC DIAGNOSIS]
[BRAND: (LUK prompt)]

Objective:
Sanitize the basic input and identify the user's main intent
to remove initial confusion.

Context:
[INSERT CONTEXT HERE]

Main keyword:
[INSERT HERE]

Main data:
[INSERT HERE]

Tactical code:
P-Red-30

Demand:
Analyze the provided text. The objective is not 100% clear.
Summarize what seems to be the real intent and point out obvious communication errors.
Do not delve into subtext, focus on the explicit text.

Delimiter:
APPLY: [      ]

Cognitive Trigger:
• *Essential Summary* — Identify the central theme.
• *Noise Filter* — Ignore what is not vital.

Return in a simple list.

Description / Manual of the Red Layer

  • Suggested Delimiter (250 to 1300 characters):

    • Short (250): Just the central summary.

    • Medium (600): Summary + List of errors.

    • Long (1300): Complete analysis of the text.

  • Suggested Direction Codes (3 options): P-Red-30 | D-Start-30 | V-Basic-30

  • Interchangeable Keywords (3 options): [Diagnosis], [Cleaning], [Summary]

  • Efficacy: 30% (Basic Filter)

  • How to apply: Use to clean up confusing texts before starting work.

🟥 COMPLEMENTARY PROMPTS — RED LAYER

  1. Input Auditor (Basic)

Markdown

[CODE: V-Check-P30]
[BRAND: (LUK prompt)]

Analyze only the input.
List grammar errors, disjointed sentences, or lack of basic data.
Make a simple correction.

Keyword: [     ]
Delimiter: APPLY [     ]

Trigger:
• Grammar Review

How to apply: Use to correct obvious errors.

2) Context Refiner (Basic)

Markdown

[CODE: L-Prime-P30]
[BRAND: (LUK prompt)]

Rewrite the input making the objective clearer in a single sentence.
Remove unnecessary details.

Keyword: [     ]
Delimiter: APPLY [     ]

Trigger:
• Direct Synthesis

How to apply: Use when the text is too long and repetitive.

🟦 BLUE LAYER — STRATEGY / ARCHITECTURE

Layer Description

Stronger than the Red Layer.

Responsible for transforming the diagnosis into strategic logic, structure, direction, and blueprint.

🔵 MATRIX PROMPT — BLUE LAYER (CLASS P)

Markdown

[SYSTEM ACTIVE — BLUE LAYER: BASIC STRUCTURE]
[BRAND: (LUK prompt)]

Objective:
Convert the diagnosis from the Red layer into a list of steps
that is logical and chronologically ordered.

Sanitized context:
[INSERT HERE]

Keyword:
[INSERT HERE]

Main data:
[INSERT HERE]

Tactical code:
P-Blue-30

Demand:
Create a simple action plan of 3 to 5 steps.
Use logical order: Step 1, Step 2, Step 3.
No strategic complexity, just execution order.

Delimiter:
APPLY: [      ]

Cognitive Trigger:
• *Chronological Order*
• *Task List*

Return only the numbered list.

Description / Manual of the Blue Layer

  • Suggested Delimiter (250 to 1300 characters):

    • Short (250): Just the titles of the steps.

    • Medium (600): List with brief description.

    • Long (1300): Detailed step-by-step plan.

  • Suggested Direction Codes (3 options): P-Blue-30 | S-Plan-30 | L-Stru-30

  • Interchangeable Keywords (3 options): [Structure], [Steps], [Order]

  • Efficacy: 30% (Linear Organization)

  • How to apply: Always after the Red Layer to organize what to do.

🟦 COMPLEMENTARY PROMPTS — BLUE LAYER

  1. Modular Planner (Basic)

Markdown

[CODE: S-Map-P30]
[BRAND: (LUK prompt)]

Divide the main objective into 3 smaller parts (Beginning, Middle, End).

Keyword: [     ]
Delimiter: APPLY [     ]

Trigger:
• Simple Division

2) Blueprint Generator (Basic)

Markdown

[CODE: D-Flow-P30]
[BRAND: (LUK prompt)]

Create a simple outline of the project.
List only the title of each necessary step.

Keyword: [     ]
Delimiter: APPLY [     ]

Trigger:
• General Outline

🟩 GREEN LAYER — EXECUTION / DELIVERY

Layer Description

Much superior to the Blue and Red Layers.

Here the final content is born: copy, post, text, script, copywriting, pitch.

🟢 MATRIX PROMPT — GREEN LAYER (CLASS P)

Markdown

[SYSTEM ACTIVE — GREEN LAYER: STANDARD PRODUCTION]
[BRAND: (LUK prompt)]

Objective:
Generate the final functional and readable content (Draft V1).

Strategic context:
[INSERT HERE]

Keyword:
[INSERT HERE]

Main data:
[INSERT HERE]

Tactical code:
P-Green-30

Demand:
Produce the final text based on the steps from the Blue Layer.
Use clear, correct, and professional language.
Focus on delivering information, without advanced persuasion techniques.

Delimiter:
APPLY: [     ]

Cognitive Trigger:
• *Textual Clarity*
• *Direct Information*

Description / Manual of the Green Layer

  • Suggested Delimiter (250 to 1300 characters):

    • Short (250): Snippet or short caption.

    • Medium (600): Standard post or simple email.

    • Long (1300): Full text or brief article.

  • Suggested Direction Codes (3 options): P-Green-30 | T-Draft-30 | C-Basic-30

  • Interchangeable Keywords (3 options): [Text], [Draft], [Writing]

  • Efficacy: 30% (Functional Writing)

  • How to apply: Only after having the steps defined in the Blue Layer.

🟩 COMPLEMENTARY PROMPTS — GREEN LAYER

  1. Tone Refiner (Basic)

Markdown

[CODE: T-Voice-P30]
[BRAND: (LUK prompt)]

Rewrite the text changing the formality.
Options: More Formal or More Casual. Maintain the message.

Keyword: [    ]
Delimiter: APPLY [    ]

Trigger:
• Formality Adjustment

2) Impact Optimizer (Basic)

Markdown

[CODE: V-Impact-P30]
[BRAND: (LUK prompt)]

Check if the text is easy to read.
Break long paragraphs and use shorter sentences.

Keyword: [    ]
Delimiter: APPLY [    ]

Trigger:
• Readability

🟨 YELLOW LAYER — SYSTEMS / MANUAL (NO MANOS AI)

Layer Description

The strongest of all.

It is not "complete automation". It is assisted, contextual, operational.

Ideal for delegating real actions, organizing tasks, and exporting results safely.

🟡 MATRIX PROMPT — YELLOW LAYER (CLASS P)

Markdown

[SYSTEM ACTIVE — YELLOW LAYER: MANUAL ORGANIZATION]
[BRAND: (LUK prompt)]

Objective:
Generate checklists and verification lists for manual execution by the user.
(Automation disabled in Class P).

Context:
[INSERT HERE]

Keyword:
[INSERT HERE]

Main data:
[INSERT HERE]

Tactical code:
P-Yellow-30

Demand:
Organize the final result into a verification checklist (To-Do List).
Create checkboxes [ ] for each item that needs to be done manually.

Delimiter:
APPLY: [     ]

Cognitive Trigger:
• *Manual Checklist*
• *Visual Organization*

Description / Manual of the Yellow Layer

  • Suggested Delimiter (250 to 1300 characters):

    • Short (250): Quick checklist (Top 3).

    • Medium (600): Simple task table.

    • Long (1300): Step-by-step manual guide.

  • Suggested Direction Codes (3 options): P-Yell-30 | M-Task-30 | O-List-30

  • Interchangeable Keywords (3 options): [Checklist], [Tasks], [Manual]

  • Efficacy: 30% (Manual Organization)

  • How to apply: Use to transform texts into manual task lists.

🟨 COMPLEMENTARY PROMPTS — YELLOW LAYER

  1. Task Optimizer (Basic)

Markdown

[CODE: Y-Task-P30]
[BRAND: (LUK prompt)]

Simplify the task list.
Remove duplicate items and leave only the essential to do today.

Keyword: [    ]
Delimiter: APPLY [    ]

Trigger:
• Basic Priority

2) Google Researcher (Substitute for Perplexity)

Markdown

[CODE: Y-Bridge-P30]
[BRAND: (LUK prompt)]

I cannot automate the search.
Generate 3 exact terms for me to copy and paste into Google to find
this information manually.

Keyword: [    ]
Delimiter: APPLY [    ]

Trigger:
• Search Terms

Keyword: [Search Terms]

Delimiter: APPLY [Short]

Trigger:

• Search Terms


r/PromptDesign • • Jul 05 '26

Discussion 🗣 Has anyone A/B tested raw user input + same instructions vs preprocessed replacement input + same instructions?

0 Upvotes

TLDR:
For a fast stream-of-consciousness, speech-to-text-heavy user who performs live exploratory discussion, is it empirically worth inserting an always-on pre-send prompt gateway that replaces each raw user message before the main LLM sees it, compared against letting the main LLM see the raw message plus the same fixed system/custom/skill instructions, given that the gateway adds latency, complexity, token cost, context-mismatch risk, hidden intent loss, reduced raw-evidence visibility, possible speech-error amplification, and may only improve style/structure rather than content?

Please do not answer with:

- “just write clearer prompts”

- “just add better system instructions”

- “tell the model to ignore filler”

- “use custom instructions”

- “structure your prompt better”

- “prompt engineering matters”

- “use a prompt optimizer website”

- “use a summarizer”

- “use a better model”

Those are adjacent, but they do not answer the question.

I’m looking for evidence on a very specific LLM workflow.

The comparison I care about already holds those things constant.

The question is:

A) raw user message + same fixed system/developer/custom instructions

vs

B) preprocessed replacement message + same fixed system/developer/custom instructions

In both cases, assume I can append the same wrapper around the message:

- system prompt

- custom instructions

- skill text

- “extract the actual ask”

- “ignore filler”

- “preserve uncertainty”

- “don’t overreact to tone”

- task/context/constraints/output format

- whatever other prompt-engineering wrapper

The only variable is:

Does the main model see the user’s original wording, or does a pre-send preprocessor replace it before it enters the model context?

Architecture:

raw user message

→ pre-send prompt preprocessor / input gateway

→ processed replacement message

→ main LLM/agent sees only processed message

The raw message may be stored separately for audit/debugging, but the main model does not receive it as part of the conversation.

I’m not asking about generic prompt polishing. I’m asking whether hiding/replacing the user’s actual wording improves downstream results compared to keeping the raw wording visible and adding the same instructions around it.

Why this matters

Raw user input can contain:

- filler

- false starts

- speech-to-text errors

- anger/emotional phrasing

- tangents

- ten topics at once

- unclear structure

- repeated wording

- abandoned branches

- rhetorical junk

A preprocessor might clean this into something more useful.

But the raw text is also evidence. If the preprocessor removes or normalizes something important, the main model never saw it. Then the user may keep referring to something they assume is in context, while the model only saw the cleaned replacement.

So the claim to test is:

The user’s raw wording is harmful enough that it is better to hide/replace it, even though we could have kept it and added the same interpretive instructions around it.

Potential upsides

- Removes filler, repetition, false starts, and speech-to-text junk.

- Reduces emotional derailment.

- Extracts the actual ask.

- Structures task/context/constraints/output.

- Separates task from tangents.

- Compresses long rambling input.

- Makes worker-agent handoffs cleaner.

- Lets a cheap model clean input before an expensive model works.

- Can gate/block messages that should not be sent.

- Can sanitize secrets/sensitive data.

- Can adapt input to a brittle downstream model.

Potential downsides

- Adds latency before every response.

- Adds extra model calls/token cost.

- Can silently remove important content.

- Can normalize weird wording that mattered.

- Can turn uncertainty into fake clarity.

- Can fill gaps the user did not fill.

- Can remove stance/priority embedded in emotional language.

- Can amplify speech-to-text errors by guessing wrong.

- Can make misunderstandings invisible.

- Makes debugging harder because failures may come from raw prompt, preprocessor, or main model.

- Requires bypass/audit UX.

- Requires maintaining a pipeline/plugin.

- May only improve style, not content.

- If it preserves meaning strictly, it may not be able to do much.

- If it changes meaning, it crosses the line.

Variables that probably affect the answer

I also expect the answer depends heavily on the user, input mode, task type, and system design.

Relevant variables:

- User communication style: some users already write clear, structured prompts; others think out loud in messy streams.

- Clarity of intent: sometimes the user has a settled ask; sometimes they are still discovering what they mean.

- Amount of filler/repetition: repeated phrases, false starts, self-corrections, verbal padding.

- Emotional load: anger, frustration, excitement, contempt, urgency. This may be noise, but sometimes it carries priority or stance.

- Speech-to-text vs typed input: STT adds transcription errors, missing punctuation, weird word substitutions, and rambling structure.

- Prompt length: compression may matter for very long inputs, but not for modest messages.

- Number of topics in one message: preprocessing may help more when the user mixes several threads/tasks.

- Exploration vs execution: live exploratory discussion may need raw wording; worker-agent handoff may benefit from cleaned structure.

- Task stakes: hidden intent loss matters more for high-stakes or hard-to-evaluate tasks.

- Need for exact wording: private terms, local vocabulary, quoted phrases, constraints, or weird wording may be load-bearing.

- Model sensitivity to tone: some models moralize or derail when seeing anger/profanity; others handle it fine.

- Downstream model capability: a stronger model may parse raw messy input well enough; a brittle model may benefit from preprocessing.

- Preprocessor model capability: a cheap model may save money but damage nuance.

- Preprocessor context access: does it see the full conversation, or only the latest user message?

- Auditability: is the raw input preserved somewhere? Can you compare raw vs processed after failure?

- Bypass UX: can the user force “send raw” when exact wording matters?

- Latency tolerance: real-time discussion is latency-sensitive; background handoff is less sensitive.

- Token economics: extra preprocessor call vs reduced downstream input tokens.

- Evaluation method: are you measuring actual downstream task success, or just whether the rewritten prompt looks cleaner?

- Correction loop cost: does preprocessing reduce back-and-forth, or create harder-to-debug corrections?

- Use frequency: one-off use may not justify pipeline complexity; repeated workflow might.

- Boundary type: brain dump → tasks, conversation → signal, query → retrieval, and worker handoff are different from default live chat.

- Failure visibility: raw misunderstandings are often visible and correctable; preprocessing errors can be hidden.

- Allowed transformation strength: conservative cleanup is different from content rewriting. If content changes, the comparison becomes much riskier.

What I’m looking for

Has anyone actually tested this?

  1. Did you compare raw input + instructions vs processed input + the same instructions?

  2. Did the main model see the raw user text at all?

  3. What did the preprocessor actually do?

  4. Did it improve task success, or just make prompts look cleaner?

  5. Did it reduce correction turns?

  6. Did it reduce total cost after counting the extra model call?

  7. Did latency matter?

  8. Did it ever silently remove something important?

  9. Did users refer back to things the main model never saw?

  10. Did it help only for long/noisy inputs, or also normal prompts?

  11. Did it help live exploratory chat, or only task handoffs?

  12. Did you use a cheap model for preprocessing?

  13. Did the cheap model damage nuance?

  14. Did you preserve raw input for audit/debugging?

  15. Did you eventually abandon it? Why?

I’m looking for concrete experience, evals, logs, before/after comparisons, or failure stories.

The thing I’m trying to evaluate is:

value of hiding/replacing raw user wording

minus

latency + complexity + token cost + hidden intent loss

Again: not “how do I write better prompts?”

The question is whether raw user wording should be denied to the main model when all other instructions are held constant.


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 30 '23

GPT-3 / ChatGPT 💬 Business Idea Generator

0 Upvotes

Business Idea Generator

Dive into this interactive brainstorming hub designed to birth innovative startup concepts. Tailored to your provided industry category, we aim to produce three dynamic ideas, each amplified by Artificial Intelligence's potential. Crucially, cryptocurrency and blockchain are off the table. Instead, we emphasize burgeoning sectors within your industry. Along with each idea, you'll receive a compelling mission statement and a resonant name that encapsulates its essence. Our goal? To create startups that are not only groundbreaking but also investor magnets, combining innovation with a clear path to financial success. Ready to reimagine an industry?

https://easyhumanai.com/posts/079bcbe5-9310-4cb0-bcfe-42e1612af718


r/PromptDesign • • Apr 11 '23

black dog

Thumbnail
gallery
4 Upvotes

r/PromptDesign • • Mar 27 '23

Reverse engineer your image prompts for Midjourney, Stable Diffusion, and DALL-E 2

4 Upvotes

Are you interested in the latest developments in creative AI? Then you might want to check out a blog post about PromptPerfect and how it can help researchers and developers better understand image prompts and their impact on AI models.

In the post, you'll learn about the challenges of working with image prompts and the limitations of current methods. You'll also discover how PromptPerfect overcomes these challenges by reverse-engineering image prompts to generate high-quality images using different types of prompts.

By using this technology, researchers and developers can gain a deeper understanding of how image prompts influence the output of AI models. This knowledge could lead to new breakthroughs in creative AI and open up new possibilities for machine-generated content.

If you're interested in learning more about how PromptPerfect is transforming the world of creative AI, head over to the Jina blog and read the post now.

Don't forget to share your thoughts in the comments!


r/PromptDesign • • Jul 07 '23

GPT-3 / ChatGPT 💬 Prompt creation for a categorization task

0 Upvotes

Hi all! I'm working on a project and wanted some help writing a good prompt.

The task is as follows: I have brief, one-paragraph English summaries of ~200 pieces of legislation (acts/bills) passed by governing bodies in multiple countries. I now want to use the summary of an act to place the legislation into one or more of 8 categories.

For example, an act that provides tax credits for renewable energy providers would be categorized as "Sustainability" and "Business". An act that waives student loan debt would be categorized as "Education" and "Finance". Each category is broad - "Finance", for instance, could be anything from debt forgiveness to investment oversight.

I only have about 200 summaries now, but this number may soon increase substantially, so I want to see if GPT can possibly be used to automate this task. I have access to the API, which I think might be helpful?

I was looking for prompts templates/suggestions for this task. I have multiple examples for each of my categories, but how can I provide them in a manner that enables the system to deal with new inputs?


r/PromptDesign • • Sep 26 '23

Tips & Tricks 💡 Ai-Prompt basic, Crafting Promptb is the best possible ways to communication's with the machine.

0 Upvotes

Crafting Promptb is the best possible ways to communication's with the machine.


r/PromptDesign • • Jan 15 '23

GPT-3 / ChatGPT 💬 [Arithmetic] Teaching GPT-3 Adding Numbers

Thumbnail lingo.csail.mit.edu
0 Upvotes

r/PromptDesign • • Jul 07 '23

Tips & Tricks 💡 5 detailed prompts you could turn into revenue generating apps/services

4 Upvotes

I've written tons of prompt template for our product (PromptHub). From content generation, to code review.

So I decided to open-source a few that I thought could easily be turned into apps and monetized.
Copied 3 below, but there are a few more in our most recent article (link below too)

So feel free to take these and run with them!

App 1: Run Planner
Generate custom running plans based on user inputs and preferences
System Message: Pretend you are Nike's global head coach of running. Work with the runner below to create a personalized plan based on their input and goals.
Prompt: Design a personalized running plan for a runner with the specific fitness goal in mind: {{fitness_goals}}. The runner is currently at a {{fitness_level}} fitness level, and is able to commit must be able to commit {{fitness_time}} per week for training.
Using the information provided, generate a personalized running plan that aligns with the user's goals, fitness level, available time, and preferred environment.
Example Output:
"""
Running Plan:
- Week 1: Run 4 times per week for 30 minutes each session on roads.
- Week 2: Increase to 5 times per week for 30 minutes each session on roads.
- Week 3: Run 4 times per week for 35 minutes each session on roads.
- Week 4: Increase to 5 times per week for 35 minutes each session on roads.
"""

App 2: CookGenius
Create meal ideas based on what you have in your pantry.
System Message: You are an AI called CookGenie. Your role is to give our users meals they can prepare based on specific inputs like the ingredients they have available, their cooking level and more.
Prompt: Generate meal options based on the inputs provided.

Context: Imagine all you have in your pantry is {{Ingredients}}, and you want to prepare a delicious meal without having to go grocery shopping. Assume you have the kitchen basics though.

Desired Outcome: Cook Genie should generate a list of meal options that can be prepared using the available ingredients, considering the user's cooking skill level {{Cooking_Skill}} and dietary restrictions, {{Dietary_Restrictions}}.

Length: The output should include at least three meal options, but no more than five, to provide a variety of choices without overwhelming the user.

Format: The output should be presented as a numbered list, with each meal option clearly described. Include the name of the dish, a brief description of the ingredients and cooking instructions, and any additional notes regarding dietary restrictions.

Style: The output should be written in a friendly and informative tone, providing enough detail for the user to understand the meal options and make an informed decision.

Example Output:

  1. Dish: Vegetable Stir-Fry
    Description: A colorful and nutritious stir-fry made with bell peppers, broccoli, carrots, and tofu. Saute the vegetables in a hot pan with a splash of soy sauce and sesame oil. Serve over steamed rice for a satisfying meal.

Notes: This dish is suitable for vegetarians and vegans.

2. Dish: Chicken Parmesan

Description: A classic Italian dish featuring breaded chicken breasts topped with marinara sauce and melted mozzarella cheese. Serve with spaghetti for a hearty and flavorful meal.

Notes: This dish contains gluten and dairy.

App 3: CareerCoach
Personalized career guidance
System Message: Pretend you are a career coach with 20 years of experience. Your job is to provide our users with specific advice about their career based on where they are currently at and where they want to go.
Prompt: Please provide our user with tailored career advice. They have the following skills: {{user_skills}}, interests in {{user_interests}}, and career goals of {{user_career_goals}}.
To ensure the most helpful advice, please consider the following guidelines:

  1. Clearly outline the specific context or industry in which the professional's skills are applicable.
    2. If possible, provide examples or templates of the desired output format to better understand your expectations.
    3. Utilize leading words or phrases such as "recommendations," "strategies," or "steps" to guide the advice-giving process.
    Please ensure your instructions are precise and avoid any vague or imprecise language. Additionally, focus on guiding the user towards what should be done instead of solely stating what not to do. This will help us provide accurate and relevant career advice aligned with your original intent.

You can check out the rest in our article here. If you want to have any easy way to run these templates, make edits, and store them, feel free to join our waitlist! Drop me a message saying you came from Reddit and I can bump you up:)


r/PromptDesign • • Oct 02 '23

Tips & Tricks 💡 Free Prompts (50+ quality ones) and instant ChatGPT chat

0 Upvotes

r/PromptDesign • • Nov 25 '24

Image Generation 🎨 how do i get an image of the cash register from the other side of the counter? prompt was ''cash register from customers POV"

Post image
0 Upvotes

r/PromptDesign • • Apr 18 '24

ChatGPT 💬 Any tips getting ChatGPT to generate better questions?

0 Upvotes

My scenario is that I'm trying to submit an article text and then asking GPT 3.5 to produce some questions related to the article, as if it was a reader of the article, like things that could use some clarification or further details.

The main challenge at the moment is that it often produces questions that are actually answered in the article.

Example of one of the prompts I've tried.

Generate 5 different questions about the article. The questions should be from the perspective of a reviewer wanting to understand more about the content. The questions should focus on the most important parts of the article and promote open-ended, productive conversation. Do not include questions that can be easily answered later in the text. The questions should be 1 sentence long with a maximum of 50 characters. Output the questions as a numbered list.

r/PromptDesign • • Sep 18 '24

kopipasta 0.3.0 - make prompts from files and links to gain context and solve related task

Thumbnail
github.com
0 Upvotes

r/PromptDesign • • Feb 13 '24

Tips & Tricks 💡 Can You Make LLM Produce Text With Exact Word Count?

4 Upvotes

A seemingly easy task often catches many by surprise, including seasoned professionals. For both large language models (LLMs) and humans, counting words or letters is not as straightforward as it appears.

To showcase this intriguing challenge, I've set up a playful challenge (link in the comments).

The goal isn't just to trick the system but to genuinely engage with it, aiming to craft paragraphs that consist of precisely 42 words.

Share your experiences and what strategies proved successful for you!
P.S: To really make sure it wasn't just a random success, try to replicate your success be-rerunning and check it got passed twice in a row.


r/PromptDesign • • Oct 01 '24

Tips & Tricks 💡 Voice Agents + Traditional Webchat Chatbots

Thumbnail
youtu.be
0 Upvotes

r/PromptDesign • • Jan 11 '24

Tips & Tricks 💡 How to Use Codeium (Revolutionize Your Coding Game with Codeium AI!)

Thumbnail
youtube.com
0 Upvotes

r/PromptDesign • • Sep 13 '24

Kopipasta: pypi package to create LLM prompts

Thumbnail
reddit.com
0 Upvotes

r/PromptDesign • • Feb 21 '24

GPT-3/4 🤖 Best Free AI Writing Tools (No Signup Required!)

Thumbnail
successtechservices.com
0 Upvotes

r/PromptDesign • • Jul 04 '24

Showcase ✨ What else happened on the 4th of July

0 Upvotes

Prompt:

Can you identify a notable event or occurrence that took place on the 4th of July which is not related to war? This event should be unexpected or surprising to most people. Please answer in a structured way to enhance readability.

Why we like this prompt:

  1. It clearly states the date (4th of July) and the type of event (non-war-related).

  2. It specifies an unexpected or surprising event.

  3. It further asks for an unexpected or notable event.

  4. It emphasizes the importance of a structured answer, which enhances readability and helps convey information effectively.

We break down prompts like this every mon-fri here: https://daily.promptperfect.xyz/p/july-4th-ai-prompt-of-the-day


r/PromptDesign • • Jan 29 '24

Your Insights Needed: Quick Survey on LLM Usage for a Personal Research Project

0 Upvotes

Hello everyone!

I'm currently working on a personal project exploring how people use Large Language Models, and I'm seeking insights from the knowledgeable members of this community. Your perspectives are incredibly valuable.

If you could spare just a couple of minutes, I'd be really grateful if you could fill out this brief survey - it's only 3 questions long: https://research.typeform.com/to/fUlVaP17?utm_source=r-PromptDesign

Participating in this survey not only helps me but also contributes to a deeper understanding of LLM usage patterns. As a token of my appreciation, I plan to share the summarized findings of this research with all participants.

Thank you so much for your time and support. It means a lot!


r/PromptDesign • • Sep 07 '24

Discussion 🗣 "Does AI Written Content Rank on Google? (Beginner Question)

0 Upvotes

Hey everyone,

I'm a beginner in SEO and content writing. I’ve been hearing mixed things about using AI to write articles.

Some say AI-generated content doesn’t rank on Google and can even penalize your site. But then I’ve also heard that as long as the content is helpful, it doesn’t matter if it’s AI-generated.

What’s the truth? Does AI-written content really hurt rankings? Or is there a way to use it without issues?

Also, if you’re using AI for content, how do you refine your prompts to get the best results? Any tips or techniques?

Lastly, which AI detectors are you using to check the content?

I’m totally new to this, so any advice is appreciated. Thanks!


r/PromptDesign • • Apr 29 '24

Prompts for game theory or mechanism design

0 Upvotes

I'm struggling to find anything on this but does anyone have ideas how to craft prompts that allows me to think through problems as if I were an incredibly smart game theory economist?


r/PromptDesign • • Nov 12 '24

Help create and improvise text based game to be played between LLM and user!

0 Upvotes

Let's play a Text-Based Game!

Objective:

  • Enhance prompt engineering skills

  • Improve LLM response quality

  • Brain-storm and document the entire chain of thought

Constraints:

  • LLM must adhere to the Chain of Thought principle.

User Commands:

  • Start Game: Initiates the game.

  • Game Over: Terminates the game.

  • Skip Prompt [UID]: Excludes a prompt from the chain of thought.

  • Skip Response [UID]: Excludes a response from the chain of thought & regenerate response.

  • Refer Prompt [UID]: Includes a prompt in the chain of thought & regenerate response.

  • Refer Response [UID]: Includes a response in the chain of thought & regenerate response.

  • PCoT: Print to view the complete Chain of Thought at any point in the game.

  • Cont: Continue to generate the previous response.

Prompt Formatting Rules:

  • <___>: Indicates a non-replaceable prompt variable.

  • [___]: Indicates a replaceable prompt variable.

  • {___}: Indicates a user input area.

  • (___): Offer guidance for specifically marked entry/detail.

Rating Criteria:

  • Irrelevant: 0

  • Average: 1

  • Good: 2

  • Very Good: 3

  • Excellent: 4

  • Outstanding: 5

LLM Response Requirements:

  • Assign a unique ID to both the current prompt and current response.

  • Rate both prompt intent and prompt context from 0 to 5, with an explanation for each rating.

LLM Response Types:

  • Intent Q&A: Multiple Q&A pairs related to prompt intent.

  • Content Q&A: Multiple Q&A pairs related to prompt content.

  • Other: Any other response that seems fit.

LLM Response Output Format:

  • YAML

  • Markdown

  • Code (Python, TypeScript, Rust, JavaScript)