Read https://cleaning-ops.ignition-desk.workers.dev/prompts and study how that prompt library is built. Then build me the same thing for something completely different.
Before you build anything, work out the pattern and tell it back to me in a few lines, so I know you actually looked: how the phases are ordered, how each prompt card is structured, what the one-line promise under each title is doing, what the three category tags mean, and what all the prompt bodies have in common.
The rules that matter, in case you miss them:
- Every prompt is fully self-contained. It restates its own context and never refers to another prompt, so any single one can be dropped into a blank chat and still work.
- Every prompt asks for a durable artifact — a page, a tracker, a script, a calculator, a checklist — not a conversational answer.
- Every prompt is written in my voice talking to Claude: first person, specific, blunt, with real numbers rather than placeholders like "your budget".
- The phases run in the order I'd actually hit them, and they include the unglamorous ones most people skip: the legal bit, the money bit, the day it goes wrong, and the way out.
- Anything that changes from person to person is a swappable placeholder, not hard-coded.
Then interview me about what I want a pack for. Do not assume it's a business. It might be a side project, a research question, moving to another country, a health or fitness goal, learning an instrument, a wedding, a novel, a job hunt, a house renovation, or something I haven't thought of. Ask me what it is, what "done" looks like, what stage I'm at right now, what I'm quietly worried about, and which parts I already know how to do — so you don't waste prompts on those.
Then propose the pack as an outline first: the phases with one line each, and under them every prompt title with its category and its one-line promise. Make me approve that outline before you write a single prompt body.
Push back while you're doing it. If my thing only needs twelve prompts, say twelve and don't pad it to forty. If I've described three phases that are really one, merge them. If there's an obvious phase I've skipped because it's the hard part, name it and put it in anyway.
Once I approve the outline, write every prompt in full in that same voice and format. Then build it as a page shaped like the one you read: phases as sections, a search box, filters per phase, a copy button on every prompt, and my entries saved so I can come back to it.
Finish by telling me which three to run first, and why those three.