Chapter 344

Quick Reference (one-paragraph summary)

3 min read

```text Quick Fixes: 1. Provide exact format template 2. Use markdown for structure 3. Specify lengths for each section 4. Give examples of desired format 5. Request specific delimiters

Problem 4: Too Long or Too Short

Symptoms: - Outputs exceed or miss length requirements - Unnecessary verbose or overly terse - Imbalanced section lengths

Diagnosis: Vague or missing length constraints.

Solutions: ```text INEFFECTIVE: Write a brief explanation

EFFECTIVE: Write exactly 150-200 words explaining cloud computing to a small business owner. Structure: Opening hook (20 words), core explanation (100 words), practical benefits (50 words), action step (30 words). ```text Quick Fixes: 1. Specify exact word counts 2. Break down by section lengths 3. Use "maximum" and "minimum" 4. Request "concise" or "comprehensive" 5. Give comparative examples

Problem 5: Wrong Tone or Voice

Symptoms: - Too formal or too casual - Mismatched audience level - Inconsistent voice

Diagnosis: Missing or unclear tone guidance.

Solutions: ```text INEFFECTIVE: Explain quantum computing

EFFECTIVE: Explain quantum computing like you're Bill Nye the Science Guy talking to curious 8th graders. Use analogies they'd understand (video games, sports, social media), maintain enthusiasm without being condescending, and include one "mind-blown" fact. Avoid jargon entirely. ```text Quick Fixes: 1. Reference known personalities 2. Define the audience explicitly 3. Provide tone adjectives 4. Include sample sentences 5. Specify what to avoid

Problem 6: Lacking Depth or Expertise

Symptoms: - Surface-level information only - Missing technical details - Overly simplified

Diagnosis: Prompt doesn't signal required expertise level.

Solutions: ```text INEFFECTIVE: How does machine learning work?

EFFECTIVE: As an ML engineer explaining to a software developer with 5 years experience but no ML background: Detail how gradient descent optimizes neural network weights. Include mathematical intuition (not full equations), code pseudocode, and connect to concepts they know (like database query optimization). ```text Quick Fixes: 1. Specify exact expertise level 2. Reference technical concepts 3. Request specific details 4. Define the audience's background 5. Ask for examples and edge cases

Problem 7: Repetitive Content

Symptoms: - Same points rephrased multiple times - Circular explanations - Redundant examples

Diagnosis: Prompt asks for quantity over quality or lacks variety requirements.

Solutions: ```text INEFFECTIVE: Give me 10 tips for better sleep

EFFECTIVE: Provide 10 distinct sleep improvement strategies, each targeting a different aspect: 1) Light exposure, 2) Temperature regulation, 3) Sound environment, 4) Physical activity timing, 5) Dietary considerations, 6) Mental preparation, 7) Sleep tracking, 8) Bedroom setup, 9) Schedule consistency, 10) Recovery protocols. Make each tip actionable, and unique. ```text Quick Fixes: 1. Request "distinct" or "unique" 2. Specify different categories 3. Number with specific focuses 4. Add "no repetition" instruction 5. Request variety explicitly

Problem 8: Incorrect Facts or Outdated Information

Symptoms: - Wrong data or statistics - Outdated references - Fictional "facts"

Diagnosis: Prompt assumes knowledge without verification or requests speculation.

Solutions: ```text INEFFECTIVE: What are the latest social media statistics?

EFFECTIVE: Based on your training data, what were the social media trends, and user statistics as of your last update? Acknowledge the cutoff date and suggest what types of current data readers should verify independently. Focus on platform comparison patterns that likely remain relevant. ```text Quick Fixes: 1. Acknowledge AI's knowledge cutoff 2. Request patterns over specifics 3. Ask for verification reminders 4. Focus on principles vs. data 5. Request methodology over facts

Problem 9: Inconsistent Quality

Symptoms: - Same prompt gives varying results - Quality fluctuates dramatically - Unpredictable outputs

Diagnosis: Prompt relies too heavily on implicit understanding or uses ambiguous language.

Solutions: ```text INEFFECTIVE: Write something creative about technology

EFFECTIVE: Write a 200-word metaphorical piece comparing smartphone evolution to human evolution. Structure: Opening metaphor (50 words), three parallel developments (100 words), thought-provoking conclusion (50 words). Style: David Attenborough documentary narration. Must include: tool use, communication, social structures. ```text Quick Fixes: 1. Add more constraints 2. Provide clear structure 3. Include must-have elements 4. Define success criteria 5. Give quality examples

Problem 10: Refuses or Misunderstands Request

Symptoms: - AI says it cannot help - Misinterprets ethical concerns - Overthinks restrictions

Diagnosis: Prompt triggers safety filters or uses problematic language.

Solutions: ```text INEFFECTIVE: How do I hack better productivity?

EFFECTIVE: What are advanced productivity techniques used by top performers? Focus on legitimate time management strategies, cognitive optimization methods, and workflow automation tools that enhance efficiency within ethical boundaries. ```text Quick Fixes: 1. Reframe using neutral language 2. Clarify legitimate intent 3. Avoid trigger words 4. Emphasize ethical approach 5. Break into smaller requests