TL;DR - Best AI Prompts for Learning & Skill Development
Looking for ready-to-use AI prompts for learning? This guide contains 40+ copy-paste prompts that work with ChatGPT, Claude, and Gemini. Each prompt is completely self-contained—just copy, customize the placeholder comments, and paste. For foundational prompting skills, see the Prompt Engineering Fundamentals guide.
What’s included:
- Learning Plans — Study roadmaps, skill breakdowns, timeline creation
- Concept Mastery — Explanations, analogies, Feynman technique
- Practice & Testing — Exercises, quizzes, flashcards, mock tests
- Knowledge Gaps — Assessment, weak area identification, targeted review
- Career Development — Skill gap analysis, interview prep, certifications
- Retention — Spaced repetition, review schedules, active recall
💡 Pro tip: Every line starting with
# REPLACE:is a placeholder. Replace these with your actual content before pasting into your AI assistant. For a comparison of AI learning tools, see the AI Assistant Comparison guide.
How to Use These Learning Prompts
Each prompt below is ready to copy and paste. Here’s how they work:
- Copy the entire prompt from the code block
- Replace the placeholder comments (lines starting with
# REPLACE:) with your actual content - Paste into ChatGPT, Claude, or your preferred AI
- Get your result and iterate if needed
Example of customization:
# Before (placeholder):
# REPLACE: What do you want to learn? (e.g., "Machine learning fundamentals")
# After (customized):
I want to learn Python programming, specifically data analysis with pandas and numpy.
I have basic programming experience in JavaScript.Learning Plan Prompts
Create Learning Roadmap
You are an expert learning coach creating a personalized learning roadmap. For AI-powered everyday productivity, see the [AI for Everyday Productivity guide](/tech-articles/ai-for-everyday-productivity/).
=== LEARNING GOAL ===
What I want to learn:
# REPLACE: The skill or topic you want to master
# Example: "Web development with React and Node.js"
Why I'm learning this:
# REPLACE: Your motivation or goal
# Example: "Career switch to front-end development, aiming for junior developer role"
=== CURRENT LEVEL ===
My background:
# REPLACE: What you already know
# Example: "Basic HTML/CSS, some JavaScript (can write simple functions)"
Related experience:
# REPLACE: Any relevant prior knowledge
# Example: "5 years in marketing, comfortable with computers, no formal coding"
=== CONSTRAINTS ===
Available time:
# REPLACE: How much time can you dedicate?
# Example: "10 hours per week, mostly weekends"
Timeline goal:
# REPLACE: When do you want to reach your goal?
# Example: "Job-ready in 6 months"
Learning preferences:
# REPLACE: How do you learn best?
# Example: "Prefer video courses, need hands-on projects, struggle with dense reading"
=== INSTRUCTIONS ===
Create a comprehensive learning roadmap. Provide:
1. LEARNING PATH OVERVIEW
Visual representation of the learning journey:
Phase 1 (Weeks 1-4): Foundation
└── Topic A → Topic B → Topic C
Phase 2 (Weeks 5-8): Core Skills
└── Topic D → Topic E → Topic F
(Continue for full timeline)
2. PHASE BREAKDOWN
For each phase:
PHASE 1: [Name] (Weeks X-Y)
Goals: What you'll be able to do after this phase
| Week | Topic | Learning Activities | Time | Milestone |
| --- | --- | --- | --- | --- |
| 1 | | | X hrs | |
Resources:
- [Free resource 1]
- [Paid resource if needed]
Projects to build:
- [Mini project for practice]
3. SKILL DEPENDENCY MAP
What needs to be learned before what:
| Skill | Prerequisites | Unlocks |
4. MILESTONE CHECKPOINTS
| Milestone | By When | How to Know You've Reached It |
Concrete deliverables or tests for each checkpoint.
5. RESOURCE RECOMMENDATIONS
| Topic | Free Resource | Paid Resource | Type |
Prioritize free resources, note when paid is significantly better.
6. PROJECT PROGRESSION
Projects that build on each other:
| Project # | Description | Skills Practiced | Complexity |
| 1 | | | Beginner |
| 2 | | | Intermediate |
| Final | Portfolio piece | All skills | Advanced |
7. WEEKLY SCHEDULE TEMPLATE
Given your time constraints:
| Day | Time Block | Activity Type |
| Saturday | 3 hrs | Video learning + practice |
| Sunday | 4 hrs | Project work |
| Weeknights | 3 hrs total | Review + exercises |
8. POTENTIAL OBSTACLES
| Obstacle | How to Overcome | Signs You're Stuck |
9. ADJUSTMENT TRIGGERS
When to modify the plan:
- Speed up if: [signs you can accelerate]
- Slow down if: [signs you need more time]
- Pivot if: [signs to change approach]
10. SUCCESS METRICS
How to measure progress:
| Week | You Should Be Able To | Self-Check |Break Down Complex Topic
You are a curriculum designer breaking down a complex topic into learnable chunks.
=== THE TOPIC ===
What to break down:
# REPLACE: The complex topic or skill
# Example: "Machine Learning"
=== CONTEXT ===
Learner's goal:
# REPLACE: What do they want to do with this knowledge?
# Example: "Build ML models for business predictions, not academic research"
Current level:
# REPLACE: Starting point
# Example: "Strong in Python, basic statistics, no ML experience"
=== INSTRUCTIONS ===
Break this topic into a learnable structure. Provide:
1. TOPIC HIERARCHY
[MAIN TOPIC]
├── Core Concept 1
│ ├── Sub-concept 1.1
│ ├── Sub-concept 1.2
│ └── Sub-concept 1.3
├── Core Concept 2
│ ├── Sub-concept 2.1
│ └── Sub-concept 2.2
└── Core Concept 3
└── ...
2. CONCEPT CARDS
For each major concept:
CONCEPT: [Name]
One-sentence summary:
[What it is in plain terms]
Why it matters:
[Why this concept is important to learn]
Prerequisites:
[What to know first]
Key sub-topics:
- [Sub-topic 1]
- [Sub-topic 2]
Time to learn:
[Estimated hours for this concept]
How to know you understand it:
[Concrete test or explanation you should be able to give]
3. LEARNING SEQUENCE
Optimal order to learn these concepts:
| Order | Concept | Why This Order |
| 1 | | Foundation for everything |
| 2 | | Builds on #1, needed for #3 |
4. MINIMUM VIABLE KNOWLEDGE
The 20% of this topic that gives 80% of practical value:
- [Essential concept 1]
- [Essential concept 2]
- [Essential concept 3]
Learn these first for fastest practical application.
5. DEPTH LEVELS
| Concept | Awareness Level | Working Level | Expert Level |
| [Concept] | Know what it is | Can apply it | Can optimize/teach |
What to know at each depth:
- Awareness: [What to learn]
- Working: [What to learn additionally]
- Expert: [Advanced learning]
6. COMMON MISCONCEPTIONS
| Concept | Common Misconception | Correct Understanding |
7. CONNECTIONS
How concepts relate to each other:
| Concept A | Relates to | Concept B | How |
8. PRACTICAL APPLICATION MAP
| Concept | Real-World Application | Practice Project |
9. RECOMMENDED LEARNING CHUNKS
Break into digestible learning sessions:
| Session | What to Cover | Duration | Outcome |
| 1 | | 45 min | |
10. ASSESSMENT FRAMEWORK
For each major concept:
- Beginner question:
- Intermediate question:
- Advanced question:Create Weekly Study Schedule
You are a productivity coach creating an optimized study schedule.
=== WHAT I'M LEARNING ===
Topic/Skill:
# REPLACE: What you're studying
# Example: "AWS Solutions Architect certification"
Current phase:
# REPLACE: Where are you in your learning journey?
# Example: "Week 3 of 8-week study plan, focusing on compute services"
=== MY AVAILABILITY ===
Weekly hours available:
# REPLACE: Total hours you can study
# Example: "15 hours per week"
Schedule details:
# REPLACE: When you're available
# Monday-Friday: 1 hour in morning, 1 hour after work
# Saturday: 4 hours
# Sunday: 3 hours
=== MY CONSTRAINTS ===
# REPLACE: Any limitations
# - Energy is low after 9 PM
# - Easily distracted at home, better at coffee shop
# - Short attention span, need breaks every 30 min
=== LEARNING ACTIVITIES NEEDED ===
# REPLACE: Types of activities to include
# - Video courses (currently using ACloudGuru)
# - Practice exams
# - Hands-on labs
# - Flashcard review
# - Reading documentation
=== INSTRUCTIONS ===
Create an optimized weekly study schedule. Provide:
1. WEEKLY OVERVIEW
| Day | Time Block | Duration | Activity | Location |
| Mon | 6:30-7:30 AM | 1 hr | | |
| Mon | 6:00-7:00 PM | 1 hr | | |
| Tue | ... | | | |
(Complete week)
2. ACTIVITY DISTRIBUTION
Balance different learning modes:
| Activity Type | Hours/Week | % of Time | Best Time Slots |
| Passive (video/reading) | | | |
| Active (practice/labs) | | | |
| Review (flashcards/notes) | | | |
| Testing (practice exams) | | | |
3. DAILY STRUCTURE TEMPLATES
WEEKDAY MORNING (1 hour):
- 0-5 min: Quick review of yesterday
- 5-45 min: [Main activity]
- 45-60 min: [Wrap-up activity]
WEEKDAY EVENING (1 hour):
- [Structure optimized for tired mind]
WEEKEND DEEP WORK (3-4 hours):
- [Structure for longer sessions]
4. ENERGY MAPPING
Match activities to energy levels:
| Energy Level | Best For | Avoid |
| High (fresh) | New concepts, complex topics | Review |
| Medium | Practice, hands-on | Heavy reading |
| Low (tired) | Review, flashcards | New learning |
5. BREAK STRUCTURE
For different session lengths:
- 30 min session: [break structure]
- 1 hour session: [break structure]
- 3+ hour session: [break structure with pomodoro]
6. WEEKLY RHYTHM
- Best day for: New material (when freshest)
- Best day for: Practice (after learning)
- Best day for: Review (before new week)
- Best day for: Assessment (check progress)
7. FLEXIBILITY BUFFER
Built-in catch-up time:
| Buffer Block | Purpose | Backup Use If Not Needed |
8. ENVIRONMENT OPTIMIZATION
| Activity | Best Environment | Why |
9. PROGRESS TRACKING
Daily: [Quick check to do]
Weekly: [Review to complete on Sunday]
| Week | Goal | Completed | Notes |
10. ADJUSTMENTS FOR COMMON SCENARIOS
- Tired/low motivation day: [Modified schedule]
- Missed previous day: [Catch-up plan]
- Ahead of schedule: [How to use extra time]Concept Mastery Prompts
Explain Concept Simply
You are an expert teacher who excels at explaining complex concepts simply.
=== CONCEPT TO EXPLAIN ===
What I want to understand:
# REPLACE: The concept you're struggling with
# Example: "How does blockchain consensus work?"
=== MY CURRENT UNDERSTANDING ===
What I already know:
# REPLACE: Your existing knowledge
# Example: "I understand that blockchain is a distributed database, and I know
# what hashing is. But I don't understand how all the computers agree on what's valid."
What confuses me:
# REPLACE: Specific points of confusion
# Example: "How do they prevent someone from cheating? What stops conflicts?"
=== MY BACKGROUND ===
Relevant knowledge:
# REPLACE: Related things you understand
# Example: "I work in IT, understand databases, networks, basic cryptography"
Learning style:
# REPLACE: How you learn best
# Example: "I learn best with analogies to real-world things"
=== INSTRUCTIONS ===
Explain this concept thoroughly but simply. Provide:
1. ONE-SENTENCE SUMMARY
The concept in one simple sentence a smart 10-year-old could understand.
2. REAL-WORLD ANALOGY
An analogy that maps the concept to something familiar:
"[Concept] is like [familiar thing]..."
Then explain how each part of the analogy maps to the concept:
| Real-World Element | Maps To | Why |
3. BUILDING BLOCKS EXPLANATION
Break down into smaller pieces, explain each:
First, understand [building block 1]:
[Explanation]
Next, understand [building block 2]:
[Explanation]
Now combine them:
[How they work together]
4. STEP-BY-STEP WALKTHROUGH
Walk through a concrete example:
Let's trace through [specific scenario]:
Step 1: [What happens]
Step 2: [What happens next]
Step 3: [Continue...]
Result: [Outcome and why]
5. WHY IT MATTERS
Why this concept exists / what problem it solves:
- Without this: [What would happen]
- With this: [What becomes possible]
6. COMMON MISCONCEPTIONS
| People Often Think | Actually |
Clear up typical misunderstandings.
7. CONNECTIONS
How this relates to things you already know:
| You Know | This Concept | Connection |
8. EDGE CASES
When doesn't this work / apply?
- Exception 1:
- Exception 2:
9. CHECK YOUR UNDERSTANDING
Questions to test if you really get it:
- Basic: [Question you should now be able to answer]
- Intermediate: [Slightly harder]
- Advanced: [Requires deeper understanding]
10. NEXT STEPS
Now that you understand this, you're ready to learn:
- [Related concept 1]
- [Related concept 2]Feynman Technique Learning
You are a learning coach using the Feynman Technique to deepen understanding.
=== CONCEPT I'M LEARNING ===
Topic:
# REPLACE: What you're trying to master
# Example: "Recursion in programming"
=== MY CURRENT EXPLANATION ===
# REPLACE: Try to explain the concept in your own words (this is key!)
# Example: "Recursion is when a function calls itself. Like if you have a problem,
# you break it into smaller versions of the same problem until you get to a simple
# case. But I'm not totally clear on why you need a base case or when to use it."
=== WHERE I STRUGGLE ===
# REPLACE: Parts that are fuzzy or you can't explain well
# Example: "I don't really get the call stack part or why you could run out of memory"
=== INSTRUCTIONS ===
Apply the Feynman Technique to strengthen my understanding. Provide:
1. ANALYSIS OF MY EXPLANATION
What I got right:
- [Correct element 1]
- [Correct element 2]
What's incomplete or unclear:
- [Gap 1]
- [Gap 2]
What's incorrect:
- [Misconception if any]
2. SIMPLIFIED EXPLANATION
How to explain this to a curious 12-year-old:
"[Complete explanation using simple words, no jargon]"
Key vocabulary needed:
| Term | Simple Definition |
3. THE GAPS FILLED
For each gap in my understanding:
GAP: [What I was missing]
Simple explanation:
[Fill the gap in plain terms]
Concrete example:
[Specific example that illustrates this]
Why this matters:
[Why understanding this is important]
4. ANALOGY THAT COVERS ALL PARTS
One unified analogy that explains the whole concept including the parts I missed:
"Think of [concept] like [analogy]..."
[Detailed analogy that maps to each component]
5. TEACHING SCRIPT
If I had to teach this in 2 minutes, here's the script:
"[Complete mini-lesson I could give to someone else]"
6. PRACTICE EXPLANATION
Now I should try explaining again. Prompts to hit each key point:
- Start with: What is [concept]?
- Then explain: Why does it exist / what problem does it solve?
- Include: [Key element I was missing]
- Give an example: [Type of example to use]
- Address: [Common confusion point]
7. COMPREHENSION QUESTIONS
To verify I truly understand:
| Question | If I Can Answer, I Understand |
| [Question 1] | [Core concept] |
| [Question 2] | [The part I was missing] |
| [Question 3] | [Application/when to use] |
8. EDGE CASE EXPLORATION
Can I explain what happens when:
- [Edge case 1]?
- [Edge case 2]?
If these are hard to explain, I need to study more.
9. CONNECTIONS TO STRENGTHEN
Related concepts that reinforce this:
| Concept | How It Relates | Why Learn Together |
10. RE-EXPLANATION TEMPLATE
Fill in this template to prove understanding:
"[Concept] is ________________.
It works by ________________.
You would use it when ________________.
The key insight is ________________.
A common mistake is thinking ________________, but actually ________________."Learn Through Examples
You are a teacher who believes in learning through concrete examples.
=== WHAT I'M LEARNING ===
Concept/Skill:
# REPLACE: What you want to understand through examples
# Example: "SQL JOIN operations"
=== MY LEVEL ===
Current understanding:
# REPLACE: What you already know
# Example: "I can write basic SELECT queries and understand table structure"
=== INSTRUCTIONS ===
Teach this concept through progressively complex examples. Provide:
1. SIMPLEST EXAMPLE
The absolute minimum example that demonstrates the concept:
Setup:
[Minimal context needed]
Example:
[The example itself]
What's happening:
[Line-by-line explanation]
Key insight:
[The one thing to learn from this]
2. BUILDING COMPLEXITY
Example 2: Adding one more element
[Example]
[Explanation of what's new]
Example 3: Real-world scenario
[Example]
[Why this is realistic]
Example 4: Common use case
[Example]
[When you'd actually use this]
3. EXAMPLE PROGRESSION TABLE
| # | Example Focus | New Element Added | Complexity |
| 1 | Basic syntax | - | Minimal |
| 2 | | | |
| 3 | | | |
| 4 | | | |
| 5 | | | Full |
4. SIDE-BY-SIDE COMPARISONS
Show differences between similar things:
| Scenario | [Approach A] | [Approach B] | When to Use Each |
Example A:
[Code/demonstration]
Example B (same scenario, different approach):
[Code/demonstration]
The difference: [What changed and why]
5. WRONG EXAMPLES (Anti-patterns)
Learn from mistakes:
WRONG WAY (common mistake):
[Bad example]
Why it's wrong:
[Explanation]
RIGHT WAY:
[Corrected example]
The fix: [What was changed]
6. EDGE CASE EXAMPLES
Examples that test boundaries:
Edge case 1: [What if X?]
[Example and result]
Edge case 2: [What if Y?]
[Example and result]
7. REAL-WORLD SCENARIOS
5 practical examples you'd encounter:
| Scenario | Why You'd Need This | Example |
| 1. | | |
| 2. | | |
8. PATTERN RECOGNITION
After seeing all these examples, the pattern is:
"When you see [situation], use [approach] because [reason]"
Template:
[Generalizable pattern to apply]
9. PRACTICE EXAMPLES
Now try these yourself:
Exercise 1 (Easy):
[Problem to solve]
Hint: [Guidance]
Solution: [Hidden or to reveal]
Exercise 2 (Medium):
[Problem]
Exercise 3 (Challenging):
[Problem]
10. CREATE YOUR OWN
Challenge: Create an example that demonstrates [specific aspect].
Your example should include:
- [Required element 1]
- [Required element 2]
This tests whether you truly understand the concept!Practice & Testing Prompts
Generate Practice Problems
You are a tutor creating targeted practice problems.
=== WHAT I'M PRACTICING ===
Topic/Skill:
# REPLACE: What you need to practice
# Example: "Python list comprehensions"
=== MY LEVEL ===
Current ability:
# REPLACE: Where you are now
# Example: "Can write basic list comprehensions with simple conditions"
Target level:
# REPLACE: Where you want to be
# Example: "Comfortable with nested comprehensions and complex transformations"
=== WEAK AREAS ===
# REPLACE: Where you struggle
# Example: "Multiple conditions, nested loops, dictionary comprehensions"
=== INSTRUCTIONS ===
Generate a progressive set of practice problems. Provide:
1. WARM-UP PROBLEMS (5 problems)
Reinforce basics before pushing further:
Problem 1: [Easy]
Description: [What to do]
Starting point: [Given information]
Expected output: [What result should look like]
(Continue for 5 problems)
2. SKILL-BUILDING PROBLEMS (10 problems)
Progressively harder, targeting weak areas:
| # | Focus Area | Difficulty | Description |
| 1 | [Weak area] | Medium | |
| 2 | | | |
For each problem:
PROBLEM [#]: [Title]
Focus: [What skill this builds]
[Full problem description]
Input: [If applicable]
Expected output: [Result]
Hint (if needed): [Guidance without giving away answer]
3. CHALLENGE PROBLEMS (3 problems)
Push beyond current ability:
CHALLENGE [#]: [Title]
[Description]
Why it's challenging: [What makes this hard]
Approach hint: [High-level guidance]
4. REAL-WORLD APPLICATIONS (3 problems)
Problems based on actual use cases:
SCENARIO: [Real situation]
You're working on [context]. You need to [task].
Given: [Data/situation]
Produce: [Required output]
Constraints: [Any limitations]
5. DEBUG CHALLENGES (3 problems)
Find and fix errors:
BUGGY CODE:
[Code with errors]
Expected behavior: [What should happen]
Actual behavior: [What's wrong]
Find and fix: [Expectation]
6. SOLUTION FRAMEWORK
For each problem, I'll provide:
- Solution approach (strategy)
- Complete solution
- Common mistakes
- Variations to try
7. SELF-ASSESSMENT RUBRIC
Check your solutions:
| Criterion | Points | How to Score |
| Works correctly | /3 | 3=perfect, 2=minor issues, 1=major issues |
| Code quality | /2 | Clean, readable, well-structured |
| Efficiency | /2 | Optimal approach |
| Edge cases | /2 | Handles unusual inputs |
Total: /9 per problem
8. SPACED REPETITION SET
Problems to revisit:
- Tomorrow: Problems [X, Y]
- In 3 days: Problems [A, B]
- In 1 week: [Full review set]
9. PROBLEM GENERATION TEMPLATE
Create your own problems like this:
[Template for generating similar problems]
10. NEXT LEVEL PREVIEW
Once you master these, here's what's next:
| Current Skill | Next Challenge | Sample Problem |Create Quiz Questions
You are an assessment expert creating comprehensive quiz questions.
=== TOPIC ===
What to quiz on:
# REPLACE: The topic being tested
# Example: "React hooks and state management"
=== SCOPE ===
What to cover:
# REPLACE: Specific areas within the topic
# - useState and useEffect basics
# - Custom hooks
# - useContext for state sharing
# - Common pitfalls
What to exclude:
# REPLACE: Out of scope
# - Redux (not covered yet)
# - Server components
=== QUIZ PURPOSE ===
# REPLACE: What this quiz is for
# Example: "Self-assessment before job interview"
=== INSTRUCTIONS ===
Create a comprehensive quiz. Provide:
1. MULTIPLE CHOICE QUESTIONS (10 questions)
Q1. [Question text]
a) [Option]
b) [Option]
c) [Option]
d) [Option]
Correct: [Letter]
Explanation: [Why this is correct and others are wrong]
Difficulty: Easy/Medium/Hard
Tests: [What concept]
(Continue for 10 questions)
2. TRUE/FALSE QUESTIONS (5 questions)
Q1. [Statement]
Answer: True/False
Explanation: [Why]
Common misconception if False: [What people often think]
3. SHORT ANSWER QUESTIONS (5 questions)
Q1. [Question requiring brief written response]
Expected answer points:
- [Key point 1]
- [Key point 2]
Scoring:
- Full credit: [What answer needs to include]
- Partial credit: [Acceptable partial answers]
4. SCENARIO-BASED QUESTIONS (3 questions)
SCENARIO: [Realistic situation]
[Context and background]
Questions:
a) [Question about the scenario]
b) [Another question]
Expected responses: [What good answers include]
5. CODE ANALYSIS QUESTIONS (if applicable) (3 questions)
Review this code:
[Code snippet]
Q1. What will this output?
Q2. What's wrong with this approach?
Q3. How would you improve it?
Answers: [Detailed explanations]
6. FILL IN THE BLANK (5 questions)
Complete the statement:
Q1. In React, _______ is used to _______ because _______.
Answer: [Completed statement]
7. MATCHING QUESTIONS
Match concepts to descriptions:
| Concept | | Description |
| 1. [Term A] | | A. [Description 1] |
| 2. [Term B] | | B. [Description 2] |
Answers: 1-?, 2-?, etc.
8. ANSWER KEY
All answers in one place:
| Question | Answer | Topic Tested |
| MC-1 | | |
| MC-2 | | |
9. SCORING GUIDE
| Score | Level | Recommendation |
| 90-100% | Expert | Ready for advanced topics |
| 70-89% | Proficient | Review weak areas |
| 50-69% | Developing | Need more study |
| <50% | Foundational | Revisit basics |
10. WEAK AREA DIAGNOSIS
If you got these wrong, study these topics:
| Questions Missed | Topic to Review | Resources |Generate Flashcards
You are a memory expert creating effective flashcards for learning.
=== TOPIC ===
What to create flashcards for:
# REPLACE: The subject area
# Example: "AWS core services for Solutions Architect exam"
=== SCOPE ===
# REPLACE: What to include
# - EC2 essentials
# - S3 storage classes
# - VPC fundamentals
# - IAM concepts
=== FLASHCARD GOALS ===
# REPLACE: What you need to memorize
# - Definitions of key terms
# - Differences between similar things
# - Key numbers/limits to remember
# - When to use what
=== INSTRUCTIONS ===
Create an effective flashcard deck. Provide:
1. DEFINITION CARDS (15 cards)
FRONT: What is [term]?
BACK:
- Definition: [Clear definition]
- Key point: [Most important thing to remember]
- Example: [Concrete example]
(Generate 15 definition cards)
2. COMPARISON CARDS (10 cards)
FRONT: [Thing A] vs [Thing B]: What's the difference?
BACK:
- [Thing A]: [Key characteristics]
- [Thing B]: [Key characteristics]
- Use A when: [Scenario]
- Use B when: [Scenario]
- Memory trick: [Mnemonic if helpful]
3. SCENARIO CARDS (10 cards)
FRONT: When should you use [feature/service]?
BACK:
- Use when: [Scenarios]
- Don't use when: [Counter-scenarios]
- Alternative: [What to use instead]
4. FACT CARDS (10 cards)
FRONT: [Question about specific fact/number]
BACK:
- Answer: [Fact]
- Why it matters: [Relevance]
- Related: [Connected facts]
5. REVERSE CARDS (5 cards)
FRONT: [Description or definition]
BACK: What is this describing? → [Term]
(Tests recognition from the other direction)
6. MNEMONIC CARDS (5 cards)
FRONT: How to remember [complex topic]?
BACK:
- Mnemonic: [Memory device]
- What each part means: [Breakdown]
7. COMMON MISTAKE CARDS (5 cards)
FRONT: Common mistake with [topic]?
BACK:
- Mistake: [What people often think]
- Correct: [What's actually true]
- Remember: [How to avoid this mistake]
8. APPLICATION CARDS (5 cards)
FRONT: [Real-world scenario]
BACK:
- Best approach: [Solution]
- Why: [Reasoning]
- Avoid: [Wrong approaches]
9. DECK ORGANIZATION
Organize cards by:
| Category | Card Numbers | Priority |
Suggested study order:
1. [Start with these]
2. [Then these]
3. [Finally these]
10. SPACED REPETITION SCHEDULE
| Day | Review Cards | New Cards | Focus Area |
| 1 | - | 10 | Foundations |
| 2 | Day 1 cards | 10 | Building |
| 3 | Day 1+2 (hard only) | 10 | |
Continue for 2 weeks.
EXPORT FORMAT:
(Cards formatted for import to Anki or other apps)Knowledge Assessment Prompts
Identify Knowledge Gaps
You are a learning diagnostician helping identify knowledge gaps.
=== SUBJECT AREA ===
What I'm learning:
# REPLACE: The overall topic
# Example: "Data analysis with Python"
=== WHAT I THINK I KNOW ===
# REPLACE: Topics you feel comfortable with
# - Pandas basics (reading files, filtering, selecting)
# - Basic statistics (mean, median, std dev)
# - Matplotlib simple plots
# - Jupyter notebooks
=== WHERE I'M UNCERTAIN ===
# REPLACE: Topics you're unsure about
# - GroupBy operations (sometimes works, sometimes confused)
# - When to use apply vs transform
# - Time series data
=== MY GOAL ===
# REPLACE: What you're working toward
# Example: "Be able to independently analyze datasets and create reports for my team"
=== INSTRUCTIONS ===
Conduct a knowledge gap analysis. Provide:
1. CORE SKILLS ASSESSMENT
For this subject area, the essential skills are:
| Skill | Your Assessment | Importance | Gap? |
| [Skill 1] | Know / Partial / Don't Know | Critical/Important/Nice to Have | Y/N |
Based on what you described, here's my assessment of your gaps:
2. DIAGNOSTIC QUESTIONS
Answer these to reveal gaps:
FUNDAMENTALS:
Q1. [Question testing core concept]
If you struggle with this: [What gap this reveals]
Q2. [Question]
If struggle: [Gap]
(Continue for 10 questions across levels)
INTERMEDIATE:
Q3-6...
ADVANCED:
Q7-10...
3. KNOWLEDGE MAP
Confident ─────────── Uncertain ─────────── Unknown
[Your skills placed on this spectrum]
Breaking down by category:
| Category | Green (solid) | Yellow (shaky) | Red (gap) |
4. PRIORITY GAPS
Gaps that matter most for your goal:
| Priority | Gap | Why It Matters | Impact on Goal |
| 1 | | | Blocking |
| 2 | | | Significant |
| 3 | | | Nice to fix |
5. ROOT CAUSE ANALYSIS
For key gaps, what's the underlying issue?
GAP: [Topic you don't know well]
Root cause: [Why this gap exists]
- Missing prerequisite?
- Not enough practice?
- Conceptual misunderstanding?
- Never learned it?
6. PREREQUISITE CHECK
For your uncertain areas:
| Topic | Prerequisites | Do You Have Them? |
You might be struggling with [X] because you're missing [Y].
7. GAP CLOSURE PLAN
For each priority gap:
GAP: [Topic]
To close this gap:
1. [Specific learning action]
2. [Practice activity]
3. [How to verify it's closed]
Time estimate: [Hours needed]
Resources: [What to use]
8. VERIFICATION CHECKPOINTS
How to know when gaps are closed:
| Gap | Closed When You Can... | Self-Test |
9. QUICK WINS
Gaps you could close quickly:
| Gap | Time to Close | Action |
These would give you quick confidence boosts.
10. RECOMMENDED LEARNING PATH
Given your gaps, optimal study order:
| Order | Topic | Why This Order | Time |
| 1 | [Most foundational gap] | Unblocks others | |
| 2 | | | |Test Understanding
You are an expert assessor testing depth of understanding.
=== TOPIC ===
What to test:
# REPLACE: The topic you've been studying
# Example: "Object-oriented programming in Python"
=== WHAT I'VE LEARNED ===
# REPLACE: What you've studied
# - Classes and objects
# - Inheritance
# - Encapsulation
# - Polymorphism
# - Magic methods
=== TEST INTENSITY ===
# REPLACE: How rigorous should this be?
# Example: "Thorough - I want to really test myself before my technical interview"
=== INSTRUCTIONS ===
Create a comprehensive understanding test. Provide:
1. EXPLAIN IT BACK
Explain these concepts as if teaching someone:
1. What are classes and why do they exist?
[Space for your explanation]
Good answer includes: [Criteria]
Missing if you don't mention: [Key elements]
2. [Another concept]
(5 explanation prompts)
2. PREDICT THE OUTPUT
What does this code/scenario produce?
Scenario 1:
[Code or situation]
Predict: What happens and why?
Actual: [Answer]
If wrong: This means you don't fully understand [concept]
3. SPOT THE ERROR
What's wrong and how to fix it?
Problem 1:
[Code/scenario with subtle error]
The error: [What's wrong]
The fix: [Correct version]
The lesson: [What this tests]
4. DESIGN CHALLENGE
Apply your knowledge:
Design [something] using [concepts].
Requirements:
- [Requirement 1]
- [Requirement 2]
Good solution characteristics: [What makes a good answer]
5. RAPID FIRE QUESTIONS
Answer quickly (30 seconds each):
1. [Quick question]
2. [Quick question]
(10 questions)
Answers: [List]
Scoring: 8+/10 = solid, 5-7/10 = review needed, <5/10 = re-learn
6. SCENARIO ANALYSIS
Given this real situation:
[Detailed scenario]
Questions:
a) How would you approach this?
b) What would go wrong if you [incorrect approach]?
c) What's the best solution and why?
7. TEACH THE EDGE CASES
Explain what happens in these unusual situations:
1. What if [edge case]?
2. What happens when [unusual scenario]?
If you can explain these, you truly understand.
8. CONNECT THE DOTS
How does [concept A] relate to [concept B]?
| Concept A | Concept B | Relationship |
| | | |
If you can state relationships, understanding is deep.
9. CHALLENGE PROBLEMS
Problems at interview level:
Challenge 1:
[Difficult problem]
Solution approach: [Hidden until solved]
10. ASSESSMENT SUMMARY
Based on your answers:
| Area | Strength Level | Evidence |
| | Strong/Medium/Weak | |
Overall readiness: [Assessment]
Priority review: [What to study more]Career Development Prompts
Create Skill Gap Analysis
You are a career development coach conducting a skill gap analysis.
=== CAREER GOAL ===
Target role:
# REPLACE: The role you're aiming for
# Example: "Senior Frontend Developer at a tech company"
Timeline:
# REPLACE: When you want to reach this goal
# Example: "Within 12 months"
=== CURRENT SITUATION ===
Current role:
# REPLACE: Your current position
# Example: "Junior Frontend Developer, 2 years experience"
Current skills:
# REPLACE: What you can do now
# - React (comfortable building components, hooks)
# - JavaScript (ES6+, async/await)
# - CSS (Flexbox, Grid, some Tailwind)
# - Git (basic workflows)
# - REST APIs (consuming them)
=== TARGET ROLE REQUIREMENTS ===
# REPLACE: What you know the target role requires (from job postings, etc.)
# - Lead frontend architecture decisions
# - Mentor junior developers
# - TypeScript required
# - Testing (unit, integration, e2e)
# - Performance optimization
# - System design for frontend
=== INSTRUCTIONS ===
Conduct a comprehensive skill gap analysis. Provide:
1. ROLE REQUIREMENTS BREAKDOWN
Complete skills needed for target role:
| Skill Category | Required Skills | Proficiency Needed |
| Technical | | Expert/Proficient/Familiar |
| Leadership | | |
| Process | | |
| Soft Skills | | |
2. CURRENT STATE MAPPING
| Required Skill | Your Current Level | Gap Size |
| | None/Basic/Intermediate/Advanced | Large/Medium/Small/None |
3. GAP VISUALIZATION
Target Role Requirements:
████████████████████████████████████████ 100%
Your Current Skills:
████████████████░░░░░░░░░░░░░░░░░░░░░░░░ 45%
By category:
| Category | Target | Current | Gap |
| Technical | | | |
| Leadership | | | |
4. PRIORITY GAPS
Rank gaps by importance:
| Priority | Skill Gap | Why Critical | Impact |
| 1 | | Mentioned in every job posting | Must have |
| 2 | | Key differentiator | Strong advantage |
| 3 | | Nice to have | Helps |
5. SKILL DEPENDENCIES
What needs to be learned first:
You need [Skill A] before [Skill B] because [reason].
Recommended order:
1. [First skill to develop]
2. [Second skill]
3. [Third skill]
6. DEVELOPMENT PLAN
For each priority gap:
SKILL: [Gap Name]
Current: [Where you are]
Target: [Where you need to be]
How to develop:
- Learning resources: [Specific recommendations]
- Practice activities: [What to do]
- Projects to build: [Concrete projects]
- Time estimate: [Hours/weeks]
Milestones:
- Week 2: [Checkpoint]
- Week 4: [Checkpoint]
- Week 8: [Competency]
7. QUICK WINS
Skills you can develop quickly:
| Skill | Time to Develop | Actions |
These will build confidence and fill gaps fast.
8. STRETCH GOALS
Beyond requirements, what would make you exceptional:
| Stretch Skill | Why Valuable | Effort |
9. EVIDENCE BUILDING
How to demonstrate these skills:
| Skill | Portfolio Piece | How It Shows Skill |
Concrete projects/artifacts to build.
10. TIMELINE TO CLOSE GAPS
| Month | Focus Area | Milestone | How to Verify |
| 1-2 | | | |
| 3-4 | | | |
| 5-6 | | | |
12-month roadmap to target role readiness.Prepare for Certification
You are a certification prep coach creating a study plan.
=== CERTIFICATION ===
Target certification:
# REPLACE: Which certification you're pursuing
# Example: "AWS Solutions Architect Associate (SAA-C03)"
Exam date:
# REPLACE: When you plan to take the exam
# Example: "March 15, 2025 (10 weeks away)"
=== CURRENT KNOWLEDGE ===
Relevant experience:
# REPLACE: Your background
# Example: "1 year using AWS at work - EC2, S3, RDS. No VPC experience."
Previous attempts:
# REPLACE: Any prior history
# Example: "None - first attempt"
=== AVAILABLE TIME ===
Study hours per week:
# REPLACE: How much time you can dedicate
# Example: "15 hours (evenings and weekends)"
=== RESOURCES AVAILABLE ===
# REPLACE: What you have access to
# - AWS Free Tier account
# - Purchased: Stephane Maarek's Udemy course
# - Free: AWS Skillbuilder
=== INSTRUCTIONS ===
Create a comprehensive certification prep plan. Provide:
1. EXAM OVERVIEW
| Domain | Weight | Topics | Difficulty |
| Domain 1 | X% | | |
Total: X questions, X minutes, passing score X%
2. KNOWLEDGE MAPPING
| Exam Domain | Your Current Level | Study Priority |
| | Strong/Moderate/Weak/None | High/Medium/Low |
3. WEEK-BY-WEEK STUDY PLAN
WEEK 1: [Focus Area]
- Topics: [What to cover]
- Video/Reading: [Specific resources]
- Hands-on: [Labs to complete]
- Practice questions: [Number/source]
- Hours: [Allocation]
- End-of-week goal: [Specific checkpoint]
(Continue for all weeks)
4. DOMAIN DEEP DIVES
For each exam domain:
DOMAIN: [Name]
Weight: X%
Key topics:
1. [Topic A] - [Study resources]
2. [Topic B] - [Study resources]
Must-know concepts: [List]
Common exam questions: [Examples]
Hands-on labs: [Specific labs]
5. PRACTICE EXAM STRATEGY
| Week | Practice Activity | Goal Score |
| Week 4 | First practice exam | Baseline |
| Week 6 | Domain-specific quizzes | |
| Week 8 | Full practice exam | 70%+ |
| Week 9 | Final practice exam | 80%+ |
6. HANDS-ON REQUIREMENTS
Labs that are essential:
| Lab | Domain | Time | Why Critical |
Don't skip these - they're exam favorites.
7. WEAK AREA PROTOCOL
If practice exams reveal weak areas:
Day 1: [Diagnostic action]
Day 2-3: [Focused study]
Day 4: [Practice questions]
Day 5: [Re-test]
8. EXAM DAY STRATEGY
- Before exam: [Prep activities]
- During exam: [Time management strategy]
- Question approach: [How to tackle different types]
- Flagging strategy: [When to mark and return]
9. LAST WEEK PLAN
Final week before exam:
| Day | Activity | Duration |
| 7 days before | | |
| 6 days before | | |
(Through exam day)
10. BACKUP PLAN
If not ready by exam date:
- Reschedule criteria: [When to postpone]
- Focus areas if rescheduling: [What needs more time]
- New timeline: [Adjusted plan]Quick Reference
| Need | Prompt to Use |
|---|---|
| Learning Plans | |
| Create study roadmap | Create Learning Roadmap |
| Understand topic structure | Break Down Complex Topic |
| Plan your study week | Create Weekly Study Schedule |
| Concept Mastery | |
| Understand something | Explain Concept Simply |
| Check your understanding | Feynman Technique Learning |
| See concrete examples | Learn Through Examples |
| Practice & Testing | |
| Practice problems | Generate Practice Problems |
| Self-assessment | Create Quiz Questions |
| Memorization | Generate Flashcards |
| Knowledge Assessment | |
| Find what you don’t know | Identify Knowledge Gaps |
| Test yourself thoroughly | Test Understanding |
| Career Development | |
| Close skill gaps | Create Skill Gap Analysis |
| Prepare for certification | Prepare for Certification |
Tips for Better Learning Prompts
1. State Your Current Level Clearly
❌ "Teach me machine learning"
✅ "Teach me machine learning. I'm a Python developer with strong programming
skills and basic statistics knowledge. I've never done ML before but
understand what it is conceptually."2. Be Specific About What Confuses You
"I understand that neural networks have layers, but I don't understand
what 'backpropagation' means or why you need activation functions."3. Define Your Goal
"My goal is to pass the AWS Solutions Architect exam in 8 weeks"
vs
"My goal is to understand enough AWS to build a simple web app"
(Very different learning paths!)4. Request Your Preferred Explanation Style
"Explain with real-world analogies - I learn better with comparisons
to things I already know."
"Give me the formal definition first, then examples."5. Ask for Verification Questions
"After explaining, give me 3 questions to check if I understood correctly."6. Request Progressive Difficulty
"Start with the simplest example possible, then gradually add complexity."7. Ask for Common Mistakes
"What do beginners usually get wrong about this?"
"What misconceptions should I avoid?"Workflow: Learning a New Skill
Here’s how to combine prompts for complete skill acquisition:
Phase 1: Planning Use: Create Learning Roadmap → Break Down Complex Topic
Phase 2: Scheduling Use: Create Weekly Study Schedule
Phase 3: Learning Use: Explain Concept Simply → Learn Through Examples
Phase 4: Deepening Use: Feynman Technique Learning → Generate Practice Problems
Phase 5: Assessment Use: Create Quiz Questions → Identify Knowledge Gaps
Phase 6: Mastery Use: Test Understanding → Generate Flashcards (for retention)
What’s Next
- 📚 AI Prompts for Writing — Document your learning
- 📚 AI Prompts for Research — Deep dive into topics
- 📚 AI Prompts for Problem-Solving — Apply your knowledge
- 📚 Prompt Engineering Fundamentals — Master prompting itself
Found these prompts helpful? Share them with fellow learners!