// in this post
Most L&D teams know AI could help. Far fewer know what to actually type into it.
The problem
The blank prompt box is where good intentions go to die. Someone sits down to use AI for a real training need, draws a blank, types something vague, gets something generic back, and quietly decides it isn't for them. The tool was never the issue. Knowing what to ask was.
What it is
130 prompts built around the 13 jobs L&D actually does: needs analysis, learning design, content drafting, assessment, facilitation, evaluation, and the rest. Each one is written to be copied, pasted, and adapted, not admired. They came out of real engagements, so they assume the messy reality of the role rather than a textbook version of it.
Who it's for
Learning and development professionals who want to stop experimenting and start getting useful work back from AI on the first attempt.
How I made this
This whole thing is an afternoon's work in the regular Claude chat, plus a little Claude Code if you want to put it online. Here's the full run-through.
1. Generate the prompts. Open Claude at claude.ai (in a browser, or the Claude desktop app), start a chat, and paste this:
You are helping me build a prompt pack for [your role or field].
First, list the 10 to 15 core jobs someone in this role does day to day.
Concrete and practical, not a textbook taxonomy.
Then, for each job, write 8 to 10 prompts I could paste into an AI assistant
to get genuinely useful work back. Each prompt should:
- be written to be copied, pasted and adapted, not admired
- assume the messy reality of the role, not an idealised version
- ask for a specific, usable output, not a generic essay
- leave [bracketed placeholders] for the details I'd fill in
Group the prompts under their job. Plain language. No preamble.
I started from the 13 jobs L&D actually does rather than letting it invent the categories.
2. Refine, one job at a time. Paste in a real example of the work and ask Claude to make each prompt more specific. Keep only the ones that earn a place. I ended up with 130.
3. Save it. Ask Claude to output the finished set as one Markdown file. That's a usable pack on its own.
4. (Optional) Make it a web page. I handed that Markdown to Claude Code (Anthropic's coding assistant, which you run from your terminal or the desktop app) and asked for a single self-contained HTML page that lists the prompts in categories with a copy button. It comes back as one index.html, no backend.
5. Put it online. I deployed that file to Vercel (vercel.com, free at this size): connect a folder or a GitHub repo, or drag the file in, and it's live on a URL in under a minute. I pointed a custom domain at it (prompts.thehumanco.org); you can just use the address Vercel gives you.
Stop at step 3 if you only need the prompts. Steps 4 and 5 are for when you want to hand it to other people.