Someone opened a new chat and typed the one question most people never think to ask.
Not “give me your top 10 prompting tips.” Something more specific: “If you were going to teach someone prompt engineering properly in 30 days, not surface level, not tips and tricks, what would the curriculum look like?”
What came back beat every paid course they had taken. The response was structured, specific, and sequenced in a way that actually built on itself. User u/AdCold1610 followed the plan for 30 days on r/ChatGPTPromptGenius. Here’s what the curriculum actually covered, and why it worked.
🧠 Why This Approach Changes Things
Most people learn prompting by accident. Something works. They use it. Something better shows up. They switch. No understanding of why. No skill that transfers. The result is a pile of templates that work sometimes and a vague sense that the AI is unpredictable.
That ceiling hits fast if you work with AI tools daily. Structured learning compounds. Accidental learning doesn’t. By week three of this curriculum, the original poster wasn’t following the plan anymore. They were seeing prompt problems differently, noticing failure modes before they happened, catching ambiguous instructions before hitting send. That shift doesn’t come from reading tip lists.
📋 The Four-Week Breakdown
Week 1 covers the foundations most people skip.
Days 1 through 3 focus on how the model actually processes input. Not the technical architecture. The practical implications. Why word order matters. Why the same words in a different sequence produce different outputs. A quick experiment worth running: take one prompt, rearrange the sentences, run both versions. The gap in output quality tends to surprise people the first time.
Days 4 and 5 tackle the difference between instructions and context. Most people only give instructions. Context is what makes instructions land. “Write a product description” is an instruction. Adding the target audience, the tone you want to avoid, and the one objection you need to address is context. Learning to separate these two changes how you write every prompt.
Days 6 and 7 cover output specification. Vague prompts produce vague results, every time. Specifying format, length, tone, audience, and what “done” looks like is its own learnable skill.
Week 2 gets into thinking structures.
Chain of thought: not as a trick, but as a genuine reasoning tool. Knowing when to force visible reasoning versus when it just adds noise.
Few-shot prompting done correctly: placement, quantity, and diversity of examples all affect output in ways that aren’t obvious until you test them deliberately. Three well-chosen examples consistently outperform ten mediocre ones. Quality of demonstration matters more than volume.
Negative constraints: telling the model what NOT to do is consistently underused and consistently powerful. The curriculum spends two full days here.
Week 3 moves into advanced patterns.
Persona design: not “act like an expert.” Building an actual character with specific knowledge, specific blind spots, specific ways of framing problems. The specificity is the whole point.
Conversation architecture: designing multi-turn interactions, not single prompts. What information goes where. How to maintain context. How to checkpoint and verify before going deeper.
Uncertainty surfacing: prompting the model to show where it’s confident versus where it’s guessing. Possibly the most underused skill in practical prompt engineering. Ask the model to flag anything it’s less than 80% sure about, and watch how much more useful the output becomes.
Week 4 is applied and meta.
Task decomposition: breaking complex problems into prompt sequences where each output feeds the next. The difference between one prompt and a system.
Prompt auditing: taking existing prompts apart to understand why they work or don’t. Reverse engineering good outputs to find the input decisions that produced them.
The final day: build one complete prompt system for a real recurring problem in your work. Not an exercise. Something you’ll carry into Day 31.
💡 Tips Before You Start
Skip expensive courses. The best free resources: Anthropic’s prompt engineering documentation (free, and better than most paid alternatives), DeepLearning.AI’s short courses on prompt engineering for developers, and Simon Willison’s blog for real-world application. All three together cost you nothing except time.
One hour a day is enough. The compounding happens at week three. Week one feels slow. Week two clicks. Week three you start seeing inputs differently. If you miss a day, don’t restart. Just pick up where you left off and keep going.
When you reach the Week 4 capstone, build the system for something you actually do at work. Not something theoretically interesting.
🚀 How to Start Today
The curriculum is free. Open Claude and ask: “If you were going to teach someone prompt engineering properly in 30 days, not surface level, not tips and tricks, what would the curriculum look like?”
Adapt what comes back to your actual work context. Then follow it deliberately for 30 days. The full discussion and additional resources are in the original r/ChatGPTPromptGenius thread.
Frequently Asked Questions
Q: Should I follow the 4-week structure or use a more detailed module-based approach?
Both work. The 4-week version is focused and intense; some people prefer that sprint, while others want depth and break it into 10+ modules. Pick whichever matches your learning style. The real test is building something with each concept and measuring whether your prompts actually improve, that’s how you know if the structure works for you.
Q: How do I know I’m asking Claude the right question about curriculum design?
More specific beats generic. Instead of “teach me prompting,” try “what curriculum for building a customer support bot?” or “…if I only have 2 weeks?” Your constraints and goals shape the answer. Test a few variations, takes minutes and often surfaces better paths. The OP’s question was strong, but iteration usually beats the first try.
Q: Is it OK to just use Claude’s curriculum directly without adapting it?
Yeah, it’s fine. The trap isn’t using AI-generated content; it’s treating it like passive reading. Actually apply each lesson, build test prompts, iterate, measure results. The curriculum provides the framework, but you build skill through doing. Apply concepts to real work and that’s when it sticks.
Q: How do I actually measure if this 30-day approach is working?
The post doesn’t share results, so create your own benchmark. Take a task you currently prompt for (research, writing, coding) and compare your “before” prompts to your “after” prompts. Better output = it’s working. No improvement? You might need to experiment more or spend extra time on concepts that aren’t landing yet.
I asked Claude to teach me everything it knows about prompting. it gave me a curriculum. i followed it for 30 days.
by u/AdCold1610 in ChatGPTPromptGenius