u/Bright-Instruction49

I spent weeks getting wildly inconsistent outputs from Claude. Same prompt, different results every time. Sometimes

brilliant, sometimes generic garbage.

The root cause wasn't the model. It was me.

Here's what I found:

**1. No role = no expertise**

"Write me a marketing email" gets you a generic email.

"You are a direct-response copywriter with 10 years writing B2B cold emails that achieve 8%+ reply rates" gets you

something that actually converts.

Claude activates different knowledge depending on the persona you assign. Generic role = generic output.

**2. Ambiguous task = Claude guesses**

"Write about content marketing" — Claude decides length, format, depth, angle. You get whatever it thinks you want.

Fix: one verb, one goal, one output. "Write a 1,200-word article structured as: intro → 3 H2 sections → CTA."

**3. No constraints = maximum drift**

Without constraints, Claude optimizes for "reasonable" — which means safe, generic, and forgettable.

Add at minimum: what NOT to do. "No filler phrases. No 'In conclusion'. Under 150 words."

**4. Missing format specification**

If you don't define the output structure, Claude invents one. And it changes every run.

Fix: describe exact sections, lengths, and sequence.

The pattern that fixed everything for me:

specific expert with measurable track record

one verb + one goal + one output type

exact structure with lengths

3+ things it must NOT do

Consistency went from ~40% to ~90% once I locked these four elements.

What's the biggest consistency issue you've hit with Claude?

After building and testing hundreds of prompts, the pattern is clear.

Every high-performing prompt has all 6 of these. Every low-performing prompt is missing at least one.

**1. SPECIFIC ROLE** (not "helpful assistant")

The role determines the knowledge base the model draws on.

"You are a helpful assistant" activates generic mode.

"You are a direct-response copywriter with 15 years of experience writing emails for DTC brands" activates specialist mode.

**2. TASK CONTEXT** (not just the instruction)

Claude performs better when it understands WHY.

Include: what this is for, who will read it, what success looks like.

**3. UNAMBIGUOUS TASK** (one action, not three)

"Write and summarize and then suggest improvements" = bad.

One clear verb. One clear objective.

**4. OUTPUT FORMAT DEFINITION** (be obsessively specific)

"A list" is not a format.

"10 bullet points, each under 15 words, starting with an action verb" is.

**5. EXPLICIT CONSTRAINTS** (what NOT to do)

The model needs to know the failure modes to avoid them.

"Don't use corporate jargon" is a constraint.

"Don't exceed 150 words" is a constraint.

**6. VARIABLES** (placeholders for customization)

[COMPANY_NAME], [TARGET_AUDIENCE], [PRODUCT] — these let one prompt serve infinite use cases.

---

The meta-prompt I use to apply all 6 automatically:

---

You are an expert prompt engineer specializing in Claude architecture.

Transform this task description into a production-ready prompt:

TASK: [YOUR_TASK_IN_PLAIN_ENGLISH]

The output prompt must include:

1. A specific expert role (not "helpful assistant")

2. Sufficient context to understand the WHY

3. Unambiguous task instruction (one clear action)

4. Explicit output format (structure, length, sections)

5. 2-3 hard constraints (what NOT to do)

6. Variables in [BRACKET_FORMAT] for customization

Format as a ready-to-use prompt. After the prompt, explain in 2 bullets why you made the key engineering decisions.

---

Full version available if anyone wants it — just comment below.