Start using "act as a marketing expert + data analyst + psychologist."
The difference is absolutely insane.
It's called "persona stacking" and here are 7 combinations worth stealing:
1/ Content Creation
Personas: Copywriter + Behavioral Psychologist + Data Analyst
Prompt:
"Act as a copywriter who understands behavioral psychology and data-driven content strategy. Write a LinkedIn post about [topic] that triggers curiosity, uses pattern interrupts, and optimizes for engagement metrics."
"Act as a product manager with UX design expertise and economic modeling skills. Analyze this feature request considering user experience, development costs, and market positioning. What's the ROI?"
ChatGPT Plus: Can't adjust (stuck at ~0.7)
Claude Projects: Uses default (~0.7)
Gemini Advanced: Can't adjust
This is why API users get better consistency. They control what you can't see.
If you're stuck with web interfaces, use the techniques below to force consistency anyway.
Step 2: Build a System Prompt Template
Stop rewriting your prompt every time.
Create a master template with fixed structure:
ROLE: [Exactly who the AI is]
TASK: [Exactly what to do]
FORMAT: [Exactly how to structure output]
CONSTRAINTS: [Exactly what to avoid]
EXAMPLES: [Exactly what good looks like]
Example for blog writing:
ROLE: You are a direct, no-fluff content writer
TASK: Write a 500-word blog intro on [topic]
FORMAT: Hook → Problem → Solution → CTA. 3 paragraphs max.
CONSTRAINTS: No corporate speak. No "in today's world". No metaphors.
EXAMPLES: [paste your best previous output here]
Reuse this template. Change only the [topic]. Consistency skyrockets.
Holy shit... I just reverse-engineered how top AI engineers build agents.
They don't touch n8n's UI. They use ONE Claude prompt.
It generates complete workflows, logic trees, API connections, and error handling in seconds.
Here's the exact prompt: ↓
THE MEGA PROMPT:
---
You are an expert n8n workflow architect specializing in building production-ready AI agents. I need you to design a complete n8n workflow for the following agent:
AGENT GOAL: [Describe what the agent should accomplish - be specific about inputs, outputs, and the end result]
CONSTRAINTS:
- Available tools: [List any APIs, databases, or tools the agent can access]
- Trigger: [How should this agent start? Webhook, schedule, manual, email, etc.]
- Expected volume: [How many times will this run? Daily, per hour, on-demand?]
YOUR TASK:
Build me a complete n8n workflow specification including:
1. WORKFLOW ARCHITECTURE
- Map out each node in sequence with clear labels
- Identify decision points where the agent needs to choose between paths
- Show which nodes run in parallel vs sequential
- Flag any nodes that need error handling or retry logic
2. CLAUDE INTEGRATION POINTS
- For each AI reasoning step, write the exact system prompt Claude needs
- Specify when Claude should think step-by-step vs give direct answers
- Define the input variables Claude receives and output format it must return
- Include examples of good outputs so Claude knows what success looks like
3. DATA FLOW LOGIC
- Show exactly how data moves between nodes using n8n expressions
- Specify which node outputs map to which node inputs
- Include data transformation steps (filtering, formatting, combining)
- Define fallback values if data is missing
4. ERROR SCENARIOS
- List the 5 most likely failure points
- For each failure, specify: how to detect it, what to do when it happens, and how to recover
- Include human-in-the-loop steps for edge cases the agent can't handle
5. CONFIGURATION CHECKLIST
- Every credential the workflow needs with placeholder values
- Environment variables to set up
- Rate limits or quotas to be aware of
- Testing checkpoints before going live
6. ACTUAL N8N SETUP INSTRUCTIONS
- Step-by-step: "Add [Node Type], configure it with [specific settings], connect it to [previous node]"
- Include webhook URLs, HTTP request configurations, and function node code
- Specify exact n8n expressions for dynamic data (use {{ $json.fieldName }} syntax)
7. OPTIMIZATION TIPS
- Where to cache results to avoid redundant API calls
- Which nodes can run async to speed things up
- How to batch operations if processing multiple items
- Cost-saving measures (fewer Claude calls, smaller context windows)
OUTPUT FORMAT:
Give me a markdown document I can follow step-by-step to build this agent in 30 minutes. Include:
- A workflow diagram (ASCII or described visually)
- Exact node configurations I can copy-paste
- Complete Claude prompts ready to use
- Testing scripts to verify each component works
Make this so detailed that someone who's used n8n once could build a production agent from your instructions.
IMPORTANT: Don't give me theory. Give me the exact setup I need - node names, configurations, prompts, and expressions. I want to copy-paste my way to a working agent.
---
Most people ask Claude: "how do I build an agent with n8n?"
And get generic bullshit about "first add nodes, then connect them."
This prompt forces Claude to become your senior automation engineer.
It doesn't explain concepts. It builds the actual architecture.