AI Prompt
Cookbook

You are a strategy consultant analyzing the competitive landscape for [COMPANY/PRODUCT] in the [INDUSTRY] market. Provide a structured analysis: 1. **Direct Competitors** (3-5): Name, positioning, strengths, weaknesses, pricing 2. **Indirect Competitors** (2-3): Adjacent solutions customers might choose instead 3. **Competitive Dimensions**: Map competitors on these axes: - Price vs. feature depth - Enterprise vs. SMB focus - Platform vs. point solution 4. **White Space**: Where is there unmet demand or underserved segments? 5. **Sustainable Advantages**: What would be hard for competitors to replicate? Format as a structured brief with tables where appropriate. Be specific, use real companies and real data.

Perform a SWOT analysis for [COMPANY] operating in [INDUSTRY/MARKET]. For each quadrant, provide 5-7 specific, evidence-based points, not generic observations. For each point, include: - The specific factor - Why it matters strategically - A concrete example or data point After the SWOT, provide: 1. **SO Strategies**: How strengths can exploit opportunities (2-3) 2. **ST Strategies**: How strengths can counter threats (2-3) 3. **WO Strategies**: How to overcome weaknesses using opportunities (2-3) 4. **WT Strategies**: Defensive moves to minimize weakness exposure to threats (2-3) Be brutally honest in the Weaknesses and Threats sections, sugar-coating defeats the purpose.

You are advising [COMPANY] on entering the [TARGET MARKET/GEOGRAPHY/SEGMENT]. Current situation: [BRIEF DESCRIPTION, revenue, core market, key assets] Build a market entry analysis: 1. **Market Sizing**: TAM, SAM, SOM with reasoning (not just numbers) 2. **Entry Barriers**: Regulatory, competitive, technical, distribution 3. **Entry Modes**, evaluate each: - Organic build - Acquisition - Partnership/JV - Licensing Rate each on: speed to market, capital required, risk level, control 4. **Beachhead Strategy**: Which specific sub-segment to target first and why 5. **90-Day Entry Plan**: First 10 concrete actions in priority order 6. **Kill Criteria**: What signals should trigger an abort decision? Be direct about which entry mode you recommend and why.

Create a Business Model Canvas for [COMPANY/STARTUP IDEA] with the following context: [BRIEF DESCRIPTION]. For each of the 9 blocks, provide: - 3-5 specific entries (not generic categories) - A brief annotation explaining the strategic logic Blocks: 1. Customer Segments 2. Value Propositions 3. Channels 4. Customer Relationships 5. Revenue Streams 6. Key Resources 7. Key Activities 8. Key Partnerships 9. Cost Structure After the canvas, identify: - The **riskiest assumption** in the model - The **strongest moat** in the model - One **pivot option** if the primary model doesn't scale

Write an executive summary of the following [REPORT/ANALYSIS/DOCUMENT]. Requirements: - 300-400 words maximum - Lead with the single most important finding or recommendation - Use the pyramid principle: conclusion first, then supporting evidence - Include 3-5 bullet points of key findings - End with a clear "Recommended Next Steps" section (2-3 actions) - Write for a [CEO/BOARD/VP-LEVEL] audience, no jargon, no hedging - Bold the key numbers and conclusions Document to summarize: [PASTE CONTENT HERE]

I'm writing a research paper on [TOPIC] for [COURSE/JOURNAL/PURPOSE]. Thesis/Research Question: [YOUR THESIS OR RQ] Create a detailed outline that includes: 1. **Abstract** (draft, 150 words) 2. **Introduction** - Hook / opening context - Problem statement - Research gap this paper fills - Thesis statement - Paper roadmap 3. **Literature Review**, suggest 5-7 research areas to cover, with the type of source to find for each 4. **Methodology**, recommend an appropriate research method and justify it 5. **Expected Findings/Analysis**, section structure based on the methodology 6. **Discussion**, how findings connect back to the literature 7. **Conclusion**, implications, limitations, future research For each section, include: - Estimated word count - Key point to make - Potential pitfall to avoid Style: [APA/MLA/CHICAGO]

Rewrite the following text to match this target profile: - **Audience**: [WHO, e.g., C-suite executives, undergraduate students, technical engineers] - **Tone**: [e.g., authoritative but approachable, formal academic, conversational] - **Reading level**: [e.g., 8th grade, graduate level, industry professional] - **Length target**: [e.g., cut by 40%, expand to 500 words, keep same length] Rules: - Preserve all factual claims and data points exactly - Replace jargon with plain language unless the audience expects it - Prefer active voice - Break up any sentence longer than 25 words - Do NOT add information that isn't in the original Original text: [PASTE HERE]

Analyze the following business case using a structured strategic framework. Case: [COMPANY NAME / CASE TITLE] Context: [BRIEF SUMMARY OR PASTE THE CASE] Provide your analysis in this structure: 1. **Situation Summary** (3-4 sentences, the core tension or decision) 2. **Key Stakeholders** and their conflicting interests 3. **Framework Application**, apply [Porter's Five Forces / Value Chain / PESTEL / Resource-Based View / choose the most appropriate] and explain why this framework fits 4. **Three Strategic Options**, for each: - Description - Pros (2-3) - Cons (2-3) - Financial/resource implications 5. **Recommendation**: Which option and why (be decisive) 6. **Implementation Risks**: Top 3 things that could go wrong 7. **Discussion Questions**: 3 questions to challenge this analysis Be specific, use numbers from the case wherever possible.

Write a professional decision memo. **To**: [RECIPIENT + TITLE] **From**: [YOUR NAME + TITLE] **Re**: [SUBJECT] **Date**: [DATE] Context: [WHAT DECISION NEEDS TO BE MADE AND WHY NOW] Structure: 1. **Bottom Line Up Front**: One sentence, what you recommend 2. **Background**: 2-3 sentences of essential context 3. **Options Analysis**: 2-3 options with pros, cons, and estimated cost/timeline 4. **Recommendation**: Which option and the top 3 reasons 5. **Risks & Mitigations**: What could go wrong and how to handle it 6. **Requested Decision**: Exactly what approval or action you need Tone: Direct, confident, no hedging. Every sentence should earn its place.

I have the following data. Help me interpret it. [PASTE DATA, CSV, TABLE, OR DESCRIBE THE DATASET] Analyze this data and provide: 1. **Key Findings**: The 3-5 most important patterns or insights 2. **Anomalies**: Anything unexpected or that doesn't fit the pattern 3. **Statistical Summary**: Central tendency, spread, and distribution shape (where applicable) 4. **Correlations**: Any relationships between variables worth investigating 5. **Limitations**: What this data can and cannot tell us 6. **Recommended Visualizations**: Which chart types would best communicate each finding 7. **Next Questions**: What follow-up analysis would deepen understanding Explain your reasoning at each step. Assume I understand basic statistics but not advanced techniques.

Design a survey to measure [WHAT YOU'RE TRYING TO LEARN]. Target respondents: [WHO] Distribution method: [HOW, email, in-person, platform] Target sample size: [NUMBER] Create: 1. **10-15 questions** that cover the research objectives 2. For each question, specify: - Question type (Likert, multiple choice, open-ended, ranking) - The specific options/scale - Why this question is included (what it measures) - Potential bias to watch for 3. **Question order**, logical flow that avoids priming effects 4. **Screening question** (if needed) to qualify respondents 5. **Estimated completion time** Rules: - No double-barreled questions - No leading questions - Include at least one reverse-coded item - Include one attention check - Keep it under 5 minutes total

I need a SQL query. Here's my database structure: [DESCRIBE YOUR TABLES AND COLUMNS, or paste CREATE TABLE statements] I want to find: [DESCRIBE WHAT YOU NEED IN PLAIN ENGLISH] Provide: 1. The SQL query (well-formatted with comments) 2. A plain English explanation of what each part does 3. Expected output format (what columns will be returned) 4. Performance notes (will this be slow on large tables? any indexes needed?) 5. An alternative approach if there is one Use [PostgreSQL / MySQL / SQLite] syntax.

I need a spreadsheet formula for [Google Sheets / Excel]. My data layout: - Column A: [DESCRIBE] - Column B: [DESCRIBE] - Column C: [DESCRIBE] - Data starts at row 2 (row 1 is headers) - [NUMBER] rows of data I want to: [DESCRIBE THE CALCULATION IN PLAIN ENGLISH] Provide: 1. The exact formula to paste 2. A step-by-step explanation of how it works 3. How to drag/copy it for multiple rows (if applicable) 4. Edge cases to watch for (blanks, errors, text vs numbers) 5. A simpler alternative if the formula is complex

Create a value proposition for [PRODUCT/SERVICE]. Target customer: [WHO, be specific about role, company size, pain] Key competitors: [2-3 ALTERNATIVES THE CUSTOMER CONSIDERS] Core differentiator: [WHAT WE DO DIFFERENTLY] Generate: 1. **One-liner** (under 10 words) 2. **Elevator pitch** (30 seconds / 75 words) 3. **Full value prop** (Geoffrey Moore format): "For [target customer] who [need/pain], [product] is a [category] that [key benefit]. Unlike [competitor], we [key differentiator]." 4. **Three supporting proof points**, specific, measurable where possible 5. **What NOT to say**, messaging traps to avoid Tone: Confident, specific, no buzzwords. If you catch yourself writing "innovative" or "cutting-edge," replace it with what's actually different.

Write a 4-email cold outreach sequence. **Who I'm targeting**: [ROLE + COMPANY TYPE] **What I'm offering**: [PRODUCT/SERVICE] **Key pain point**: [WHAT KEEPS THEM UP AT NIGHT] **Social proof**: [RELEVANT CUSTOMER WIN OR METRIC] For each email: - Subject line (under 6 words, no clickbait) - Body (under 100 words, mobile-readable) - Clear CTA (one per email) - Sending timing relative to previous email Sequence structure: 1. **Email 1**: Lead with their pain, introduce solution 2. **Email 2**: Social proof / case study angle (3 days later) 3. **Email 3**: Different angle, industry insight or trigger event (5 days later) 4. **Email 4**: Breakup email, last touch, low pressure (7 days later) Rules: - No "I hope this finds you well" - No "Just following up" - No "I'd love to pick your brain" - First sentence must reference THEIR world, not yours - Every email must be valuable even if they never respond

Write a LinkedIn post about [TOPIC/INSIGHT/EXPERIENCE]. My audience: [WHO FOLLOWS ME, e.g., AI practitioners, business students, tech founders] Goal: [WHAT I WANT, thought leadership, engagement, drive traffic to X] Structure: - Hook (first line that stops the scroll, no "I'm excited to announce") - Story or observation (3-5 short paragraphs) - Insight or lesson (the takeaway) - CTA or question to drive comments Rules: - Short paragraphs (1-2 sentences max) - No emoji spam - No hashtag walls (3 max, at the end) - Write like a human, not a brand - Include one specific number, name, or detail that makes it real - Under 1300 characters for optimal reach Tone: [PICK: conversational / authoritative / vulnerable / contrarian]

Write landing page copy for [PRODUCT/SERVICE]. **Target visitor**: [WHO LANDS ON THIS PAGE AND WHERE THEY CAME FROM] **Primary action**: [WHAT YOU WANT THEM TO DO, sign up, buy, book demo] **Price point**: [IF APPLICABLE] Sections to write: 1. **Hero headline** (under 8 words) + subhead (one sentence) 2. **Problem section**: 3 pain points the visitor relates to 3. **Solution section**: How your product solves each pain 4. **Features → Benefits**: 3-4 features translated into outcomes 5. **Social proof block**: Format for testimonials/logos/numbers 6. **Objection handling**: 3 common objections with one-line answers 7. **CTA section**: Final push with urgency or value reinforcement 8. **Microcopy**: Button text, form labels, trust badges Rules: - Headlines: benefit-first, not feature-first - Every section should answer "why should I care?" - Write scannable, bullets, bold key phrases, short paragraphs - No "Welcome to our website"

Explain the following code. I'm a [BEGINNER/INTERMEDIATE/ADVANCED] [LANGUAGE] developer. ```[LANGUAGE] [PASTE CODE HERE] ``` Provide: 1. **One-sentence summary**: What does this code do overall? 2. **Line-by-line walkthrough**: Explain what each significant block does and why 3. **Key concepts**: List any design patterns, algorithms, or language features used 4. **Data flow**: Trace how data moves through the code (input → transformation → output) 5. **Potential issues**: Bugs, edge cases, or performance concerns 6. **How to modify it**: If I wanted to [COMMON MODIFICATION], what would I change?

I have a bug. Help me diagnose and fix it. **Language/Framework**: [e.g., Python/Flask, JavaScript/React] **Expected behavior**: [WHAT SHOULD HAPPEN] **Actual behavior**: [WHAT ACTUALLY HAPPENS] **Error message** (if any): [PASTE ERROR] **Relevant code**: ``` [PASTE CODE] ``` **What I've already tried**: [LIST ATTEMPTS] Please: 1. Identify the most likely root cause 2. Explain WHY it's happening (not just what to change) 3. Provide the fix with a code diff 4. Suggest a test to verify the fix works 5. Recommend how to prevent this class of bug in the future

Generate code to integrate with [API NAME]. **Language**: [LANGUAGE/FRAMEWORK] **Authentication**: [API key / OAuth / Bearer token] **Endpoints I need**: - [ENDPOINT 1, describe what it does] - [ENDPOINT 2] - [ENDPOINT 3] Provide: 1. **Setup**: Dependencies, configuration, environment variables 2. **Auth helper**: Reusable authentication function 3. **API client class/module**: With methods for each endpoint 4. **Error handling**: Retry logic, rate limiting, common error codes 5. **Usage example**: How to call each method 6. **Type definitions**: Input/output types for each endpoint Code style: [CLEAN/MINIMAL, no unnecessary abstractions]

Write a README.md for [PROJECT NAME]. Project description: [WHAT IT DOES IN 2-3 SENTENCES] Tech stack: [LANGUAGES, FRAMEWORKS, TOOLS] Target audience: [WHO WILL USE/READ THIS] Include these sections: 1. **Title + one-line description** 2. **Features** (bullet list) 3. **Quick Start** (get running in under 2 minutes) 4. **Installation** (step-by-step) 5. **Usage** (with code examples) 6. **Configuration** (environment variables, options) 7. **API Reference** (if applicable, brief) 8. **Contributing** (how to submit changes) 9. **License** Rules: - Use proper markdown formatting - Include actual shell commands (not pseudo-code) - Add code fence language tags for syntax highlighting - Keep it scannable, someone should find what they need in 10 seconds

You are a Socratic tutor. Your goal is to help me deeply understand [CONCEPT/TOPIC]. Rules: - Never give me the answer directly - Ask me one question at a time that guides me toward understanding - If I'm wrong, don't say "wrong", ask a follow-up that reveals the flaw in my reasoning - If I'm stuck, give me a hint, not the answer - Use concrete examples and analogies from [DOMAIN I'M FAMILIAR WITH] - After 5-7 exchanges, summarize what I've learned and what gaps remain My current understanding: [WHAT I THINK I KNOW ABOUT THE TOPIC] My learning goal: [WHAT I WANT TO BE ABLE TO DO/EXPLAIN BY THE END] Start with your first question.

Generate practice exam questions for [COURSE/SUBJECT]. Topics to cover: [LIST KEY TOPICS] Exam format: [MULTIPLE CHOICE / SHORT ANSWER / ESSAY / MIXED] Difficulty distribution: 30% easy, 50% medium, 20% hard Generate: - [NUMBER] questions total - For multiple choice: 4 options, one correct, three plausible distractors - For short answer: Include the model answer and a grading rubric - For essay: Include key points a strong answer would cover After all questions, provide: 1. Answer key 2. Explanation for each answer (why right answer is right, why wrong answers are wrong) 3. Study recommendations for topics I'd likely struggle with Do NOT make questions that test memorization, test understanding and application.

Explain [CONCEPT] at these four levels: 1. **ELI5** (Explain Like I'm 5): Use a simple analogy a child would understand 2. **High School**: Use everyday language, introduce the correct terminology 3. **Undergraduate**: Include the theory, key researchers, and academic framework 4. **Expert**: Technical depth, edge cases, current debates in the field For each level, keep it to one paragraph. Then provide: - **Common misconceptions** about this concept (3) - **How to test understanding**: A question that reveals whether someone truly gets it vs. just memorized the definition - **Best analogy**: Your single best analogy for this concept and why it works

Design a [DURATION, e.g., 75-minute] lesson plan for [TOPIC]. Audience: [WHO, e.g., MBA students, corporate workshop, undergraduate intro course] Learning objectives (by end, students should be able to): 1. [OBJECTIVE 1] 2. [OBJECTIVE 2] 3. [OBJECTIVE 3] Provide: 1. **Lesson timeline** with minute-by-minute breakdown: - Activity name - Duration - Description - Materials needed - Engagement method (lecture, discussion, exercise, case, etc.) 2. **Opening hook** (first 3 minutes, grab attention) 3. **Active learning exercise** (at least one, not just lecture) 4. **Discussion questions** (5 questions, ordered from accessible to challenging) 5. **Assessment**: How to check whether learning objectives were met 6. **Backup plan**: If you run short or long on time No more than 20 minutes of straight lecture in any block.

Process these meeting notes into a structured summary. Meeting: [TITLE] Date: [DATE] Attendees: [NAMES] Raw notes: [PASTE MEETING NOTES, messy is fine] Provide: 1. **Meeting Summary** (3-4 sentences, what was this meeting about?) 2. **Key Decisions Made** (bulleted list, what was decided and by whom) 3. **Action Items** (table format): | Action | Owner | Deadline | Priority | Include every commitment made, even casual ones 4. **Open Questions** (unresolved items that need follow-up) 5. **Next Meeting Agenda** (suggested based on what's pending) If something is ambiguous in the notes, flag it with [UNCLEAR] rather than guessing.

I need to make a decision between [OPTION A], [OPTION B], and [OPTION C]. Context: [WHAT'S THE DECISION AND WHY IT MATTERS] Constraints: [BUDGET, TIMELINE, TEAM SIZE, etc.] What matters most: [TOP PRIORITIES] Build a decision matrix: 1. **Identify 6-8 evaluation criteria** based on my context (suggest them, don't just ask me) 2. **Weight each criterion** (must sum to 100%), explain your weighting logic 3. **Score each option** 1-5 on each criterion with brief justification 4. **Calculate weighted totals** 5. **Sensitivity analysis**: Does the ranking change if we adjust the top 2 weights by ±10%? 6. **Gut check**: Does the quantitative result match your qualitative assessment? If not, what criterion is missing? 7. **Recommendation**: Clear winner and the one reason that clinches it Present the matrix as a formatted table.

Create a project kickoff document. Project idea: [DESCRIBE IN 2-3 SENTENCES] Team: [WHO'S INVOLVED] Timeline: [ROUGH DEADLINE OR CONSTRAINT] Budget: [IF APPLICABLE] Generate: 1. **Project Name** (suggest a clear, internal-friendly name) 2. **Problem Statement**: What problem does this solve? (3 sentences) 3. **Success Criteria**: How do we know this worked? (3-5 measurable outcomes) 4. **Scope**: What's IN scope and what's explicitly OUT of scope 5. **Milestones**: 4-6 key milestones with target dates 6. **Roles & Responsibilities**: RACI-style for key activities 7. **Risks**: Top 5 risks with likelihood, impact, and mitigation 8. **Dependencies**: What needs to be true/done before we can start 9. **Communication Plan**: Who gets updates, how often, what format 10. **First Week Actions**: 5 concrete tasks to build momentum Keep the whole document under 2 pages.

Help me run my weekly review and plan next week. **Last week's goals were**: [LIST WHAT YOU PLANNED TO DO] **What actually happened**: [LIST WHAT YOU ACTUALLY DID, wins, misses, surprises] **Current projects**: [LIST ACTIVE PROJECTS AND STATUS] Provide: 1. **Week in Review**: - Completion rate (goals hit / goals set) - Biggest win - Biggest miss and why - What I should stop doing - What I should start doing 2. **Next Week Plan**: - Top 3 priorities (the week is a success if these get done) - 2 secondary goals - 1 stretch goal - Time blocks: Suggest a daily theme structure 3. **Energy Management**: - Which tasks need deep focus (schedule for morning)? - Which are administrative (batch into one afternoon)? 4. **One question to reflect on this week**

I wrote this prompt but the output isn't great. Improve it. My current prompt: """ [PASTE YOUR PROMPT] """ The output I'm getting: [DESCRIBE WHAT'S WRONG, too vague, wrong format, missing detail, etc.] What I actually want: [DESCRIBE IDEAL OUTPUT] Rewrite my prompt to be more effective. Specifically: 1. Add structure and constraints where the original is vague 2. Include output format specifications 3. Add a role/persona if it would help 4. Include examples of good vs. bad output if applicable 5. Remove ambiguity, every instruction should have one clear interpretation Show me: - The improved prompt - A bullet list of what you changed and why - One thing to watch for in the output

Build a system prompt for an AI assistant with this purpose: **Name**: [ASSISTANT NAME] **Purpose**: [WHAT IT DOES, e.g., customer support for a SaaS product, research assistant, writing coach] **Audience**: [WHO WILL INTERACT WITH IT] **Personality**: [TONE, e.g., professional, friendly, direct, Socratic] The system prompt should include: 1. **Identity & Role**: Who the assistant is and what it does 2. **Behavioral Rules**: What it should always/never do 3. **Knowledge Boundaries**: What it knows and doesn't know, how to handle out-of-scope questions 4. **Output Formatting**: Default response structure 5. **Edge Cases**: How to handle ambiguity, mistakes, or hostile input 6. **Examples**: 2-3 example interactions showing ideal behavior Format the system prompt ready to paste into an API call. Keep it under 500 words, concise system prompts outperform verbose ones.

I need to accomplish [COMPLEX TASK] using AI, but it's too complex for a single prompt. Design a prompt chain, a sequence of prompts where each step's output feeds into the next. For each step: 1. **Step name** and purpose 2. **Input**: What goes into this prompt (user input, or output from previous step) 3. **The prompt** itself 4. **Expected output format**: What this step produces 5. **Quality gate**: How to check if the output is good enough to proceed 6. **Fallback**: What to do if this step produces poor results Design for: - Minimum number of steps (each API call costs money) - Clear data handoff between steps - Error recovery at each stage - A final step that synthesizes everything into the desired end product Also suggest which steps can run in parallel vs. which are sequential.

Help me prepare a sacrament meeting talk on [TOPIC, e.g., faith during trials, the Atonement of Jesus Christ, covenant keeping]. Talk length: [10 / 15 / 20] minutes (approximately [1000 / 1500 / 2000] words) Audience: Ward members of all ages Requirements: - Ground every point in scripture (Book of Mormon, Doctrine & Covenants, Bible, Pearl of Great Price) - Include at least 2-3 specific scripture references with the actual verses quoted - Reference at least one recent General Conference talk (within the last 2-3 years) from churchofjesuschrist.org/study/general-conference - Include one personal experience or relatable story (mark as [INSERT PERSONAL STORY HERE] so I can add my own) - Build toward a testimony-bearing conclusion - Maintain a tone that is sincere, warm, and inviting, not preachy or academic Structure: 1. **Opening**: A compelling scripture, story, or question that draws people in 2. **Doctrinal Foundation**: What the scriptures and prophets teach about this topic 3. **Application**: How this doctrine applies to our daily lives, specific, practical examples 4. **Personal witness / story**: [Placeholder for my experience] 5. **Testimony & Close**: Bear testimony and end in the name of Jesus Christ Do NOT: - Use generic filler ("We all know that..." or "Webster's dictionary defines...") - Over-quote without explanation, weave scriptures into the narrative - Make it a lecture, make it a conversation Source material ONLY from: - The Standard Works (Bible, Book of Mormon, D&C, Pearl of Great Price) - General Conference addresses: churchofjesuschrist.org/study/general-conference - Gospel Topics: churchofjesuschrist.org/study/manual/gospel-topics

I want to deepen my understanding of [GOSPEL TOPIC, e.g., grace and works, the gathering of Israel, temple covenants, the plan of salvation]. Create a structured study guide: 1. **Overview**: A clear, concise explanation of this doctrine (3-4 paragraphs) 2. **Key Scriptures** (8-10): - List the reference - Quote the key verse(s) - Explain how it relates to the topic - Group by: Old Testament, New Testament, Book of Mormon, D&C/PoGP 3. **Prophetic Teachings**: Summarize what 3-4 modern prophets or apostles have taught about this topic, referencing General Conference talks 4. **Common Questions**: 3-5 questions people often have about this topic, with thoughtful answers grounded in doctrine 5. **Related Topics**: What other gospel principles connect to this one? 6. **Personal Study Plan**: 5 days of focused study with specific readings for each day Sources ONLY from: - Scriptures (standard works) - General Conference: churchofjesuschrist.org/study/general-conference - Gospel Topics: churchofjesuschrist.org/study/manual/gospel-topics - Come Follow Me manuals: churchofjesuschrist.org/study/come-follow-me - Bible Dictionary: churchofjesuschrist.org/study/scriptures/bd - Guide to the Scriptures: churchofjesuschrist.org/study/scriptures/gs Do NOT reference unofficial sources, blogs, podcasts, or commentary outside official Church materials.

Help me plan a [DURATION, e.g., 40-minute] lesson on [TOPIC]. Class: [Sunday School / Elders Quorum / Relief Society / Young Women / Young Men, Deacons (12-13) / Teachers (14-15) / Priests (16-17)] Come Follow Me reference (if applicable): [WEEK/CHAPTER] Class size: approximately [NUMBER] people Design the lesson: 1. **Opening** (3-5 minutes): - An engaging question, scenario, or object lesson to start - Opening scripture and prayer 2. **Core Doctrine** (15-20 minutes): - 2-3 key principles to teach from the scriptures - For each principle: the scripture reference, a clear explanation, and a discussion question - Include a quote from a modern prophet or apostle (from General Conference) 3. **Discussion & Application** (10-15 minutes): - 4-5 open-ended discussion questions (not yes/no) that invite personal reflection - At least one question that connects the doctrine to real, current challenges the class faces - A small-group or partner activity if appropriate for the class size 4. **Closing** (5 minutes): - Invitation to act: One specific thing class members can do this week - Closing testimony bearing opportunity - Summary of key truths **Teaching principles to follow:** - Invite the Spirit, don't just lecture - Ask questions more than you give answers - Leave space for class members to share experiences - Use the scriptures as the primary text, not your outline - Prepare more than you'll use, the Spirit may redirect the lesson Sources ONLY from: - Standard Works - Come Follow Me: churchofjesuschrist.org/study/come-follow-me - General Conference: churchofjesuschrist.org/study/general-conference - Teaching in the Savior's Way: churchofjesuschrist.org/study/manual/teaching-in-the-saviors-way

Plan a youth activity for our ward. **Group**: [Young Men, Deacons (12-13) / Teachers (14-15) / Priests (16-17) / combined Young Men / Young Women / combined youth] **Number of youth**: approximately [NUMBER] **Available time**: [DURATION, e.g., 90 minutes, 2 hours, full evening] **Location**: [Church building / outdoor park / member's home / service location] **Budget**: [$ AMOUNT or "minimal"] **Season/Weather**: [MONTH and indoor/outdoor preference] **Theme or focus** (optional): [e.g., service, teamwork, Come Follow Me tie-in, just fun, getting to know each other] Provide 3 activity options, and for each: 1. **Activity Name** (something the youth would actually think sounds fun) 2. **Description**: What happens, step by step 3. **Gospel Connection**: How this naturally ties to a gospel principle (subtle, not forced) 4. **Materials Needed**: Specific list 5. **Setup Time**: How long to prepare 6. **Detailed Schedule**: Minute-by-minute plan 7. **Backup Plan**: What to do if weather, attendance, or energy isn't what you expected 8. **Safety Considerations**: Anything leaders need to watch for 9. **How to Involve Less-Active Youth**: Ideas to make newcomers feel welcome, not awkward Priorities: - Fun first, youth come back when they had a good time - Include everyone, activities shouldn't favor athletic or outgoing kids only - Age-appropriate, a Deacons activity is different from a Priests activity - Gospel tie-in should feel natural, not forced Reference the Church's youth activity guidelines: churchofjesuschrist.org/study/manual/young-women-camp-guide FSY resources: churchofjesuschrist.org/youth/childrenandyouth

Plan a Family Home Evening (FHE) on [TOPIC, or say "surprise me"]. Family makeup: [DESCRIBE, e.g., couple with no kids, family with kids ages 3, 7, and 12, young single adults together, empty nesters] Time available: [30 minutes / 45 minutes / 1 hour] Provide a complete FHE plan: 1. **Opening Song**: Suggest a hymn or children's song from the Church hymnbook (hymn number) 2. **Opening Prayer**: Who should be invited to pray 3. **Scripture**: One scripture to read together (short enough for young kids if applicable) 4. **Lesson** (10-15 minutes): - A simple object lesson or story that teaches the principle - 2-3 discussion questions appropriate for the age range - For families with young children: include a coloring page idea or simple activity - For families with teens: include a real-world scenario to discuss 5. **Activity** (10-20 minutes): A game, craft, or activity that reinforces the lesson (or is just fun) 6. **Treat**: A simple treat idea that fits the theme (optional but let's be real, this is key) 7. **Closing Song & Prayer** 8. **Challenge for the week**: One thing the family can do together Sources: - Hymns: churchofjesuschrist.org/music/library/hymns - Children's Songbook: churchofjesuschrist.org/music/library/childrens-songbook - Come Follow Me: churchofjesuschrist.org/study/come-follow-me - Gospel Library: churchofjesuschrist.org/study