In 2025, I wrote a series called The Elements of Artificial Intelligence—Strunk and White’s The Elements of Style, but for using AI. This page holds the most updated guide, last updated June 2026. If you like it, check out my home page and newsletter. ![]()
The Elements of Artificial Intelligence
How to use AI well.
by Brady Gerber
Author’s note: This guide was created with the assistance of Claude, ChatGPT, and Cursor. Thanks to Sam—you were right.
Table of Contents
The Core Guide
- Foreword
- Introduction
- Getting Started
- I: Elementary Rules of AI Usage
- II: Elementary Principles of AI Interaction
- III: A Few Matters of AI Form
- IV: AI Concepts Commonly Misunderstood
- V: An Approach to AI Philosophy
Bonus Chapters
- VI: When Not to Use AI
- VII: Case Studies
- VIII: Quick Reference Guide
- IX: AI for Software Development
- X: Advanced Techniques for Experienced AI Users
- XI: Visual Examples and Templates
Foreword
My favorite rule in this guide is No. 10: “Be a Person.”
You—not the AI—will get blamed for using AI irresponsibly.
Consider this: You ask AI to write an email to your boss. It sounds professional and good enough. You send it. Later, you realize the AI included a completely fabricated statistic. Who does the boss blame for including fake data and pressing send? Hint: It won’t be the AI.
Introduction
AI is wonderful, and it stinks.
AI is easy and accessible. It removes gatekeeping for anyone trying to learn or practice skills such as writing or coding. Experienced software engineers can now generate a working React component, debug a complex SQL query, or draft a technical spec in minutes instead of hours. And you’ve been using AI longer than you realize: autocomplete, search rankings, spam filters, GPS routes, and more. What’s new in AI is the interface—and the marketing.
AI is also biased. It can be clunky. It confidently generates broken code, hallucinates API endpoints, and introduces subtle bugs that pass code review. It’s trained on data with a cutoff date and has no concept of your specific architecture, constraints, or business logic. There’s also the fear that AI will replace you. The fear is not unwarranted. When it comes to the bottom line, even the most sympathetic companies will choose “good enough” over “great” if it saves them money. AI is now “good enough” compared to experienced—”great”—professionals. And yes, these tools still need a lot of supervision.
The problem isn’t just the technology. The problem is that most people treat AI like a search engine.
Whether you like it or not, you need AI fluency now more than ever. This guide is for people like you and me: people who didn’t ask to need it.
That doesn’t mean it has to be hard or boring.
The overused “AI is an intern” metaphor
Still: AI is like a very well-read intern drinks infinite amounts of coffee (and water), never sleeps, and is so excited to help that it’ll sometimes forget to fact-check its work—or literally make things up to impress you. Make peace with this intern. And remember what an intern can’t and shouldn’t do.
This intern continues to get faster and more capable with each passing day. The need for oversight hasn’t gone away.
The Strunk and White of it all
As the title hints, this guide is modeled after William Strunk Jr. and E.B. White’s The Elements of Style—short and useful. Like that little book, this guide won’t cover everything. The goal isn’t mastery. The goal is mindfulness.
Getting Started
Choose Your AI Tool
Most people start with one of these
- ChatGPT (by OpenAI): Go to chat.openai.com and create a free account.
- Claude (by Anthropic): Go to claude.ai and create a free account.
- Gemini (by Google): Google’s assistant, deeply integrated with Gmail, Google Docs, and Drive. Best if you already live in Google’s ecosystem.
- Copilot (by Microsoft): Embedded into Windows 11, Microsoft 365, Edge, and Teams. Best if your work runs on Microsoft’s stack.
Cost expectations: Free tiers handle most beginner needs. Paid versions (typically $20/month for individuals) unlock more powerful reasoning models, higher message limits, and advanced features like image generation.
Your First Interaction
- Sign up for your chosen platform
- Find the chat box (usually prominently displayed)
- Start simple: Type something like “Hello! Tell me a joke.”
- Try a practical task: “Help me write a polite email declining a meeting invitation.”
What to Expect
- Response time: Usually 5-30 seconds, depending on the request
- Length: AI often writes more than you expect—you can ask it to be shorter
- Accuracy: Good for general help, but always double-check important facts
- Interface: Most AI tools work like text messaging—just type and press enter
I. Elementary Rules of AI Usage
1. Don’t Lie
Be transparent about your AI use. You’re probably not good at hiding it.
At the very least, don’t actively deceive people about your AI use.
Don’t lie. It’s not worth it.
2. Verify Outputs Before Sharing or Using
“Plausible” is not “factual.”
- Plausible: The Berlin Wall fell in 1988.
- Factual: The Berlin Wall fell in 1989.
Facts and figures: Cross-reference with established sources. Be especially careful with recent events—AI training has cutoff dates.
Professional content: Have a colleague review AI-generated reports or presentations. Test suggestions in low-risk situations.
Code or technical instructions: Test in a safe environment before deploying. Check for deprecated APIs, security vulnerabilities, and edge cases that the AI likely didn’t consider.
Red Flags to Watch For
- Overly confident statements about controversial topics
- Statistics without sources
- Technical instructions that seem too simple
- Historical dates or facts that sound right, but you’re unsure of
3. Provide Clear, Specific Prompts with Relevant Context
Garbage in, garbage out. Vague prompts produce vague results.
- Bad: Where should I eat in Chicago?
- Good: I’m visiting Chicago for the first time this summer and love Indian food. Any recommendations near public transit? Budget: $100 max per meal.
4. Use Literal Examples
Show, don’t tell.
- Bad: Help me write this email in a conversational tone.
- Good: Help me write this email in a conversational tone, like this: “Here’s the thing about remote work—it’s not for everyone, but when it works, it really works.”
5. Break Complex Requests into Steps
Large requests produce unfocused results. Divide your work into manageable phases.
- Bad: Create a complete marketing strategy for my new app.
- Good: First, help me identify three key user personas for my productivity app. Then, help me develop messaging for each persona.
6. Specify Your Desired Format
Your AI isn’t going to know otherwise.
- Bad: Summarize this report.
- Good: Summarize this report in three bullet points, each focusing on each department’s performance.
7. Set Constraints
Even if you don’t know exactly what you want, knowing what you don’t want helps.
- Bad: Explain quantum computing.
- Good: Explain quantum computing in exactly 200 words, using no technical jargon, with one concrete analogy, speaking as if you’re talking to a five-year-old.
8. Iterate, Refine
Good writing is good editing. Same with AI. Never accept the first response if you’re not satisfied.
Some helpful refinement prompts:
- “Make this more concise.”
- “Read my tailored resume text as if you’re a harsh yet experienced HR professional looking for a reason to say no.”
- “Rewrite this memo for an older audience.”
9. Understand Your AI’s Limitations
What AI Does Well
- Creative drafting: copy, brainstorming, generating variations
- Pattern recognition: Analyzing, summarizing, identifying themes
- Busy work: Formatting, basic translations
- Learning assistance: Explaining concepts, creating practice questions
What AI Struggles With
- Current events and real-time information
- Personal or private information that can’t be accessed
- Complex multi-step math
- Nuanced judgment requiring lived experience
AI vs Search Engines
Despite what AI companies would like you to believe, chatbots are not a replacement for search engines.
- Use AI for: busy work tasks, brainstorming, explaining concepts, analyzing text you provide
- Use search engines for: Current events, real-time information, specific recent facts
Remember How AI is Trained
Most LLMs have training cutoffs. They might suggest a framework from 2023 when a better option exists from 2025. Be mindful of what’s overrepresented in training data (popular frameworks, common patterns) and what isn’t (your company’s specific architecture, recent releases, edge cases).
10. Be a Person
You—not the AI—will get blamed for using AI irresponsibly.
II. Elementary Principles of AI Interaction
11. Start Conversations with Context, not Commands
- Bad: Write a press release.
- Good: I’m the marketing director for a 50-person software company. We’re announcing a new integration with a new software that will help our customers sync data more easily. I need a press release for tech industry publications.
12. Build Conversations Progressively
Each exchange should build upon the last. Think of AI conversations as collaborative work sessions, rather than isolated requests. Reference previous parts of your conversation and build complexity gradually.
13. Ask for Explanations, Not Just Answers
Understanding beats memorization.
- Bad: What’s the best pricing strategy?
- Good: What are three pricing strategies for a new SaaS product? What factors would determine which one to choose?
14. Use AI for Brainstorming, Humans for Decisions
Generate options, then you choose. As mentioned in Rule No. 10: You will get blamed if you use bad AI-generated content. You might as well do it right the first time.
15. Document your Successful Prompts
Build a personal prompt library that you can copy and paste.
- Save what works, and note the context it worked in
- Create templates by replacing specifics with [brackets]
- Organize by purpose: writing, analysis, creative, etc.
- Refine prompts that almost worked; delete ones that consistently fail
16. Test AI Outputs with Real Scenarios
Ask yourself: Would this actually work in my situation? If not, say so.
- Example: “This email template assumes that we have a formal relationship with clients, but our company culture is very casual. Can you adjust the tone?”
17. Request Multiple Perspectives
Intentionally ask for counterarguments and alternative viewpoints.
- Example: “Present three different perspectives on implementing AI in customer service—from management who is worried about next quarter’s earnings, jaded employees who think AI is a fad, and customers who think AI results are sloppy.”
18. Challenge AI Responses
AI systems don’t have feelings that you can hurt. Push back on responses that seem incomplete or questionable.
- Example: “What evidence supports this? What are the potential downsides? What assumptions are you making? How would someone disagree with this?”
19. Structure Complex Projects in Phases
Break large projects into discrete phases: planning, research, drafting, refining. This gives you more control and prevents AI from trying to do everything at once.
20. Know When to Stop and Switch to Human Expertise
When you need specialized knowledge, sensitive judgment, or accountability for important decisions, consult human experts. Remember: if AI trains on work created by human experts, it’s better to go directly to the source when you can. This goes back to our core principle of Rule No. 10: You remain responsible for the output.
Common Beginner Mistakes
- Treating AI like Google: Asking for current information instead of help with thinking and writing
- Being too vague: “Help me with my project” instead of specific, contextual requests
- Accepting first answers: Not iterating or refining when the output isn’t quite right
- Over-relying: Using AI for everything instead of building complementary skills
- Under-explaining context: Forgetting that AI doesn’t know your situation, company, or personal preferences
III. A Few Matters of AI Form
Citation and Attribution
The level of stated attribution should match the level of AI contribution and your professional context.
Examples:
- Light editing: This text was reviewed with AI assistance
- Substantial generation: This content was developed in collaboration with AI, then reviewed and edited
- Research assistance: AI tools were used to gather initial research, which was then verified and supplemented
Privacy and Data Handling
Assume Zero Privacy
Every prompt you send to AI services is potentially:
- Vulnerable to data breaches
- Stored indefinitely by the AI company
- Used for model training (unless you’re on enterprise plans with specific guarantees)
- Accessible to employees for quality assurance
Never share:
- Production credentials, API keys, passwords
- Real customer data, PII, or sensitive business information
- Proprietary algorithms or competitive intelligence
- Security vulnerability details from your systems
Enterprise Considerations
- Use AI services with BAAs (Business Associate Agreements) for healthcare
- Implement AI usage policies for your team
- Consider on-premise LLM deployments for sensitive work
- Monitor AI service terms of service changes
Effective Prompt Structure
Not everything needs to be written in paragraph form. Structure can improve clarity.
Example A
- CONTEXT: [Background information]
- TASK: [Specific request]
- FORMAT: [Output requirements]
- EXAMPLES: [Sample inputs/outputs]
Example B
- ROLE: Act as a [specific role]
- GOAL: Help me [specific objective]
- CONSTRAINTS: Keep it under [X] words, avoid [Y], focus on [Z]
Backup and Fallback Strategies
When AI tools fail or are unavailable, you should still be able to do your work. Don’t become dependent on any single AI system. Maintain your underlying skills.
Remember Rule No. 10.
IV. AI Concepts Commonly Misunderstood
Artificial General Intelligence (AGI)
True AGI—AI that matches or exceeds human intelligence across all domains—does not currently exist. Today’s AI systems are specialized tools with narrow capabilities. Think of current AI like a brilliant specialist doctor who only knows one field extremely well. True AGI would be a doctor equally expert in surgery, psychiatry, pediatrics, and research—all at once. We don’t have that yet.
AI vs. Machine Learning vs. Deep Learning
- AI: The broad field of creating intelligent systems — the whole hospital
- Machine learning: A subset of AI that learns patterns from data — the medical training program
- Deep learning: A subset of ML using neural networks — advanced specialist training
Hallucination
When AI generates false information and presents it with confidence. AI doesn’t know it’s making things up—it’s predicting what sounds right based on patterns. Overconfident errors remain common enough to warrant skepticism.
Not that this idea is new: Humans have been presenting false information with confidence for centuries.
Bias in AI Systems
AI systems reflect and can amplify biases in their training data: cultural, demographic, professional, ideological. Imagine learning everything about cooking from only Italian cookbooks. Great Italian advice, blind spots everywhere else.
Large Language Models (LLMs)
AI systems trained on vast amounts of text to understand and generate human language. They predict the next likely words based on patterns. They don’t truly “understand” language in the human sense — they’re sophisticated pattern-matching systems.
Think of LLMs like autocomplete on steroids. Your phone’s keyboard predicts your next word; LLMs do it after reading billions of books, articles, and websites.
Tokens
The basic units AI uses to process text—roughly 0.75 words per token (100 tokens ≈ 75 words). Think of tokens like a data limit. AI has a “token limit”—how much text it can consider at once. Hit the limit, and it starts forgetting the beginning of your conversation.
Temperature
Parameters that control randomness in AI outputs. The typical range is from 0.1 to 2.0. It’s like a creativity dial:
- Low temperature (0.1-0.3): Like a careful accountant—consistent, predictable, conservative
- High temperature (1.5-2.0): Like an improvisational jazz musician—creative, unpredictable, sometimes brilliant, sometimes nonsensical
Context Window
The amount of text an AI can consider simultaneously—its short-term memory. Measured in tokens rather than time, but the limitation is analogous to a person who remembers the last few minutes of conversation clearly but struggles with details from three hours ago.
V. An Approach to AI Philosophy
Maintain Intellectual Honesty and Integrity
Don’t claim AI work as entirely your own. Don’t diminish your genuine contributions, either.
Preserve Human Agency and Judgment
Keep humans in control of important decisions. AI should inform and support human decision-making, not replace it, especially for choices that affect other people or have significant consequences.
Stay Curious About How AI Works
You don’t need to understand the technical details, but having a basic grasp of AI’s capabilities and limitations makes you a more effective user.
Question AI Outputs Actively, not Passively
Skepticism is a feature, not a bug.
Use AI to Amplify Human Creativity, not Replace It
AI works best when it enhances and expands human imagination rather than substituting for it.
Consider the Environmental Impact of Your AI Use
AI systems require significant computational resources and energy. More AI isn’t always better AI.
Respect Privacy Boundaries
Always protect personal information and respect others’ data rights.
Adapt as AI Evolves
What works today may not work tomorrow. Stay flexible.
Remember: AI Serves Human Purposes
We use technology to improve our lives and solve problems. We don’t live to serve technology.
Practice Digital Minimalism
Use AI when it adds genuine value … but otherwise, do you need it?
Cultivate Human Skills AI Can’t Replicate
Emotional intelligence, creative judgment, interpersonal communication, ethical reasoning, strategic thinking … but really, for the sake of your sanity, learn a skill or hobby that doesn’t require an Internet connection or a screen.
Recognize AI’s Cultural Limitations
AI systems reflect the perspectives and biases of their training data and creators. Be aware of whose voices are included and whose might be missing.
Use AI to Learn, not to Avoid Learning
Use AI as a learning tool, not a crutch.
AI Ethics and Responsibility
- Transparency: Be clear about AI use in your work.
- Accountability: Take responsibility for AI-generated content.
- Fairness: Consider how AI outputs might affect different groups.
- Privacy: Protect personal information and respect data rights.
- Bias awareness: Actively look for and address biases in AI outputs.
- Human oversight: Maintain human control over critical decisions.
VI. When NOT to Use AI
Privacy and Security Concerns
Assume everything you tell AI will be stored, analyzed, and potentially exposed.
Never share:
- Personal identifying information
- Financial data or account credentials
- Proprietary business information
- Confidential client data
- Medical or legal information
- Passwords or API keys
Real-Time Decision Making
AI is not suitable for:
- Emergencies requiring immediate action
- Time-critical decisions with high stakes
- Situations where you need to act faster than you can type
Situations Requiring Perfect Accuracy
AI is probabilistic, not deterministic. Don’t use it for:
- Financial calculations that must be exact
- Medical diagnoses or treatment decisions
- Legal advice or contract interpretation
- Safety-critical system design
- Any task where 99% accuracy isn’t good enough
Creative Work That Must Be Uniquely Human
Remember Rule No. 10.
Avoid AI for:
- Personal artistic expression
- Work that represents your unique voice
- Projects where authenticity is more important than efficiency
When You Need to Learn, Not Just Get Answers
AI can be counterproductive when:
- You’re trying to understand fundamental concepts
- You need to develop your own problem-solving skills
- The learning process is more valuable than the result
- You’re building foundational knowledge in a field
When Human Judgment and Intuition Matter Most
AI struggles with:
- Nuanced social situations
- Context-dependent decisions
- Situations requiring emotional intelligence
- Tasks that benefit from human creativity and intuition
Remember
AI is a tool, not a replacement for thinking. Your judgment about when to use AI is as important as how you use it. Sometimes, the best use of AI is not to use it.
VII. Case Studies
A few examples of when using AI helps, and when using AI backfires.
Case Study 1: The Lawyer Who Trusted AI Too Much
A lawyer used ChatGPT to research legal precedents for a court filing. The AI generated six fake court cases with plausible-sounding names and citations. The lawyer didn’t verify them before submitting. The judge discovered the fake cases, fined the lawyer $5,000, and dismissed the case.
Lesson: Always verify AI-generated information, especially when accuracy is critical. Use AI for initial research, then confirm through authoritative sources.
Case Study 2: The Marketing Team’s AI Success
A marketing team used AI to generate 50 email subject lines for an A/B test, then used AI to predict which would perform best. They validated predictions against real performance data, found 80% accuracy, and saw email open rates increase 35%.
Lesson: AI excels at pattern recognition and optimization when you validate its suggestions with real data.
Case Study 3: The Student’s Plagiarism Problem
A student used AI to write an essay, submitted it as their own, and didn’t realize their school’s policy required disclosure. The result: a failing grade and academic probation.
Lesson: Understand your organization’s AI usage policies. Use AI for brainstorming and structure, write the final content yourself, and disclose AI assistance as required.
Case Study 4: The Developer’s Debugging Breakthrough
A developer spent three days on a complex bug, then asked AI to analyze the code with the error message. The AI identified the issue in 30 seconds and provided a working solution.
Lesson: AI accelerates problem-solving dramatically when you provide clear context and specific error information.
Case Study 5: The Content Creator’s AI Dilemma
A content creator used AI for the entire writing process and found the results sounded generic. The fix: use AI for research, outlines, and initial drafts — then rewrite everything in their own voice. Content production increased 40% while maintaining an authentic voice and audience engagement.
Lesson: Use AI for the parts of your process where you struggle. Maintain control over final creative output.
Case Study 6: The Business Analyst’s Data Disaster
A business analyst used AI to analyze customer data without verifying the AI’s understanding of the data structure. The AI made incorrect assumptions. The company made poor strategic decisions based on flawed analysis.
Lesson: Provide clear data context, verify the AI’s assumptions with sample data, and cross-check AI insights with traditional analysis.
VIII. Quick Reference Guide
Beginners
- Start simple: “Help me write a professional email.”
- Be specific: Include context, constraints, and desired format
- Verify everything: Fact-check AI outputs before using them
- Be honest: Don’t lie about your AI usage
Intermediate Users
- Build conversations: Use follow-up prompts to refine outputs
- Document success: Save effective prompts for reuse
- Test scenarios: Ask “Would this work in my situation?”
- Challenge assumptions: Ask for evidence and counterarguments
Advanced Users
- Chain prompts: Break complex tasks into sequential steps
- Use examples: Provide sample inputs/outputs for better results
- Manage context: Start fresh conversations for new topics
- Combine tools: Use multiple AI systems for different tasks
Red Flags to Watch For
- Overconfidence: AI sounds certain about uncertain topics
- Outdated information: Claims about current events or recent developments
- Inconsistent logic: Contradictory statements within the same response
- Generic advice: Vague suggestions that don’t apply to your situation
- Missing context: Responses that ignore important details you provided
When to Stop and Ask a Human
- High-stakes decisions: Financial, medical, legal, or safety matters
- Personal judgment calls: Situations requiring emotional intelligence
- Creative authenticity: Work that represents your unique voice
- Learning fundamentals: When you need to understand, not just get answers
- Privacy concerns: Any situation involving sensitive information
IX. AI for Software Development
Code Review and Analysis
- Bad: Review this code
- Good: Review this Python function for performance issues, security vulnerabilities, and adherence to PEP 8 standards. Focus on the database query optimization.
Debugging Assistance
- Bad: Why isn’t this working?
- Good: I’m getting a ‘TypeError: ‘NoneType’ object is not iterable’ error in this function. Here’s the full traceback and the function code. What’s the most likely cause?
Documentation Generation
- Bad: Write documentation for this function
- Good: Generate JSDoc documentation for this JavaScript function that handles user authentication, including parameter types, return values, and usage examples.
Testing Strategy Development
- Bad: Write tests for this
- Good: Suggest unit tests for this React component. Focus on edge cases for the form validation logic and user interaction scenarios.
Architecture Discussions
- Bad: What’s the best architecture?
- Good: Compare microservices vs. monolithic architecture for a social media app with 10,000 users. Consider scalability, maintenance, and development speed.
Natural Language Programming
- Bad: Create a login system
- Good: Create a secure login system using Python Flask with JWT tokens, password hashing, and rate limiting. Include input validation and error handling.
Code Translation and Migration
- Bad: Convert this to JavaScript
- Good: Convert this Python class to TypeScript, maintaining the same interface and adding proper type annotations.
Understanding Legacy Code
- Bad: What does this do?
- Good: Explain this legacy JavaScript function step by step. It appears to handle data transformation but the variable names are unclear.
Performance Optimization
- Bad: Make this faster
- Good: Analyze this SQL query for performance issues. The table has 1M rows and this query takes 5 seconds. Suggest indexing strategies and query optimizations.
Security Review
- Bad: Check for security issues
- Good: Review this authentication code for common security vulnerabilities like SQL injection, XSS, and session management issues.
Remember for Developers
- AI is a tool, not a replacement—use it to augment your skills
- Always test AI-generated code before deploying
- Understand the output: don’t copy-paste without knowing what it does
- AI might not follow your team’s coding standards—review accordingly
- Version control everything when using AI assistance
X. Advanced Techniques for Experienced AI Users
Chain-of-Thought Prompting
Encourage AI to show its reasoning process by asking it to think step-by-step.
- Bad: Solve this math problem
- Good: Solve this math problem step by step, showing your reasoning at each stage.
Few-Shot Learning
Provide examples to help AI understand the pattern you want.
- Bad: Write a product description
- Good: Write a product description in the style of these two following examples. Example 1: Revolutionary wireless headphones with 30-hour battery life and crystal-clear sound. Example 2: Premium coffee maker featuring smart brewing technology and customizable settings.
System Prompts vs. User Prompts
- System prompts: Set the AI’s role and behavior (e.g., “You are a helpful coding assistant”)
- User prompts: Your actual requests
- Best practice: Use system prompts to establish context, user prompts for specific tasks
RAG (Retrieval-Augmented Generation)
Combine AI with external knowledge sources for more accurate, up-to-date responses. Useful when you need current information or domain-specific knowledge. Implementation: provide relevant documents or data alongside your prompt.
Prompt Chaining
Break complex tasks into a series of connected prompts.
- First prompt: Analyze the problem
- Second prompt: Generate solutions based on analysis
- Third prompt: Evaluate and refine solutions
Context Management
- Be mindful of token limits: Longer conversations cost more and may lose coherence
- Summarize when needed: “Summarize our conversation so far” to reset context
- Start fresh for new topics: Don’t mix unrelated tasks in the same conversation
Error Handling in Prompts
- Bad: Write code for user authentication
- Good: Write code for user authentication. Include error handling for invalid inputs, and explain any security considerations.
Iterative Refinement
Use AI’s responses as starting points, not final products:
- Generate initial output
- Identify gaps or issues
- Ask for specific improvements
- Repeat until satisfied
Remember for Advanced Users
- Experiment with parameters: Try different temperatures, max tokens, etc.
- Keep a prompt library: Document what works for your use cases
- Stay updated: AI capabilities evolve rapidly
- Combine tools: Use multiple AI systems for different tasks
- Validate outputs: Always verify AI-generated content, especially for critical applications
XI. Visual Examples and Templates
Writing Assistance
CONTEXT: [Your background/role]
TASK: [What you need written]
TONE: [Professional, casual, academic, etc.]
LENGTH: [Word count or format]
EXAMPLES: [Similar content you like]
Problem Solving
PROBLEM: [Describe the issue]
CONTEXT: [Relevant background]
CONSTRAINTS: [Limitations or requirements]
DESIRED OUTCOME: [What success looks like]
Analysis
TOPIC: [What to analyze]
PERSPECTIVE: [From whose viewpoint]
CRITERIA: [What factors to consider]
FORMAT: [How to present]
Thanks for reading, and check out the newsletter.