In this lesson you use pstack to make something real and small: a web page that tracks how many glasses of water you drink each day. By the end you’ll see how it differs from the AI as usual.
First, make an empty folder
- Make a new folder on your desktop called
water. - If Claude Code is open, type
/exitto quit. - In the same window, type this line and press Enter. It means “go into the water folder on the desktop”:
- Type
claudeand press Enter. Claude Code opens inside that folder.
Why a new folder: the AI works in whatever folder you open Claude Code in. In a new, empty folder, it can’t touch anything else on your computer.
Desktop
- Work files
- Photos
- waterThe AI works here
Your other folders stay out of reach
Send it this message
/pstack:poteto-mode Make me a small web page that tracks how much water I drink each day. This is an empty folder; do whatever setup it needs.
What done looks like: I open the page and click "I drank a glass," and today's count goes up by one; I close it and open it again and the number is still there; the page shows how many glasses I drank on each of the last 7 days.
When you're done, show me: how you checked it, what you did and what you saw, with a screenshot if you can. Then tell me how to open the page.The /pstack:poteto-mode at the start is the switch. With it, the AI follows pstack’s rules. Without it, it works the way it always does.
The rest of the message has just three parts, and that’s the whole trick to using pstack:
What I want · What done looks like · What to show me when it’s done1/pstack:poteto-mode2Make me a small web page that tracks how much water I drink each day.3Click “I drank a glass” and today's count goes up by one; it's still there after I reopen it; it shows the last 7 days.4How you checked it and what you saw, with a screenshot if you can.
- 1The switch
- 2What I want
- 3What done looks like
- 4What to show me
- What I want: a page that tracks water.
- What done looks like: clicking adds one, the number survives closing and reopening, and you can see 7 days. This tells it “how to know it’s done,” and it will check each of these.
- What to show me when it’s done: how it checked and what it found. You can’t read the code, so ask for something you can understand.
It will stop and ask you things
It will work for a few minutes. Along the way, Claude Code stops to ask: may I create this file? May I run this command?
That’s Claude Code protecting you: every step needs your OK. This folder is new and empty, so pick Yes.
Where to look in its reply
Its reply will be longer than usual and may be full of technical words. Skip what you don’t understand and look only at the four marked places:
① My understanding of the goal: a page that tracks water. Clicking
"I drank a glass" adds one to today's count; the number survives
closing and reopening; it shows the last 7 days.
② To do
☐ Set up this folder
☐ Build the page
☐ Check: add a glass, close and reopen, see 7 days
☐ Hand you the results
… (the middle is it doing the work; you can skip it) …
③ What I checked
✓ Clicked "I drank a glass" 3 times; today shows 3
✓ Closed the page and opened it again; still 3
✓ There's a bar for each of the last 7 days; today's is tallest
? Couldn't check: how it looks on a phone (I only checked on a computer)
④ How to open it: double-click index.html in the water folder- Look at ① first. Did it get it right? If not, just type a correction, like “not 7 days, 30 days.”
- ② is the steps it plans to take. It ticks them off as it goes. You don’t need to manage it.
- ③ matters most. Each line says what it did and what it saw. The “couldn’t check” line is it being honest, and that’s a good thing.
- Do what ④ says and look for yourself.
How to tell whether it did well
Ask yourself three questions:
- Is the goal it repeated back the same as what I meant?
- When it said it was done, did it list the checks it actually did and what it saw?
- When I open it myself, does it match what it said?
If all three are yes, the job is done.
If it only says “done” with no checks at all, it isn’t done. Reply with:
Show me what you actually checked: what you did and what you saw. Don't just tell me it's done.What to say when it’s wrong
The result is wrong, for example the number doesn't change when I click.
Say only what you saw, like: “I clicked three times and the number stayed at 0.” Skip guessing the cause. A wrong guess sends it the wrong way.
The reply is long and full of words I don't know.
Type /pstack:bro. It retells the last reply in plain words, much shorter.
It asked me a question I don't understand.
Reply: “I don’t code. Please ask me in plain words, or pick the safest option for me and tell me why.”
It's doing things I didn't ask for, and I want it to stop.
Press Esc and it stops. Then tell it what you want, like “only the water tracker, don’t add anything else for now.”
On Windows, the cd line says it can't find the folder.
On some Windows computers the desktop lives inside OneDrive. Try cd ~/OneDrive/Desktop/water instead.
I use the Claude desktop app, and there's nowhere to type cd.
When you start a new session, it asks you to pick a folder. Pick water on your desktop. The rest is the same.
You’ve got it
Whatever you do from now on, it looks the same: /pstack:poteto-mode plus the three parts. Two more examples:
/pstack:poteto-mode My bookmarks plug-in sometimes saves the same item twice when I click save.
What done looks like: click save ten times in a row, and the list still has only one.
When you're done, show me: how you made the problem happen again, and what happened when you tried again after the fix./pstack:how How does the stuff in this folder work? Explain in plain words; I don't code.The second example uses /pstack:how: it only explains and doesn’t touch your things. Use it when you want to understand something before deciding whether to change it.