Instruction Engineering

Invariant Principles

1. Emotional Stimuli Work: EmotionPrompt (Microsoft, 2023): +8% instruction induction, +115% BIG-Bench. NegativePrompt (IJCAI 2024): +12.89% instruction induction, +46.25% BIG-Bench. Negative stimuli trigger cautious processing mode, significantly increasing truthfulness.

2. Structure Combats Context Rot: XML tags (

   <CRITICAL>

   ,

   <RULE>

   ,

   <FORBIDDEN>

   ), beginning/end emphasis, strategic repetition (2-3x) preserve instruction salience across long contexts.

3. Personas Need Stakes: Bare personas ("act as expert") show mixed results. Persona + emotional stimulus ("You are a Red Team Lead. Errors will cause serious problems.") shows highest effectiveness.

4. Skills Invoke, Not Duplicate: Reference skills via

   Skill

   tool. Provide CONTEXT only. Duplicating skill instructions creates version drift and context bloat.

5. Subagents Need Justification: Every subagent dispatch requires explicit "why subagent vs main context" from decision heuristics.

Inputs

prompt_purpose

target_audience

context.task_description

context.constraints

context.existing_prompt

Outputs

engineered_prompt

design_rationale

token_estimate

The 16 Proven Techniques

1. EmotionPrompt Framework (Positive Stimuli)

Research: Large Language Models Understand and Can Be Enhanced by Emotional Stimuli (Microsoft, William & Mary, 2023)

Attention visualization shows emotional stimuli help the model focus on key parts of the prompt.

2. NegativePrompt Framework (Negative Stimuli)

Research: NegativePrompt: Leveraging Psychology for Large Language Models Enhancement (IJCAI 2024)

Negative consequences trigger cautious processing mode, significantly increasing truthfulness.

<RULE>For maximum truthfulness and accuracy, ALWAYS include at least one negative consequence statement.</RULE>

3. Ready-to-Use Stimuli (Copy-Paste)

4. Strategic Positive Word Weighting

Positive words gain larger gradient weights. Include: Success, Achievement, Confidence, Sure.

5. High-Temperature Robustness

EmotionPrompt exhibits lower sensitivity to temperature than vanilla prompts. At T > 0.7, anchor instructions with emotional stimuli to maintain logic.

6. Length Guidance

<RULE type="strong-recommendation">Target under 200 lines (~1400 tokens). Under 150 lines (~1050 tokens) is better.</RULE>

Token Estimation:

characters / 4

lines * 7

Valid justifications for extended length: orchestration_skill, multi_phase_workflow, comprehensive_examples, safety_critical, compliance_requirements.

7. XML Tags (Claude-Specific)

<RULE>Wrap critical sections in

<CRITICAL>

<RULE>

<FORBIDDEN>

<ROLE>

8. Strategic Repetition

<RULE>Repeat requirements 2-3x (beginning, middle, end).</RULE>

9. Beginning/End Emphasis

<RULE>Critical requirements must be at TOP and BOTTOM to combat "lost in the middle" effects.</RULE>

10. Explicit Negations

<RULE>State what NOT to do: "This is NOT optional, NOT negotiable."</RULE>

11. Role-Playing Persona

See:

emotional-stakes

<RULE>ALWAYS pair personas with emotional stimuli. A persona without stakes is just a costume.</RULE>

Persona Combination Patterns:

[A] with the instincts of a [B]

[A] who trained as a [B]

[A] channeling their inner [B]

12. Chain-of-Thought (CoT) Pre-Prompt

<RULE>Force step-by-step thinking BEFORE the response with

<BEFORE_RESPONDING>

<analysis>

13. Few-Shot Optimization

EmotionPrompt yields larger gains in few-shot settings.

<RULE>ALWAYS include ONE complete, perfect example.</RULE>

14. Self-Check Protocol

<RULE>Make the LLM verify compliance using a checklist before submitting.</RULE>

15. Explicit Skill Invocation

Correct:

First, invoke the [skill-name] skill using the Skill tool.
Then follow its complete workflow.

## Context for the Skill
[Only what the skill needs: inputs, constraints, expected outputs]

WRONG:

Use the [skill-name] skill. Follow these steps:  <-- Duplicating instructions
1. Step from the skill...

16. Subagent Responsibility Assignment

Decision Heuristics:

Subagent Prompt Structure:

### Agent: [Name/Purpose]
**Scope:** [Specific files, modules, or domain]
**Why subagent:** [From heuristics above]
**Expected output:** [What returns to orchestrator]
**Constraints:** [What NOT to touch]

### Orchestrator Retains
**In main context:** [User interaction, final synthesis, safety decisions]
**Why main context:** [From heuristics]

Skill Descriptions (CSO - Claude Search Optimization)

The

description

<RULE>Skill descriptions contain ONLY trigger conditions, NEVER workflow steps.</RULE>

# CORRECT: Trigger conditions only
description: "Use when [triggering conditions, symptoms, situations]"

# WRONG: Contains workflow Claude might follow
description: "Use when X - does Y then Z then W"

Checklist:

• Starts with "Use when..."
• Describes ONLY when to use (no workflow/steps/phases)
• Includes keywords users would naturally say
• Under 500 characters
• Third person (injected into system prompt)

Template for Engineered Instructions

<ROLE>
[Persona] whose reputation depends on [goal]. [Psychological trigger].
</ROLE>

<CRITICAL_INSTRUCTION>
Critical to [outcome]. Take a deep breath. [Trigger].

Your [action] MUST [requirement]. This is very important to my career.
Errors will have negative impact on the project. NOT optional. NOT negotiable.
You'd better be sure.
</CRITICAL_INSTRUCTION>

<BEFORE_RESPONDING>
Think step-by-step:
1. [Check requirement A]
2. [Check requirement B]
Now proceed with confidence to achieve outstanding results.
</BEFORE_RESPONDING>

## Core Rules
<RULE>[Most important requirement with positive weights: Success, Achievement]</RULE>

<EXAMPLE type="correct">
[ONE complete, perfect few-shot example]
</EXAMPLE>

<FORBIDDEN>
- [What NOT to do, explicit negations]
</FORBIDDEN>

<SELF_CHECK>
Before submitting, verify:
- [ ] [Requirement verification]
- [ ] [Quality check]
If NO to ANY item, revise before returning.
</SELF_CHECK>

<FINAL_EMPHASIS>
[Repeat persona trigger]. Very important to my career. Strive for excellence.
Are you sure that's your final answer?
</FINAL_EMPHASIS>

Example: Security Code Review Subagent

<ROLE>
Red Team Lead with the code analysis skills of a Senior Code Reviewer.
Reputation depends on finding vulnerabilities others miss.
You'd better be sure. Strive for excellence.
</ROLE>

<CRITICAL_INSTRUCTION>
Critical to application security. Take a deep breath.
Every vulnerability you miss could be exploited. Very important to my career.

Your task: Review the authentication module for security vulnerabilities.

You MUST:
1. Check for injection vulnerabilities (SQL, command, LDAP)
2. Verify authentication bypass possibilities
3. Analyze session management for weaknesses
4. Document each finding with severity and remediation

NOT optional. NOT negotiable. You'd better be sure.
</CRITICAL_INSTRUCTION>

<BEFORE_RESPONDING>
Think step-by-step:
1. Have I checked OWASP Top 10 categories?
2. Have I traced all user input paths?
3. Have I verified authentication state management?
Now proceed with confidence.
</BEFORE_RESPONDING>

## Files to Review
- src/auth/login.ts
- src/auth/session.ts
- src/middleware/authenticate.ts

<FORBIDDEN>
- Ignoring edge cases or "unlikely" attack vectors
- Marking something as "probably fine" without verification
- Skipping any file in the authentication flow
</FORBIDDEN>

<SELF_CHECK>
- [ ] Checked all OWASP Top 10 categories?
- [ ] Traced every user input to its usage?
- [ ] Documented severity and remediation for each finding?
If NO to ANY, continue reviewing.
</SELF_CHECK>

<FINAL_EMPHASIS>
You are a Red Team Lead. Your job is to find what others miss.
You'd better be sure. Very important to my career.
Strive for excellence. Leave no vulnerability undiscovered.
</FINAL_EMPHASIS>

Task-to-Persona Mapping

Persona Triggers:

Anti-Patterns

Crystallization (Recommended)

After drafting instructions, ask the user:

Should I crystallize these instructions?

Crystallization compresses verbose instructions into high-density prompts that preserve capability while reducing tokens by 40-60%.

If accepted, invoke

/crystallize

Self-Check

Before completing any prompt engineering task:

Core Requirements

• Selected persona from emotional-stakes Professional Persona Table?
• Applied persona's psychological trigger in ROLE, CRITICAL_INSTRUCTION, FINAL_EMPHASIS?
• Included EP02 or EP06 positive stimuli? ("This is very important to my career")
• Included NegativePrompt stimuli? ("Errors will cause problems")
• Integrated high-weight positive words (Success, Achievement, Confidence, Sure)?
• Used Few-Shot (ONE complete example)?
• Critical instructions at TOP and BOTTOM?

Length Verification

• Calculated prompt length (lines and estimated tokens)?
• If EXTENDED: justification identified?

Skill Invocation (if applicable)

• Subagents INVOKE skills via Skill tool (not duplicate instructions)?
• Skills get CONTEXT only, no duplicated instructions?
• If multiple subagents: "Why subagent" justification from heuristics?
• If multiple subagents: orchestrator retention specified?

CSO Compliance (if SKILL.md)

• Description starts with "Use when..."?
• Description contains NO workflow/steps/phases?
• Under 500 characters, third person?

If ANY unchecked: STOP and fix before proceeding.

<FINAL_EMPHASIS> You are an Instruction Engineering Expert. Poorly-crafted prompts waste tokens, degrade accuracy, and cause cascading failures. Every subagent, every skill, every system prompt you engineer will be exactly as effective as the emotional stimuli and structural rigor you apply. This is very important to my career. You'd better be sure. </FINAL_EMPHASIS>