You’re early. I haven’t written a word until now — that changes today.
Intro for those who don’t know me yet. I deploy AI inside a real enterprise for a living — over a million dollars of it shipped to date. By day I’m in the meetings, the procurement calls, the rollout decks. By night I write @mattymoe.ai for operators, marketers, founders, and salaried humans who never wanted to be engineers but accidentally became them.
One email. One workflow you can copy. That’s the contract.
Let’s get into it.
THE THING ALMOST NOBODY KNOWS ABOUT
Anthropic ships a feature inside the Claude Console called Generate a Prompt. It’s free. It takes ten seconds to find. And it writes better prompts than you do.
I’m not exaggerating. I’ve been writing prompts professionally for two years — it’s literally part of my day job — and this tool consistently produces prompts that outperform mine on the first try. Not because I’m bad at prompting. Because Anthropic built a system that knows exactly how Claude thinks, and it uses that knowledge to construct prompts the way Claude wants to receive them.
If you’ve ever sat there staring at a chat window trying to figure out how to phrase what you want, this is the unlock.
WHAT IT ACTUALLY DOES
You go to console.claude.com, sign in (free account works), and hit “Generate a prompt” in the dashboard. You type one sentence describing what you want — “help me write cold emails for SaaS founders,” “review my Notion docs for clarity,” “build me a workout plan based on my weekly schedule” — and it produces a full structured prompt, complete with role definition, instructions, examples, output format, and edge case handling.
The prompts it generates are 200-400 words long. They include XML tags, few-shot examples, and instruction hierarchies. They look like what an Anthropic engineer would write if you paid them to write a prompt for you. Because that’s essentially what they are.
You can then copy that prompt into Claude.ai, ChatGPT, or anywhere else and run it. It will work better than the three-line version you would have written yourself. Every time.
WHY THIS MATTERS MORE THAN IT SOUNDS
The bottleneck for most people using AI isn’t the model. The models are already smarter than you need them to be for 95% of tasks. The bottleneck is the prompt. A bad prompt to a great model produces mediocre output. A great prompt to the same model produces work you’d pay a contractor for.
Most non-engineers learn this the wrong way. They write a half-sentence prompt, get a mediocre answer, conclude AI is overrated, and go back to doing things the slow way. They never see what these models can actually do because they never wrote a prompt good enough to find out.
Generate a Prompt collapses that learning curve to zero. You describe the outcome you want. It builds the prompt. You skip the years of trial and error.
THE THREE WORKFLOWS WHERE THIS HAS CHANGED HOW I WORK
Building reusable workflows for repetitive tasks.
I have a weekly task where I review the previous week’s content performance and decide what to do next. Used to take me an hour of staring at spreadsheets. I described the task to Generate a Prompt in one sentence. It built me a 350-word prompt that asks for the inputs, structures the analysis, identifies the top three patterns, and outputs a one-page action plan. I saved it as a template. The task now takes seven minutes.
Onboarding non-technical people to AI.
When someone on my team says “I don’t know how to use Claude for X,” I don’t teach them prompting anymore. I sit them down at the Console, watch them describe what they want in plain English, and let the tool build the prompt. They get a working result on the first try. They learn what good prompts look like by reading the ones the tool generates for them.
Stress-testing my own prompts.
When I write a prompt I think is good, I now describe the same task to Generate a Prompt and compare. About half the time, the generated version is meaningfully better. I steal what works and incorporate it into my own writing. My baseline has gotten significantly better over the last three months just from this exercise alone.
TRY IT THIS WEEK
Three steps:
Go to console.claude.com and sign in (free account is fine)
Click “Generate a prompt”
Type one sentence describing a task you do every week — anything you wish you had a better system for
That’s it. Take the prompt it generates, paste it into Claude.ai, and run it on a real input. See what happens. Reply to this email and tell me what you tried. I’m genuinely curious which workflows this unlocks for people.
WHAT’S COMING
Issue #2 next Tuesday: how I use Claude Code from the terminal to run this newsletter — research, drafts, the whole thing — and I’m not a developer.
If something here landed, reply and tell me. If something didn’t, reply and tell me that too. I read every one.
Make moe money,
Matt
@mattymoe.ai