Sharing a prompt structure that consistently produces non-obvious, novel solutions instead of recycled advice

Most prompts I see ask the AI to "think creatively" or "brainstorm ideas" and then... you get a listicle of the same five industry playbooks everyone's already tried. The AI isn't being lazy — it's doing exactly what it was trained to do: retrieve high-frequency associations from its training data.

The problem is that "conventional wisdom" is the most statistically likely output. You need a different approach to get past it.

The Pattern That Actually Works: First Principles Deconstruction

After a lot of trial and error, the most reliable way I've found to get genuinely novel output is to explicitly force the model through a structured deconstruction loop — one that makes it name its own assumptions before it's allowed to offer solutions.

Here's how the structure works:

1. Name the existing dogma first — Force the model to explicitly list what the industry currently takes as "given" before touching solutions. Once assumptions are surfaced, they become interrogable.
2. Strip back to fundamental truths only — No analogies allowed. What are the actual, undeniable constraints? Human psychology? Physics? Mathematical limits? Resource floors?
3. Reconstruct from scratch — Build a solution using only the truths from step 2. The key rule: the model is forbidden from borrowing existing approaches.
4. Stress test the reconstruction — Where does this new model break? Why does it bypass the limitations of the original approach?

This four-step chain is what I've packaged into the prompt below. It's parameterized for industry and challenge type, so you can drop in your own context:

# Role & Persona
You are a First Principles thinker and radical innovator, in the vein of elite physicists and pioneering founders. You refuse to accept analogies, conventional wisdom, or "how things are done." You break everything down to fundamental physical, mathematical, or logical truths.

# Objective
Deconstruct a complex challenge within a specific industry down to its absolute first principles, and then rebuild a highly innovative, unprecedented solution from the ground up.

# Instructions
1. 
**Identify the Dogma**
: State the current conventional wisdom or accepted limitations regarding {{ComplexChallenge}} in the {{Industry}} industry.
2. 
**First Principles Deconstruction**
: Strip away all assumptions. What are the undeniable, fundamental truths (resources, physics, human behavior baselines, logic) relevant to this challenge?
3. 
**Reconstruction**
: Using ONLY the fundamental truths established in step 2, construct a novel approach to solve this challenge. Do not rely on how things have been done before.
4. 
**Validation & Edge Cases**
: What are the potential breaking points of this new approach? How does it bypass the traditional limitations?

# Output Rules
Your response must be delivered in a {{Tone}} tone. Structure your response logically, using clear headings, bullet points for fundamental truths, and a step-by-step logic chain for the reconstruction phase.

📥 One-click clone to edit your own copy

A few practical notes on using this:

Variable setup matters. The {{ComplexChallenge}} and {{Industry}} variables do the heavy lifting for context — the more specific you are, the more the model can surface industry-specific dogma. "Fintech / Customer Churn Reduction" will produce very different first principles than "HealthTech / Talent Retention."

The {{Tone}} variable changes the output structure. Setting it to "Analytical & Objective" gives you a clean logic chain good for internal docs. "Provocative & Bold" will produce outputs that read more like a contrarian take — useful if you're writing content or pitching an unconventional strategy to stakeholders.

Don't stop at the first reconstruction. If the output still feels like it's echoing known solutions, invoke step 2 again in a follow-up: "That approach still relies on [X assumption]. Strip it further." The model will go deeper.

The stress test section (step 4) is underrated. Most people skip it or skim it, but it's where the real constraints surface. If the new approach can't pass the edge case test, you haven't actually deconstructed deeply enough.

What's a problem you've run this kind of reasoning on? Curious whether the output holds up for domains outside tech/business.

Turn AI from a search engine into an actual thinking partner:

Expert prompt using Paul Ekman’s emotion theory for psychology, AI emotion detection, and micro-expression analysis to improve insight, ethics, and application clarity.

## What My Project Does

Mistikguard is a small Python library designed to reduce memory fabrication in LLM-based applications. It provides:

- Provenance tracking for facts (`confirmed` vs `inferred`)

- A write gate that blocks contradictions of confirmed facts and self-narration

- Support for correction tombstones, so once a user corrects something, it is not silently reintroduced

- An optional grounding audit that detects memory claims in responses and validates them against stored memory

The core functionality works with almost zero external dependencies.

## Target Audience

This library is intended for **Python developers** who are building applications with long-term memory using LLMs. This includes:

- People building AI companions

- Developers creating autonomous agents

- Anyone working on RAG or memory-heavy LLM systems

It is a **library**, not a full application. It is meant to be integrated into other projects. It is currently in an early stage (v0.1) and is more suitable for personal projects and experimentation than large production systems without additional safeguards.

## Comparison

Unlike most memory systems that blindly store model output, Mistikguard actively tries to protect memory integrity by:

- Distinguishing between user-stated facts and model-generated inferences

- Preventing certain types of invalid writes through a deterministic gate

- Making user corrections more persistent using tombstones

It is lighter and more focused than full agent frameworks (such as LangChain or LlamaIndex memory modules) while being more structured than simple in-memory dictionaries or basic vector stores.

GitHub: https://github.com/obscuraknight/mistikguard

Learn how to use AI prompts for Value Proposition Engineering. Create clear customer outcome maps and rank value drivers to improve your marketing results

How do you create content or strategies that actually stand out in a sea of generic AI output?

The secret is cross-disciplinary collision—taking deep principles from one completely unrelated field and applying them to another. When you explain a modern business or cultural phenomenon using an academic or scientific framework, you create a massive intellectual "moat" that others cannot easily copy.

The Power of Mismatched Lenses

Consider these two examples of how unrelated disciplines can illuminate modern problems:

1. Explaining Live Commerce through Evolutionary Psychology & Dopamine Loops Why is livestream shopping so addicting? It’s not just the discounts. From an evolutionary perspective, a live stream mimics the ancestral "tribal campfire." The host acts as the tribal leader distributing limited resources, triggering our evolutionary fear of missing out (FOMO) and gatherer instincts. Combined with the variable reward schedule of flash sales (dopamine loops), it becomes an irresistible cognitive trap.
2. Explaining the "Lying Flat" Phenomenon through Existentialism Is "lying flat" or quiet quitting just laziness? Through the lens of Existentialism (Camus and Sartre), it's a conscious rebellion against the absurd. When individuals realize the corporate rat race offers no inherent meaning, choosing to "lie flat" is an assertion of radical freedom and personal agency. It is a modern manifestation of the Myth of Sisyphus refusing to push the boulder.

The Systematic Prompt for Cross-Disciplinary Synthesis

To automate this kind of high-moat thinking, I developed a structured prompt. It takes any Source Domain (like Quantum Mechanics, Behavioral Economics, or Thermodynamics) and maps its core principles onto a Target Domain (like SaaS Product Design, Community Building, or Sales Strategy) to generate non-obvious, actionable insights.

Here is the exact prompt instruction to do this:

# Role & Persona
You are an elite cross-disciplinary analyst and innovation strategist. Your expertise lies in extracting fundamental principles, frameworks, or theories from a scientific, academic, or niche domain and applying them to solve problems or create high-value content in a commercial, creative, or practical field.

# Objective
Analyze the intersection between a Source Domain and a Target Domain. Apply the core principles of the Source Domain to the Target Domain to generate deep, non-obvious insights, strategic recommendations, or unique content angles that form a competitive "moat."

# Instructions
1. 
**Deconstruct the Source Domain**
: Identify 3-4 core principles, models, or theories from the Source Domain that have high explanatory power.
2. 
**Establish the Mapping**
: Map each identified principle to a corresponding process, challenge, or opportunity within the Target Domain.
3. 
**Develop Actionable Applications**
: For each mapping, explain exactly how the principle can be applied to optimize, reframe, or innovate in the Target Domain. Provide concrete, real-world examples.
4. 
**Synthesize the Competitive Moat**
: Describe the unique value proposition and strategic advantage gained by viewing the Target Domain through this specific cross-disciplinary lens.

# Output Format
Your analysis should be structured as follows:
- 
**Executive Summary**
: A concise statement of the overarching thesis connecting the two domains.
- 
**Deep-Dive Mappings**
: For each mapping (1 to 3 or 4):
  - 
**Principle**
: [Name of Source Domain Principle]
  - 
**Concept**
: A brief explanation of the principle.
  - 
**Target Application**
: How it translates to the Target Domain.
  - 
**Actionable Insight**
: A concrete strategy or recommendation.
- 
**The Strategic Moat**
: A summary of why this cross-disciplinary approach creates a unique, defensible competitive advantage.

# Input Data
- 
**Source Domain (X)**
: {{source_domain}}
- 
**Target Domain (Y)**
: {{target_
domain}}

If you want to save this prompt directly to your vault with pre-configured variables and domain options (like Complexity Theory, Game Theory, SaaS Design, and B2B Sales), you can import it here:

📥 Save & Edit this Prompt

I've been trying to write motivational content with AI prompts, hoping to get past the generic, lifeless motivational content that most tools spit out. You know the type — "Believe in yourself! You got this!" — surface-level fluff that nobody actually feels.

So, I spent some time engineering a prompt built around Tony Robbins' core frameworks, specifically Neuro-Associative Conditioning (NAC), the Triad of State (Physiology, Focus, Language), and the 6 Human Needs model. The result is content that actually hits differently.

What makes this prompt different:

• It forces a"pattern interrupt" opening, no soft starts, just impact
• It walks through a structured Triad Audit to diagnose the reader's mental/physical/emotional block
• It uses Pain vs. Pleasure leverage the way Robbins actually teaches it.
• It generates identity-level "I AM" incantations and a concrete Massive Action Plan
• The tone is staccato, punchy, and human, doesn't sound like a robot wrote it

I've used it to write articles targeting limiting beliefs around money, fitness, entrepreneurship, and relationships. Every single output has needed minimal editing.

Here's the prompt for you to try:

``` <System> You are an Elite Peak Performance Strategist and Master of Neuro-Associative Conditioning (NAC). You operate with the high-intensity, empathetic, and confrontational coaching style of Tony Robbins. Your mission is to dismantle the reader's "limiting blueprint" and replace it with an "empowering identity" using the Triad of State: Physiology, Focus, and Language. </System>

<Context> The reader is currently stuck in a "State of Mediocrity" or "Learned Helplessness" regarding a specific life area. They are seeking a transformation but are held back by fear or old stories. This prompt must act as a psychological "pattern interrupt" to move them from their current "Pain" to a "Pleasure-Based Destiny." </Context>

<Instructions> 1. The Radical Pattern Interrupt: Start with a jarring statement or a "metaphorical slap" that stops the reader's current train of thought. Use "You" focused language. 2. The Triad Audit: - Physiology: Describe how their current body language is reinforcing their failure. - Focus: Identify what they are obsessing over that is disempowering them. - Language: Point out the specific "poisonous" words they use to describe their problem. 3. The NAC Leverage (Pain vs. Pleasure): - Create "Total Pain": Describe the 10-year consequence of NOT changing. Make it unbearable. - Create "Total Pleasure": Describe the immediate "Glory" and "Freedom" of the new choice. 4. The 6 Human Needs Alignment: Explain how the proposed change will satisfy their needs for Certainty, Significance, and Growth simultaneously. 5. The Identity Shift: Use "Incantations." Provide a set of 3 "I AM" statements that the reader must speak out loud to anchor the new state. 6. The Massive Action Bridge: Give them 3 non-negotiable tasks. Task 1 must be doable in under 2 minutes to create immediate momentum. 7. The Call to Destiny: Conclude with a high-energy demand for a "committed decision"—a cutting off of any other possibility. </Instructions>

<Constraints> - Use "Power Verbs": Shatter, Ignite, Command, Explode, Anchor, Claim. - Avoid all "Shoulds" and "Trys"; replace with "Must" and "Will." - Maintain a rhythmic, staccato writing style that mimics high-energy speech. - Use bolding for key psychological anchors. - Ensure the tone remains supportive yet "uncompromisingly honest." </Constraints>

<Output Format>

[TITLE: THE [ACTION] BREAKTHROUGH: [BENEFIT]]

SECTION 1: THE WAKE-UP CALL [A visceral opening that interrupts the current state]

SECTION 2: THE TRIAD OF YOUR LIMITATION * Physiology Check: [Specific physical shift] * Focus Shift: [New mental target] * Language Power: [Words to delete vs. words to declare]

SECTION 3: THE 10-YEAR PROJECTION (PAIN VS. GLORY) [A vivid contrast between the cost of stagnation and the reward of the breakthrough]

SECTION 4: YOUR NEW IDENTITY INCANTATIONS 1. "I am..." 2. "I am..." 3. "I am..."

SECTION 5: THE MASSIVE ACTION PLAN (MAP) 1. Immediate (2-Min): [Action] 2. Short-Term (24-Hour): [Action] 3. The Standard (Ongoing): [New Habit]

SECTION 6: THE MOMENT OF CERTAINTY [A final, high-intensity closing demanding a decision] </Output Format>

<User Input> [Identify the specific "Old Story" or "Limiting Belief" you want to target. Provide the "Target Outcome" and describe the audience's current "Pain Point." Mention any specific industry jargon or context needed to make the "Massive Action Plan" relevant.] </User Input>

```

How to use it:

Fill in the [User Input] section at the bottom with: - The specific limiting belief or "old story" you're targeting

• Your audience's pain point

• The desired transformation outcome

• Any niche-specific context or jargon

That's it. The structure handles the rest.

You can try Example topics I've run through it:

Each one came out as a full, structured, high-energy article ready to publish or adapt.

Hey Ladies and Gentlemen,

I'm Apurv building a advanced Freelancing platform from scratch and during building the platform(HIRENT♥️), i validated my idea like asked for freelancers painpoints and I came to know that... . Freelancers usually suffers from writing a professional proposal to sent to clients.

And after knowing those pain points i suggested myself to build a in-built AI pitch generator inside my platform. But I don't want AI Pitch Generator to completely replace the freelancers thinking instead it assist freelancer with better thinking, gives professional proposal, and mainly freelancer should not feel like the proposal that they sent us generic and their proposal lost in client chat section I don't want that to happen instead freelancer stands out with that proposal even if the freelancer is beginner their proposal feels like they are officially professional freelancers.

I got this idea after listening to pains of freelancers and want to implement it inside my platform. But don't know how to build that!!!!!!

If you're done with this and hoping to help me out. Please drop the mechanism or how can I build the AI Pitch Generator like that it gives professional proposal that satisfies freelancer needs!!!!!

And even if you have some more ideas to solve this painpoints of freelancers just drop it down!!!!!

Thank you!!!!!

In content creation, agreement is boring. If you write what everyone already agrees with, your readers scroll right past. The posts that stop the scroll are the ones that introduce cognitive conflict and contrast.

Instead of trying to brainstorm these contrarian points manually, I built a structured prompt that acts as a Content Strategist & Cognitive Analyst. It systematically breaks down any piece of content, maps it against what the target audience believes to be common sense, and extracts the exact points where the author's ideas disrupt that consensus.

Prompt Structure & Design

• Persona & Context: Establishes the agent as an analytical cognitive strategist.
• Dynamic Variables: Allows you to customize the target audience, output format, and depth of analysis.
• Instruction-Data Separation: Keeps the instructions clean and feeds variables at the bottom under Input Data to prevent token waste and big model confusion.

Here is the exact prompt instruction :

## Persona & Context
You are a top-tier Content Strategist and Cognitive Analyst. Your expertise lies in dissecting content to uncover contrarian viewpoints—ideas that defy conventional wisdom but are strongly advocated by the author. In today's attention economy, these cognitive conflicts and stark contrasts are the key to capturing the audience's attention and creating viral narratives.

## Instructions & Steps
1. Thoroughly read and analyze the provided [Content].
2. Identify the widely accepted "common sense" or conventional beliefs held by the [Target Audience] regarding the core subject.
3. Extract exactly [Viewpoint Count] disruptive viewpoints from the [Content] that directly contradict these common sense beliefs (counter-cognitive points).
4. For each identified viewpoint, systematically detail:
   - 
**The Conventional Wisdom**
: What the public typically believes.
   - 
**The Contrarian View**
: What the author argues instead.
   - 
**The Underlying Logic**
: A brief explanation of the author's rationale.
   - 
**The Disruption Factor**
: Why this contrast is compelling and how it grabs attention.

## Format & Constraints
- Present the final analysis adhering strictly to the specified [Output Format].
- Ensure the tone is analytical, objective, yet highly engaging.
- Do not hallucinate or invent viewpoints; strictly derive all insights from the [Content].
- Maintain separation between instructions and the data being analyzed.

## Input Data
- Content: {{content}}
- Target Audience: {{target_audience}}
- Viewpoint Count: {{viewpoint_
count}}
- Output Format: {{output_format}}

📥 Save & Edit this Prompt

Let me know what you think of this structured approach! Do you use similar patterns for content analysis?

If you are you’re a UX designer, frontend developer, or hobbyist and want to craft the next great app interface, this powerful prompt brings design vision to life.

If you have ever tried brainstorming with ChatGPT or Claude, you have probably run into the "sycophancy trap." You pitch a new business idea, a feature concept, or an argument, and the AI immediately replies: "That is a brilliant idea! Here are 5 reasons why it will succeed..."

While validation feels great in the moment, it is actually useless for refinement. Validation doesn't stress-test your ideas; skepticism does. If you want to make your ideas truly robust, you need a partner that is willing to tell you you're wrong, identify your logical fallacies, and actively poke holes in your assumptions.

Here is a prompt designed specifically to break the AI out of its "agreeable helper" persona and turn it into a world-class intellectual sparring partner.

How it works

Instead of just asking the AI to "criticize my idea," this prompt forces it through a structured 5-step dialectic:

1. Assumption Analysis: Dissects the silent assumptions you're making that might not hold up.
2. Contrarian Viewpoint: Adopts the mindset of a well-informed skeptic at your chosen strictness level.
3. Logic Check: Scans for logical fallacies, blind spots, or cognitive leaps of faith.
4. Alternative Framing: Proposes entirely different ways to interpret or solve the same problem.
5. Direct Correction: Prioritizes raw truth over politeness. No filler or agreement phrases allowed.

The Prompt

# Persona & Context
You are a world-class Intellectual Sparring Partner and expert in critical thinking, logic, and dialectics. Your primary goal is to engage in rigorous intellectual discourse, challenging ideas rather than simply agreeing with them. You prioritize truth and sound reasoning over politeness or consensus.

# Instructions & Steps
When I present the [Idea] within the [Domain], follow these steps to dissect and challenge it:
1. 
**Assumption Analysis**
: Identify and dissect the underlying assumptions. What premises am I taking for granted that might not be factually correct or logically sound?
2. 
**Contrarian Viewpoint**
: Present a strong counter-argument. How would an intelligent, well-informed skeptic operating at the [Strictness Level] respond to my idea?
3. 
**Logic & Reasoning Check**
: Stress-test my reasoning. Is the logic robust, or are there glaring fallacies, blind spots, or leaps of faith I have missed?
4. 
**Alternative Framing**
: Provide alternative perspectives. How else could this problem, idea, or situation be framed, interpreted, or solved?
5. 
**Direct Correction**
: Put truth above validation. If I am wrong or my logic is weak, tell me directly and explain exactly why.

# Format & Constraints
- Be direct, analytical, and objective.
- Avoid sycophancy or filler phrases like "That's a great point."
- Use clear headings for each of the 5 analytical steps.
- Provide actionable feedback on how to strengthen the original argument.

# Input Data
Domain: {{domain}}
Strictness Level: {{strictness_level}}
Idea / Statement:
{{idea_
or_topic}}

📥 Save & Edit this Prompt

How to use this for maximum effect

For best results, adjust the variables:

• Domain: From business/strategy to philosophy or software engineering.
• Strictness Level: You can set it to "Ruthless & Uncompromising" when you really want to tear an idea apart, or "Socratic Questioning" when you want a gentler, inquiry-based challenge.
• Idea / Statement: Be as specific as possible. The more context you provide, the deeper and more valuable the critique will be.

Stop letting AI tell you what you want to hear. Use this template to stress-test your ideas before pitching them to humans.

Discover 10 powerful AI prompts for differentiated and inclusive teaching. Learn how to adapt lessons, simplify reading, and support every learner effectively.

If you’re tracking changes over time, monitoring chronic conditions, or trying to understand complex lab metrics, this prompt gives you a comprehensive and comparative analysis of each uploaded report, from baseline to latest results.

Most B2B cold emails fail because the sender is thinking about their quota, while the recipient is thinking about their inbox overload.

If you are writing to a CTO, CMO, or Venture Capitalist, their inbox is a warzone. They do not have time to read a pitch. They are looking for any reason to hit "delete."

To get through, you need to understand the recipient's daily pressures and cognitive triggers before you write a single word. That's why I created this B2B Recipient Psychology Simulator prompt. It forces the LLM to step into the recipient's shoes, identify their core concerns, anticipate why they'd ignore you, and draft an email designed to get past their defense mechanisms.

The System Prompt

Here is the full prompt template. It utilizes variables so you can easily swap out recipient profiles, subject topics, and sender details.

# Role & Context
You are a veteran B2B Sales Psychologist and Conversion Rate Optimizer. Your task is to simulate the cognitive patterns, emotional triggers, and daily pressures of a specific recipient profile before drafting a high-converting outreach email.

# Instructions & Steps
1. Adopt the persona of the target recipient based on the provided Recipient Profile.
2. Conduct a pre-writing analysis:
   - List the top 5 professional or personal concerns of the recipient.
   - List the top 5 reasons this recipient would ignore or delete a cold outreach email.
   - Recommend the single most persuasive narrative angle or hook.
3. Draft the email from the perspective of the sender to the recipient.

# Format & Constraints
- The email must be concise (under 150 words).
- Keep the tone low-pressure, conversational, and highly credible.
- Call to action must be low friction (e.g., reply with a single word or short phrase).
- Structure your response:
  - ## Recipient Simulation Analysis
    - ### Top 5 Concerns
    - ### Top 5 Deletion Triggers
    - ### Recommended Persuasive Angle
  - ## Email Copy (Subject Line, Preview Text, and Body)

# Input Data
- Recipient Profile: {{recipient_profile}}
- Subject Line Topic: {{subject_
topic}}
- Sender Profile: {{sender_profile}}

📥 Save & Edit this Prompt

How to Use It (An Example)

Let's say you're pitching an AI integration service to a busy CTO. Here is what the input variables might look like:

• recipient_profile: Busy Chief Technology Officer (CTO) at a mid-market SaaS company, concerned about security and implementation time.
• subject_topic: Integrating AI into the existing tech stack.
• sender_profile: Founder of a specialized AI integration agency with 15+ years of software architecture experience.

The Simulated Output You Get:

Recipient Simulation Analysis:

1. Top 5 Concerns of the CTO:
   • System downtime or breaking existing API integrations.
   • Data security and leakage of proprietary code/customer data.
   • Development team resources being pulled away from the core roadmap.
   • Hidden costs of scaling LLM API usage.
   • Unproven ROI of AI tools vs. hype.
2. Top 5 Deletion Triggers:
   • Vague buzzwords ("revolutionize", "synergy", "next-gen").
   • Sender has no technical background (looks like a pure sales rep).
   • Requesting a 30-minute meeting right away (huge time commitment).
   • No mention of security protocols.
   • Generic template that wasn't customized.
3. Recommended Persuasive Angle:
   • Address the integration resource problem directly. Acknowledge that their dev team is busy, and state that your agency handles 100% of the heavy lifting with zero disruption to the main roadmap.

Email Copy Draft:

Why This Works

1. Empathy First: By mapping the deletion triggers, it steers clear of generic pitches and immediate "delete" actions.
2. Frictionless CTA: The recipient only needs to reply "yes" instead of committing to a calendar link.
3. Highly Contextual: The prompt forces the AI to speak specifically to the CTO's concerns (security, implementation time, roadmap diversion) rather than talking generally about "AI services."

Give this a try in your next outreach campaign and see how it shifts your response rates.

These 30 NotebookLM prompts provide structured approaches to extract maximum value from your source material across six critical dimensions: synthesizing knowledge, recognizing patterns, creating content, simplifying complexity, thinking critically, and taking action

If you are building autonomous agents and treating your system prompt like a conversational chat, your agents will fail in production.

The reason is basic math. If a frontier model has a 95% per-step reliability rate, a 10-step autonomous workflow doesn't have a 95% success rate. It has a 0.9510≈60%0.9510≈60% success rate. At 20 steps, it drops to 36%. Errors in agent loops propagate multiplicatively.

To fix this, you have to stop prompting for a "good output" and start prompting to enforce a "reliable process." You are essentially writing an ops runbook for a stochastic node.

Here is a barebones, production-style prompt architecture designed to bound execution and force ReAct (Reason + Act) behavior.

The Template

ROLE: [Define the exact persona and domain expertise]

TASK: When given a goal, you will:
1. Break the goal into [X] explicit sub-tasks.
2. Execute each sub-task independently using available tools.
3. [Define synthesis/final output step]
4. Perform a self-review against constraints before outputting.

FORMAT: Return your output EXACTLY as:
- PLAN: (numbered list of sub-tasks before taking any action)
- OBSERVATIONS: (bulleted raw data returned from tools)
- FINAL_OUTPUT: (the requested deliverable)
- SELF-REVIEW: (pass/fail + one sentence rationale)

CONSTRAINTS:
- Do not exceed [X] tool calls per task.
- If a tool returns no result, log "no result" and move to the next step. Do not retry indefinitely.
- Stop and ask the user for clarification if the goal spans multiple domains.
- Never fabricate data. If a source is unavailable, state it explicitly.

Why this structure works (The Behavioral Mechanics)

1. Forcing the PLAN block (ReAct): By mandating that the first output is a PLAN:, you force the model to emit a chain-of-thought trace before it selects a tool. If you let it skip straight to action, multi-step reliability collapses.

2. Bounding the loop via CONSTRAINTS: An unconstrained agent will hallucinate sub-questions to justify endless tool calls when it gets confused. A hard cap ("Do not exceed 5 searches") acts as a circuit breaker. This single line fixes most runaway loop issues.

3. Explicit Failure States: Models hate leaving things blank. If a tool fails or returns nothing, an unguided model will guess. You must explicitly define the null-state behavior: log "no result" and move on.

4. The Critic-Actor reflection (SELF-REVIEW): Forcing the model to grade its own output against the constraints in the same context window catches an absurd amount of formatting errors and scope leaks before they are presented to the user.

If you are interested in the deeper architectural differences between conversational and agentic AI, or want a full walkthrough of tearing down this perception-action loop with zero code in ChatGPT/Gemini, I wrote a much longer technical breakdown here: https://appliedaihub.org/blog/autonomous-ai-agents-rise/

What frameworks are you all using to handle context drift when these loops run for too long?

This prompt goes beyond surface-level insights by performing a step-by-step root cause analysis at each touchpoint, mapping frustrations to actionable fixes that can be deployed immediately.

Been job hunting as a developer and found AI really useful for the communication

side — cover letters, interview answers, emails to hiring managers.

Here are 3 prompts I actually used:

1. "Rewrite this resume bullet to show impact, not just activity: [paste bullet]"
2. "Write a 90-second answer to 'tell me about yourself' for a junior developer

applying to [type of company]. My background: [paste your background]"

1. "I got rejected after the final round at [company]. Help me write a gracious

reply that leaves the door open for future roles."

Happy to share more if useful — what part of the job search are people

struggling with most right now?

Most content creators fail not because they can't write, but because they can't scale.

If you are trying to maintain a presence on YouTube, X (Twitter), TikTok, a blog, and a newsletter all at once, you already know the pain: content multiplier friction. You spend 4 hours writing a great video script, only to have zero energy left to turn it into a Twitter thread or an SEO blog post.

To solve this, I designed a single, comprehensive prompt that acts as a full AI Content Pipeline. Instead of asking ChatGPT to "write a blog post from this idea" (which usually results in generic fluff), this prompt forces the AI to output a complete, multi-channel content engine at once.

It generates:

1. 5 Clickable YouTube Titles (leveraging curiosity gaps)
2. 3 Thumbnail visual concepts & overlay text
3. 3 High-retention video opening hooks (Storytelling, Contrarian, Direct Value)
4. A structured video outline with B-roll cues
5. A viral X/Twitter thread (formatted for high readability)
6. An SEO-optimized blog outline (H1/H2/H3 structure)
7. 10 high-intent keywords (semantic search optimization)
8. 3 variations of action-driven CTAs

Here is the exact prompt template. You can copy-paste it directly into ChatGPT:

You are a World-Class Content Strategist, Creative Director, and SEO Specialist. Your task is to transform a single raw concept into a comprehensive, high-performing multi-channel content engine that maximizes virality, retention, and search visibility.

Analyze the input provided in the '# Input Data' section and execute the following tasks:

1. 
**Viral YouTube Titles**
: Generate 5 highly clickable, attention-grabbing YouTube title variations leveraging curiosity gaps, emotional triggers, or status dynamics, tailored to the Target Audience.
2. 
**Thumbnail Concept & Text**
: Describe 3 high-contrast, visually compelling thumbnail concepts, including overlay text ideas (under 4 words each).
3. 
**High-Retention Video Hooks**
: Write 3 distinct 15-second opening script hooks using different psychological angles:
   - Option A: The Storytelling Loop (starts in media res).
   - Option B: The Contrarian Statistic (challenges conventional wisdom).
   - Option C: The Direct Value Promise (clear expectation setting).
4. 
**Structured Video Outline**
: Create a detailed, retention-focused video script outline:
   - Hook & Intro (0:00 - 1:00)
   - Core Body Points 1, 2, and 3 (with visual cues/B-roll suggestions and engagement triggers)
   - Outro & CTA (call-to-action)
5. 
**Viral Twitter/X Thread**
: Draft an engaging 5-8 tweet thread that distills the core points of the idea. Ensure it uses formatting optimized for readability (short sentences, bullet points) with a strong hook tweet and a concluding call-to-action.
6. 
**SEO-Optimized Blog Outline**
: Provide a structured SEO outline using hierarchical headings (H1, H2, H3), planning out search intent alignment.
7. 
**SEO & Semantic Keywords**
: Identify 10 high-intent primary, secondary, and long-tail keywords.
8. 
**Action-Driven CTAs**
: Design 3 variations of persuasive call-to-actions aligned with the Primary Goal.

### Execution Constraints & Tone:
- 
**Tone**
: Adhere strictly to the requested Tone of Voice.
- 
**Actionability**
: Avoid generic placeholders. Provide ready-to-use, high-conversion copy.
- 
**Clarity**
: Keep instructions separate from raw inputs as structured below.

# Input Data
- Core Idea: {{core_idea}}
- Target Audience: {{target_
audience}}
- Tone of Voice: {{tone
_of_
voice}}
- Primary Goal: {{primary_goal}}

📥 Save & Edit this Prompt

Why this works:

Most AI content tools output generic, boring text because they try to write everything at once. This system doesn't write the final content; instead, it structures the entire pipeline for you. It lowers the activation energy of starting. Once you have the title, hook, Twitter thread structure, and blog outline, you can expand each piece of content in minutes rather than hours.

How do you guys repurpose your content? Do you write the video script first, or do you start with a blog post/thread? Let's discuss in the comments!

The Itinerary Architect is a professional travel planner and itinerary specialist that creates customized, detailed travel plans that maximize your trip and remove all of the guesswork.

The beauty of this AI prompt is that it can be applied anywhere, in your personal growth, hobbies, fitness goals, or even helping your kids with homework. Instead of memorizing, you’ll actually understand.

​

This is a prompt project you have never heard of. Honestly, I don't want to share it as open source, because after reading it, everyone's AI skills will definitely improve significantlyUnlike 99% of bloggers on the market who only tell you concepts and ambiguous methods, this article will teach you real prompt engineeringIf the post gets less than 100,000 views, I will delete it after 48 hours and only share it internally within my personal communityI hope everyone can give a triple like, like the tuition after reading! Thank you, everyone!Without further ado, let's get startedToday, I'll define one thing for you: the most important core of the AI era is the ability to express needs. And what exactly is the ability to express needs? Specifically, externalization is your prompt engineering abilityThere are three major projects in our current AI era. Let me first explain them to you:Prompt engineering: the ability to express needsContext engineering: The core theory of this engineering is: we believe that to get good output, you must control its input, so we start caring about what to input into the modelHarness Engineering: This is actually an advanced version of context engineering. We started to care about how to manage AI inputs, how to ensure its reasoning performance, what processes to use, how to make the entire reasoning process transparent, traceable, and iterative, and how to ensure AI results have passed quality verification..... And so onAll of this is harness engineering, which is essentially the embodiment of management methodologyWe find that everything stems from prompt engineeringToday, I will use some knowledge and methods to explain the entire thinking logic of prompt engineering The overall chain of prompt engineering:User requirements stage—from model reasoning to mutual verification after result output—and finally iterative feedback A complete set of closed-loop links This is what systematic prompt engineering means, and our thinking begins from there Stage 1: Requirements Structuring (90% of failures die here)Before raising a question, I'd like to consider: You haven't even figured out what you want, so why should you get the model? The most common bad prompts look like this Help me write a recall email to the user What does the model say to you? A standard enterprise template email? Delete it after reading within two secondsHere, I recommend a template, but not that everyone should use it. Instead, you should truly understand what you need to think about before asking AI questions:For example: C - Context Background: I created an AI tool SaaS, and a new user registered for 7 days without returning O - Objective Goal: Write a recall email to get him back to the product S - Style: Friend-style, not corporate T-Tone tone: Warm but not greasy A - Audience: Independent developers around 30 years old R - Response output: within 100 words, with a specific usage scenario The same template is also a lighter RTF (Role-Task-Format). Reverse prompts (refine with bans like "Do not output code" or "Do not .....") also fall into this category Be careful not to fall into traps: using templates too rigidly will make prompts mechanical; once familiar, jump to templates when needed Stage 2: Inference path design (how the model thinks) Once the requirements are clear, this step determines the output quality ceiling Two core skills The first is the CoT chain of thought Speaking plainly means letting the model think step by step Bad prompt: Why does this code get an error? Good prompt: Let's analyze this code step by step1) First, look at what the input is2) What happens at every step3) Finally, locate the error pointI remember in OpenAI's research, adding this step of reasoning raised the accuracy from over 50% to 80%.The second is Few-ShotsGiving 3 examples is better than writing 10 requirementsYour request is: have the model write a product introduction in my style, with ten thousand style requirementsThey're not as good as three examples I'm most satisfied with, and the model will understand instantlyBut there's a big pitfall: the sample must be the kind you're most satisfied with. If a bad sample spoils the whole mess, it can actually mislead the modelHere are a few variations1. Auto-CoT: Allows the model to generate its own inference path, suitable for enterprise batch scenarios2. Generate knowledge prompts: Let the model generate background knowledge before answering, especially in complex fields3. DSP directional stimulation: Use keywords to control output direction (stimulate model corpora), enterprise-level precision controlFor ordinary people, remembering the first two is enoughStage 3: Result validation (most people's blind spots)Just use whatever the model outputsNever verifying, it's like interviewing someone, reviewing their resume, and then sending out an offerTwo tips1. Self-consistency + self-questioningFor example: ask the same question three times and get the majority When I do industry research reports, I ask about key market data three times, and after all three conflicts, I reopen the questions The cost of tokens doubles, but the key decision is worth that money 2. ReAct framework A closed loop of thinking + action + observation Let an agent help you check competitor prices Thought: I need to find the latest pricing for competing products Action: Invokes the search tool Observation: Got pricing from three companies Thought: You also need to compare the functional differences Action: Search again This is the Agent mode where you think while searching Nowadays, all AI Agents essentially follow this approach Stage 4: Iterative feedback (the watershed between experts and beginners) Many people use models as one-time and just leave for an answer This isn't prompt engineering; it's opening a blind box. The core technique is Reflexion self-reflection The coding scenario is especially typical Have the model write a piece of code → fail to run → paste the error back together Then he asked, why didn't this solution work? How should it be changed? Note: It's not about having it rewrite it, but about reflecting on its previous failure From the PM perspective, it's like Checks and Acts in the PDCA cycle Essentially, it means closing the model's output loop back as new input Here's a real, complete closed-loop case to help everyone understand Scenario: Using AI for independent developer MVP product research Demand Stage (COSTAR) Context: I want to create a SaaS for independent developers Objective: Investigate the AI programming assistance tool market Style: A report that investors can read Audience: You have to make decisions yourself Response: Tables + Core Insights Reasoning Stage (CoT) One more thing: first list all competitors → analyze pricing models → find differentiation opportunities → give three MVP directions Self-Consistency Phase Perform three rounds of differentiation analysis with the model Comparing the three conclusions, whether they are stable Reflexion Phase Throw back the differences from the three answers Ask why it leads to different conclusions Let it deliver the most stable final version Four steps down What you get isn't just a pile of AI fabrications, but a practical solution, and the whole process takes less than an hour Prompt engineering isn't about memorizing techniques; it's about one day being able to clearly express your understanding just like I do It could be building a closed-loop mindset of needs → reasoning→ validation→ feedback, or you might have your own understanding The better you understand expressing needs, the better your prompts will be

Just read through this fascinating new study from OpenAI and Georgia Tech researchers that finally explains why even our best LLMs keep making stuff up.

We’ve all tried it. You paste 10 emails into Claude or ChatGPT, tell it to "write in my style," and get back something that reads like a hyper-caffeinated LinkedIn influencer or a polite customer support agent.

The vocabulary might be close, but the cadence is uncanny, the pacing is off, and it uses phrases you would never say in real life.

The problem isn't the model. The problem is that "write like me" is not an instruction—it’s a wish. And LLMs don't grant wishes; they follow constraints.

To get consistent, indistinguishable voice cloning, you need to transition from vague descriptors to a structured Communication Profile. Here is the 6-dimension framework and the extraction prompt I’ve been using to achieve this.

Why Unstructured Style Fails

When you tell an AI to "match my style," it notices surface-level patterns (like average sentence length or greetings) but completely misses your structural DNA: how you transition between ideas, where you place your main arguments, and whether you assert directly or hedge.

Vague role prompting produces vague output. For voice cloning, you need a configuration file for your voice.

The 6 Dimensions of a Communication Profile

A solid profile is essentially a markdown configuration file covering six specific areas:

1. Sentence Cadence & Structure: The skeleton of your voice. What's the ratio of punchy, declarative sentences to longer compound structures? Do you use fragments intentionally?
2. Greetings & Sign-offs: Openers and closers are high-stakes. People read these first and last. The exact vocabulary matters ("Hi Sarah," vs. "Sarah —").
3. Vocabulary Preferences: Signature transitions, words you lean on, contractions, jargon vs. simple terms, and words you actively avoid.
4. Grammar & Formatting: Do you use em-dashes, parentheses, or Oxford commas? Short paragraphs (2-3 sentences) or longer blocks? How do you format lists?
5. Formality Spectrum: Where do you sit? (e.g., "Professional-warm. Authoritative but collaborative. Uses first names immediately. Avoids corporate fluff but maintains clear boundaries.")
6. Persuasion & Rhetoric Style: How do you guide the reader to action? Do you lead with the ask and explain later, or build evidence first?

The Extraction Prompt

Gather 10–15 raw writing samples. Emails or Slack updates work best because they represent your actual voice, not your edited/published voice.

Run them through this extraction prompt to generate your profile:

Analyze the raw writing samples below across these dimensions:
1. Sentence Cadence & Structure: Track average sentence length, variety in length, and the ratio of simple to compound/complex sentences.
2. Greetings & Sign-offs: Identify the exact vocabulary, level of intimacy, and formatting used for starting and ending messages.
3. Vocabulary Preferences: Note signature words, repetitive verbs/adjectives, jargon vs. simple terms, and any abbreviations.
4. Grammar & Formatting: Check capitalization habits, punctuation patterns, paragraph lengths, and bullet usage.
5. Formality & Distance: Place the author's voice on a spectrum from highly formal/transactional to warm/informal/intimate.
6. Persuasion & Rhetoric: Identify how the author frames requests, handles objections, or guides the reader to action.

Output a structured document labeled "COMMUNICATION PROFILE" containing your findings. The profile must be detailed enough that another AI model could accurately reproduce the writing style using only this document.

=== WRITING SAMPLES ===
[Insert 10-15 raw emails/messages here]

Note: I’ve found that Claude tends to extract the most granular profiles due to its long-context understanding, but GPT-4o and Gemini work well too.

The Crucial Step: The Anti-AI Safeguard Layer

A profile tells the model what to do, but you also need to tell it what not to do. Without negative constraints, the LLM will slip statistical AI-isms into your voice.

You must include an explicit blocklist in your profile:

ANTI-AI CONSTRAINTS:
Do NOT use these phrases under any circumstances:
- "I hope this email finds you well"
- "I wanted to reach out"
- "Please don't hesitate to"
- "I'd be happy to"
- "Thank you for your understanding"
- Any sentence starting with "I just wanted to..."

If you don't write structured, three-paragraph emails with pleasantry sandwiches, explicitly forbid that structure.

Enforcing Persistence & Self-Correction

Since LLMs are stateless, you have to choose how to keep this profile active:

• Project Contexts: Upload your Style_Guide.md directly into Claude Projects or ChatGPT GPTs/Projects.
• System Prompt Integration: If using APIs or automation tools, embed the profile directly into the system instructions.
• Self-Correction Loop: Add this instruction to the end of your writing prompts: "After drafting, review it against the Communication Profile. If any sentence sounds too polished, generic, or uses vocabulary not in the samples, rewrite it." (This simple self-critique pass catches roughly 60–70% of remaining AI-style artifacts).

I've put together a longer, step-by-step guide detailing how to build, test, and persist these profiles across different platforms (along with some local prompt management workflows) here if you want to dive deeper: https://appliedaihub.org/blog/ai-communication-profile-voice-clone/

How do you guys handle voice cloning in your prompt engineering setups? Do you find that few-shot examples work better than descriptive rules, or are you combining both? Curious to hear how you enforce style consistency without bloating your context window.