Copy each prompt, paste it into Claude, and replace the yellow [brackets] with your own words before you send.
Chat 1 · Plan it
Open Claude on a new, empty folder for this project.
1Explain your idea and get grilled
Claude asks a few numbered questions at a time, each with a suggested answer. Reply by number, like "1 yes, 2 only our team". Not sure? Write "what do you recommend?"
Need an idea? An event-day crew checklist, a vendor contact sheet, or a quick package calculator for client calls.
Y
/grill-me
I want to build: [your idea]
Who will use it: [me / our team / our clients]
The problem it solves: [what is annoying or slow today]
What I already have: [files, screenshots, examples, or "nothing"]
I'm not technical, so use plain words.
Don't build anything yet. When we're done, save everything we agreed, including what we left out, in BRIEF.md, and show me a short summary.
Typing /grill-me does nothing? Paste this once, then start again:
Y
Install the grill-me skill from https://github.com/mattpocock/skills (with the grilling skill it uses) so it works in every project. Tell me when it's ready and whether I need to open a new chat.
2Get a plan, checked by a skeptic
Claude writes a short plan, then a second, skeptical Claude looks for holes. Nothing gets built yet.
Y
Read BRIEF.md and write a short plan in PLAN.md, in plain words:
- What it's for, in 2–3 sentences
- What I see and do on each screen, step by step
- Where the information comes from, whether it's kept when I close the page, and who else can see it
- What's not in this version
- A short checklist I can use to test it myself
Keep it simple: one HTML file I open by double-clicking, with nothing to install. Don't write any code yet.
Then have a skeptical subagent check the plan against BRIEF.md for anything missing, too complicated, or private that could leak. Fix what's unclear, and ask me about anything that changes what I get.
Finally, show me "what's not in this version" and the test checklist.
3See a preview and approve it
A plan in words is hard to picture. Look at the preview and ask for changes until it's what you want.
Y
Using PLAN.md, make preview.html: a quick mock-up of each screen with realistic example data, that opens by double-clicking.
Buttons don't need to work, and don't build the real thing yet.
Tell me how to open it, then ask me what to change. Update the preview and PLAN.md until I say "approved".
Chat 2 · Build it
Open a new chat in the same folder.
4Build it in one go
A fresh Claude builds everything and tests it. Keep your computer awake. If it asks to delete, send, pay or use a password, say no and ask Shay.
Y
Read BRIEF.md and PLAN.md, and use preview.html as the approved look.
Build the whole thing in one go as index.html in this folder: one file that opens by double-clicking, with nothing to install. Include clearly marked example data so it isn't empty at first.
Don't stop to ask me. If something is unclear, pick the simplest option and note it under "Decisions" at the end of PLAN.md.
Stay inside this folder: don't send, publish or delete anything, and don't use my accounts.
Then go through every item on the test checklist. If you can't open it in a browser, check the code carefully and tell me which items I need to check myself. Fix what fails.
Finish with a plain-words note: how to open it, what you tested, and what's not done.
5Test it and fix what's off
Double-click index.html and go through the checklist. If something is wrong, say what happened, not how to fix it.
Y
I tested it.
What I did: [the steps you took]
What happened: [what you saw; add a screenshot if you can]
What I expected: [what should have happened]
First save a copy of index.html in a folder called backup, with the date and time in the name. Then fix only this, without changing anything else.
Then go through the test checklist in PLAN.md again so nothing else broke, and tell me exactly how to check it.
If what I expected isn't in PLAN.md, ask me before adding it.
