Not just what to type.
How to think.
Everyone teaches prompts. Nobody teaches the thinking behind them. These guides cover the mental models that separate people who get extraordinary results from people who think AI is overrated.
- Why generic questions produce generic answers
- The five things to include in any serious prompt
- How to ask Claude what context it needs
- How to set up a Project that never forgets you
- The Pre-Mortem: assume it failed, work backwards
- The Devil's Advocate: argue the opposite
- The Blind Spot Finder: what you're not seeing
- 5 more techniques, each with a ready-to-copy prompt
- The five-question verification framework
- What to trust vs. what to check independently
- Red flags that should trigger your scepticism
- The self-audit prompt that surfaces hidden problems
- What Claude Pro's Projects actually change
- What the API unlocks (and how simple it is to start)
- What Claude Code is and who it's really for
- MCP servers in plain English
If you're starting from scratch
Read the guides in order. Each one builds on the last. Then do Prompt School to put it into practice.
Start here: The Blank Slate Problem
Understand why context is everything. Read this before you do anything else. Read →
Then: Prompt School
Eight lessons that build the core skills. Takes about an hour. Start →
Then: The Thinking Partner
Eight techniques for using Claude to reason, not just produce. Read →
Then: Testing Your Output
How to verify before you act. The skill most people skip. Read →
When you're ready: The Tool Progression
Only when you've built the habit. Then decide what level you actually need. Read →
Jump to what you need
If you use Claude but feel like you're not getting the most out of it, these are the highest-leverage things to fix first.
Now go use it.
Reading about prompting is useful. Actually prompting is better. Open Claude, pick a real problem from your life, and apply one thing from the guides you just read.