Copy one first
Pick one small, real thing in your project. For example, add an export button to a Chrome extension’s settings page:
/pstack:poteto-mode Add an “Export settings” button to the settings page that downloads the current settings as a JSON file. The existing settings and how they're saved must not change. When done, show me: the exported file's contents and what's stored in chrome.storage. The two must match exactly.This message has just three parts:
- What you want: an export button.
- What counts as done: the export matches what’s stored, and the old settings aren’t affected.
- What to show you: the actual contents of both.
The author’s advice for beginners fits in one line: give it a goal and a way to check, in your own words.
When an AI gets something wrong, it’s usually one of two things. It didn’t understand what you wanted, or it lacked the background to do it right. These three parts handle the first. Step 4 handles the second: before it changes anything, have it explain the code as it is now.
Make “done” something you can check
It uses this part to check its own work. So it has to be a clear pass or fail.
- Checkable: the exported file matches what’s stored, exactly.
- Not checkable: make it better. Make it look nicer. Spend an hour on it.
Without a check, it can only go by feel when it says “done.”
Two things you can add
They’re optional. If you have them, add one sentence each:
- Clues you already have: an error line, the step where it breaks, a link. It saves a round of searching.
- What it really must not touch: for example, “Don’t change code yet, just investigate,” or “The old output must not change at all.”
Two things to leave out at first
- Exactly how to do it. Say the result you want. It may find a better way.
- Your guess at the cause. Once you say it, it only looks where you pointed. Wait until it gives its own view, then add yours.
Also, don’t line up skills in your message, like “use /pstack:how first, then /pstack:architect.” It calls them in order on its own. Your order can get in its way.
After you send it, look in three places
At the start: its restatement. It says in its own words what you want and where it plans to change things. It won’t wait for your OK. So if it got it wrong, interrupt right away.
In the middle: the todo list. These are the steps it will take next. Once it picks an approach (a playbook), that approach’s steps are copied into the list. Steps it decides to skip stay on the list too, marked skip: with a reason.
At the end: evidence. What you asked to see should be here, like real commands and their output. If it couldn’t check something, it says “not sure.”
Keep going: shorter is better
Within the same task, follow-ups can be very short:
/pstack:poteto-mode go ahead
continue
keep going until it's doneIt remembers how far the task has gotten. You only need to say what you want next.
When you switch to something else, say “new task” first. Otherwise it treats your new question as the next step of the last task:
/pstack:poteto-mode new task. Find out why the cache is still there after logging out. Don't change any code yet.“Don’t change any code yet” makes it only investigate, without touching anything.
Stuck?
It misunderstood what I meant.
Just say so: “No, what I want is…”. It’s easiest to fix at its first restatement. When the request is messy (a long discussion, a problem you can’t quite describe), have it only restate things first: /pstack:poteto-mode Read this discussion and say in plain words what the root problem is. Don’t change any code yet.
It skipped a step I think matters.
Read the reason after skip: on that item. If you disagree, say: “Don’t skip step 2. Make the problem happen again first.”
The reply is too long to follow.
Type /pstack:bro, and it will say the last reply again in plain words.
Before moving on, check
✓ All ticked — on to the next step.