Chad Thiele's '55 Prompting Strategies' Complete Guide: Applying Writing Techniques to Engineering

• Target Audience: Software Engineers, Backend/Frontend Developers, DevOps Engineers
• Prerequisites: Experience with Git and basic AI tools (ChatGPT, GitHub Copilot, etc.)
• Reading Time: 15 minutes

Overview

On December 4, 2025, Chad Thiele, founder of Chibi AI, shared “55 prompting strategies” on X (formerly Twitter), which quickly gained attention. Originally systematized as prompt strategies for writers, their structure and concepts are directly applicable to software engineering.

This article introduces all 55 strategies and explains how each category can be leveraged in IT engineering work.

Transparency Note: This post was published on December 4, 2025, making it very recent information. Due to its recency, independent secondary source verification has not been possible. The following content is based on the original post but has not undergone academic peer review.

From “Vending Machine” to “Copilot”: Thiele’s Message

Thiele opens his post with this observation¹:

“Most approach AI like a vending machine. Put in a vague request, get disappointing results. The difference isn’t the tool. It’s how you use it.”

This message captures the essence of prompt engineering. Even as AI capabilities improve, without the skill of knowing “what to ask and how to ask it,” you cannot unlock its potential.

flowchart TB
    subgraph Vending["Vending Machine Mindset"]
        A1["Vague Request"]
        A2["Disappointing Results"]
        A1 --> A2
    end

    subgraph Copilot["Copilot Mindset"]
        B1["Structured Dialogue"]
        B2["Valuable Output"]
        B1 --> B2
    end

    Vending --> Copilot

The Big Picture: 6 Categories of 55 Strategies

The 55 strategies are organized into six categories:

flowchart TB
    R["1. RESEARCH & WORLDBUILDING<br/>(10 strategies)"]
    B["2. BRAINSTORMING & IDEATION<br/>(10 strategies)"]
    C["3. CHARACTER DEVELOPMENT<br/>(10 strategies)"]
    P["4. PLOTTING & STRUCTURE<br/>(10 strategies)"]
    D["5. DRAFTING SUPPORT<br/>(7 strategies)"]
    E["6. REVISION & EDITING<br/>(8 strategies)"]

    R --> B
    B --> C
    C --> P
    P --> D
    D --> E
    E -.->|"Feedback"| R

This flow corresponds to the software development lifecycle:

Writing	Engineering
Research & Worldbuilding	Technical Research & Requirements
Brainstorming	Design Exploration & Architecture Selection
Character Development	Persona Design & Stakeholder Analysis
Plotting & Structure	System Design & Failure Scenario Analysis
Drafting Support	Implementation & Documentation
Revision & Editing	Code Review & Refactoring

---

Category 1: RESEARCH & WORLDBUILDING

A category for acquiring expert knowledge in understandable form without jargon.

#	Strategy	Prompt Example
1	Level-Appropriate Explanation	“Explain forensic blood spatter analysis as if teaching a crime novelist who needs accurate details but isn’t a scientist.”
2	Expert Interview	“You’re a medieval blacksmith. Walk me through forging a sword from raw iron. What do I see, smell, hear, and feel at each stage?”
3	Contradicting Perspectives	“Give me three different expert perspectives on whether eyewitness testimony is reliable.”
4	Common Mistakes	“What do most thriller writers get wrong about how the FBI actually operates?”
5	Daily Life Details	“Describe a typical morning for a middle-class woman in 1920s Paris, from waking to leaving the house.”
6	Period-Appropriate Vocabulary	“Give me 30 slang terms actually used by American soldiers in WWI, with definitions and context for each.”
7	Finding Logical Holes	“Here’s my magic system: [details]. What are the potential exploits, contradictions, or unintended consequences I haven’t considered?”
8	Day-in-the-Life Flow	“Walk me through an ER nurse’s 12-hour night shift, including the mundane parts between emergencies.”
9	Cultural Consultation	“What everyday customs might a character from rural Japan find surprising about American grocery stores?”
10	Procedural Breakdown	“Explain exactly how a detective would process a crime scene in a small-town police department with limited resources—step by step, including paperwork.”

Engineering Application

This category directly applies to technical research and requirements understanding.

Explain implementing the Kubernetes Operator pattern
as you would to a senior backend engineer.

Include the following perspectives:
- Common mistakes teams make during implementation (Strategy 4)
- Step-by-step procedural breakdown (Strategy 10)
- Considerations for resource-constrained environments (Strategy 8)

Particularly Useful Strategies:

• Strategy 4 “Common Mistakes”: Anti-pattern research when adopting new technologies
• Strategy 7 “Finding Logical Holes”: Security reviews, edge case analysis
• Strategy 3 “Contradicting Perspectives”: Multi-angle evaluation during technology selection

---

Category 2: BRAINSTORMING & IDEATION

A category for developing ideas in multiple directions.

#	Strategy	Prompt Example
11	Unexpected Combinations	“Give me 10 romance novel premises that incorporate elements of cosmic horror without becoming horror novels.”
12	“Yes, And” Prompting	“Build on this concept in three different directions I might not have considered.”
13	Opposite Approach	“My protagonist is a retired detective. Give me 10 protagonists who could investigate the same mystery but would approach it completely differently.”
14	Escalating Stakes	“Here’s my story premise. Give me five ways the stakes could escalate in act two that I might not expect but would feel inevitable in retrospect.”
15	What-If Variations	“What if my heist story took place during a natural disaster? A pandemic? A power grid failure? Give me specific complications for each scenario.”
16	Thematic Connections	“My novel explores grief. What are 15 unexpected metaphors, symbols, or recurring images that could reinforce this theme without being heavy-handed?”
17	Subverting Expectations	“What are the most common plot beats in cozy mysteries? Now give me interesting ways to subvert each one while still satisfying genre readers.”
18	Constraints as Creative Fuel	“Give me a compelling story premise where the protagonist cannot leave a single room for the entire novel.”
19	Character-Driven Possibilities	“Given this character’s specific wound and desire [details], what are 10 situations that would force them to confront exactly what they’re avoiding?”
20	Tone Variations	“Here’s my scene premise. Show me how the setup would differ if I wanted readers to feel dread versus hope versus dark humor.”

Engineering Application

This category applies to design exploration and failure scenario analysis.

Critique this API endpoint design from three different perspectives (Strategy 13):

1. An architect prioritizing scalability
2. A DevOps engineer prioritizing operational costs
3. A product manager prioritizing development speed

For each perspective, identify design strengths and areas for improvement.
Also consider "what if a major outage occurs?" scenarios (Strategy 15).

Particularly Useful Strategies:

• Strategy 15 “What-If Variations”: Chaos engineering, failure scenario design
• Strategy 18 “Constraints as Creative Fuel”: Architecture design under resource constraints
• Strategy 13 “Opposite Approach”: Alternative architecture exploration

---

Category 3: CHARACTER DEVELOPMENT

A category for psychology-based deep character design.

#	Strategy	Prompt Example
21	Backstory Questionnaire	“Create 25 questions about my character’s childhood, relationships, and formative experiences that would reveal who they are today.”
22	Psychology-Based Profiling	“Based on attachment theory, what relationship patterns would someone develop if they experienced [specific childhood situation]?”
23	Contradictions for Depth	“Give me 10 pairs of contradictory traits that could exist believably in the same person, with brief explanations of how they’d coexist.”
24	Character-Revealing Situations	“What are 20 small, everyday moments that would reveal my character’s personality without requiring dialogue or internal monologue?”
25	Dialogue Patterns	“How would someone with [specific background, education, region, personality] speak differently from the average person?”
26	Relationship Dynamics	“Given these two characters [details], what are 10 specific points of friction and 10 points of unexpected connection?”
27	Secrets and Lies	“Give me 15 secrets a character might keep from their spouse, ranging from trivial to devastating, and the specific fears driving each concealment.”
28	Body Language	“How does someone who grew up in [specific environment] physically carry themselves differently? What unconscious habits would they have?”
29	Wound-Driven Behavior	“If my character’s core wound is [specific trauma], what are 20 small behaviors, avoidances, or overcompensations that might result?”
30	Character Voice Test	“Write the same mundane complaint about traffic in the voices of five different character archetypes.”

Engineering Application

This category applies to persona design and stakeholder analysis.

Analyze this user persona from a behavioral psychology perspective (Strategy 22):

Persona: Startup CTO, 40s, tech-oriented but increasingly occupied with management duties

Consider the following:
- What is this user's "wound" (source of frustration)? (Strategy 29)
- Contradictory desires (e.g., wanting efficiency but also wanting to stay informed on details) (Strategy 23)
- Unconscious habits or biases in decision-making (Strategy 28)

Particularly Useful Strategies:

• Strategy 23 “Contradictions for Depth”: Understanding users’ conflicting needs
• Strategy 26 “Relationship Dynamics”: Team communication analysis
• Strategy 29 “Wound-Driven Behavior”: Deep-diving pain points

---

Category 4: PLOTTING & STRUCTURE

A category for designing causal chains and narrative structure.

#	Strategy	Prompt Example
31	Scene Breakdown	“Break down the three-act structure of a heist story into 15 key scenes, explaining the purpose each serves for tension and character.”
32	Causal Chain	“Given this inciting incident, generate a chain of 10 escalating consequences where each event logically causes the next.”
33	Subplot Possibilities	“Here’s my main plot. What are 10 subplots that could mirror, contrast, or complicate the central theme without feeling disconnected?”
34	Pacing Analysis	“Here’s my chapter outline. Identify where the pacing might flag and suggest specific scene types that could restore momentum.”
35	Reversal Points	“Give me 10 possible midpoint reversals for a story where [premise]. Moments that flip the protagonist’s understanding of their situation.”
36	Time Pressure	“What are 15 different sources of time pressure I could add to my [genre] story that would feel organic rather than manufactured?”
37	Obstacle Brainstorm	“My character wants [goal]. Generate 20 obstacles: 5 external physical, 5 external social, 5 internal psychological, and 5 that combine multiple types.”
38	Ending Variations	“Here’s my story setup. Give me five possible endings ranging from triumphant to tragic, with the thematic implications of each.”
39	Try-Fail Cycles	“My protagonist needs to [objective]. Give me three attempts that fail in different ways, each teaching them something necessary for the eventual success.”
40	Scene Purpose Audit	“For each scene type you suggest, tell me: What does the reader learn? What changes? Why can’t this be cut?”

Engineering Application

This category most directly applies to system design and failure impact analysis.

For this system change, generate a 10-step scenario where failures cascade escalatingly (Strategy 32):

Change: Migrating authentication service to microservices

For each step, include:
1. The problem that occurs (logically caused by the previous problem)
2. Impact scope
3. Detection method
4. Mitigation measures

Also audit the necessity of each failure countermeasure using the lens of
"Can this scene be cut?" (Strategy 40).

Particularly Useful Strategies:

• Strategy 32 “Causal Chain”: Failure cascade analysis
• Strategy 37 “Obstacle Brainstorm”: Risk classification and countermeasure planning
• Strategy 40 “Scene Purpose Audit”: Validating necessity of features/code

---

Category 5: DRAFTING SUPPORT

A category for adding specific details and depth to writing.

#	Strategy	Prompt Example
41	Contextual Synonyms	“Give me 15 alternatives to ‘walked’ that convey exhaustion specifically—not just slowness, but bone-deep tiredness.”
42	Sensory Detail Expansion	“Here’s my sparse scene description. Add specific sensory details for all five senses that would fit this setting and mood.”
43	Transition Options	“I need to move from [scene A] to [scene B]. Give me five different transitional approaches with different effects on pacing.”
44	Description Starters	“Give me 10 different opening images for a chapter set in an abandoned hospital, each establishing a different mood.”
45	Dialogue Alternatives	“Here’s my flat dialogue exchange. Give me five versions where the subtext and tension increase while the surface conversation stays similar.”
46	Metaphor Brainstorm	“Generate 15 fresh metaphors for loneliness that don’t use common comparisons like ‘empty’ or ‘cold’ or ‘isolated.’”
47	Action Beat Variations	“Give me 20 small physical actions a character could do while delivering difficult news, each revealing something different about their emotional state.”

Engineering Application

This category applies to documentation improvement and communication quality enhancement.

This API description is bland (Strategy 42).
Improve it to be more specific and understandable while maintaining technical accuracy:

Original: "This endpoint performs user authentication."

Include:
- Specific use cases (when and why to use it)
- Concrete request/response examples
- The "pain" developers feel when errors occur and solutions

Particularly Useful Strategies:

• Strategy 42 “Sensory Detail Expansion”: Making documentation concrete
• Strategy 43 “Transition Options”: Improving documentation structure
• Strategy 41 “Contextual Synonyms”: Appropriate rephrasing of technical terms

---

Category 6: REVISION & EDITING

A category for improving existing work.

#	Strategy	Prompt Example
48	Specific Feedback Framework	“Analyze this paragraph for: overused words, passive construction, unclear antecedents, and rhythm problems. Be specific about locations.”
49	Concision Suggestions	“Here’s my 200-word paragraph. Show me how to convey the same information in 100 words without losing voice or essential detail.”
50	Consistency Check	“Here’s my character description from chapter 1 and chapter 15. Flag any inconsistencies in physical description, speech patterns, or established traits.”
51	Pacing Diagnosis	“Analyze this scene for pacing. Where does it drag? Where does it rush past moments that deserve more space?”
52	Crutch Word Identification	“Review this chapter and identify my overused words, phrases, and sentence structures. Be ruthless.”
53	Line Edit Options	“Here’s my awkward sentence. Give me five smoother alternatives that preserve the meaning and voice.”
54	Emotional Arc Tracking	“Trace the emotional beats in this chapter. Does the protagonist’s emotional state shift believably? Where are the gaps?”
55	Reader Confusion Prediction	“Read this scene as a first-time reader. What questions would you have? What might confuse you? What assumptions might you make that I didn’t intend?”

Engineering Application

This category directly applies to code review and refactoring.

Review this codebase and identify the following patterns:

1. Overly repeated patterns (Strategy 52: crutch words = DRY violation candidates)
2. Inconsistent naming conventions (Strategy 50: chapter 1 vs chapter 15 inconsistencies)
3. Pacing problems (Strategy 51: overly complex parts and under-explained parts)
4. Points that might confuse first-time developers (Strategy 55)

[Code snippet]

For each issue, specify the exact location and provide improvement suggestions.
Be ruthless.

Particularly Useful Strategies:

• Strategy 50 “Consistency Check”: Code quality, API design consistency
• Strategy 52 “Crutch Word Identification”: DRY violation detection
• Strategy 55 “Reader Confusion Prediction”: Onboarding improvement, documentation quality

---

Summary: Strategy Application Map

Mapping the 55 strategies to engineering work:

Writing Strategy	Engineering Application	Primary Use Cases
Expert Interview	Technical Research	Learning new technologies, understanding architecture
Common Mistakes	Best Practice Verification	Code review, design review
Finding Logical Holes	Security Review	Vulnerability analysis, edge case discovery
What-If Variations	Failure Scenario Design	Chaos engineering, DR planning
Causal Chain	Failure Impact Analysis	Incident response, dependency analysis
Consistency Check	Code Quality Management	API design, naming convention unification
Reader Confusion Prediction	Documentation Improvement	Onboarding, API design
Concision Suggestions	Refactoring	Code simplification, technical debt reduction

As Thiele emphasizes, what matters is not the tool but “how you use it.” These strategies function as a framework for transforming AI dialogue from “vague request → disappointing results” to “structured dialogue → valuable output.”

---

References

About Chad Thiele

Chad Thiele is the founder of Chibi AI, an AI writing tool². He researches and shares methodologies for writers to effectively leverage AI, and these 55 strategies represent the culmination of that work.

1. Chad Thiele (@ChibiChaddeus) - X Post (December 4, 2025). “55 prompting strategies” publication. Organized into 6 categories (RESEARCH & WORLDBUILDING, BRAINSTORMING & IDEATION, CHARACTER DEVELOPMENT, PLOTTING & STRUCTURE, DRAFTING SUPPORT, REVISION & EDITING). Note: Due to the very recent nature of this post, independent secondary source verification is difficult. [Reliability: Medium (verification difficult)] ↩︎

2. Transform your writing with Chad Thiele, Founder of Chibi AI - Ness Labs. About Chad Thiele and Chibi AI. [Reliability: Medium-High] ↩︎