Copy this one first
It says “done,” but all that happened is the build passed. You reply:
apply prove it works. Run the real import flow and show me the records it wrote.prove it works means “show that it really works.” It names one of pstack’s principles (written-down rules for how to work). /pstack:poteto-mode reads them all before it starts, so the name tells it exactly which rule you mean.
The second half says what you want this time. A name points more precisely than a paragraph. No need to memorize them. Come back here when it drifts.
1apply prove it works.2Run the real import flow3and show me the records it wrote.
- 1Principle name, typed as is
- 2What to do this time
- 3The real result you want
Three more ways to pull it back
It did something you didn’t ask for. Restate the goal:
i said the goal is to repro. i did not ask for a fix yet.The reply is hard to follow, or sounds too much like AI:
/pstack:bro/pstack:unslop that, no emdashes/pstack:bro says the last reply again in plain words. /pstack:unslop that takes the AI feel out of that text, and no emdashes means “no em dashes.”
You’ve moved on to something else. Say new task first:
/pstack:poteto-mode new task. Find out why the cache is still there after logging out. Don't change any code yet.Otherwise it treats your new question as the next step of the last task.
What it’s doing, and what you reply
Meaning first, then the name to type as-is:
- Says “done” because the build passed → show it really works:
apply prove it works.Run the real command and show me the real output. - Adds an if check after the point of failure and calls it fixed → find the real cause:
fix root causes.Find where it first goes wrong. - Stacks a new adapter on three old ones → remove before adding:
subtract before you add.Delete the stale ones first. - Fixed the same check several times, still failing → question the assumption:
attack the premise.Test what those fixes assume. - Making dozens of identical changes by hand → build a tool:
build the lever.Write a script I can rerun. - Leaves a compatibility layer for the old interface during a migration → delete once moved:
migrate callers then delete legacy apis. - Tests check which internal function was called → test behavior:
test behavior not implementation.Check what the user can see. - Stops to ask about a small thing that can be undone → don’t wait on me:
never block on the human.Do it, then show me. - Starts writing the first design straight away → try several:
exhaust the design space.Build two or three prototypes and compare.
All 24 are in Principles.
It should say which decision changed
Just saying the name doesn’t count. When it uses a principle, it should say what it changed because of it.
Following subtract before you add, I first deleted two adapters nobody calls anymore. The new one no longer has to stay compatible with them, and the interface is half the size.Followed the prove it works principle. Feature works.The second one has a name, but no decision and no evidence. Push back:
You said you used prove it works. Which command, and which output, proved it? Paste them.The same problem came back
A correction in chat only covers this one time. The second time, use /pstack:correct to change the repo itself:
/pstack:correct the AI keeps bypassing the repository layer and calling the database client directly.It adds a check, a type, or a test, so later AIs can’t make the mistake. For more, see Once you’re comfortable.
Stuck?
I said the principle name, and nothing seemed to happen.
If you sent /pstack:poteto-mode with Enter, it stops working after a few turns. Type it again, or in Cursor use Option+Enter (Alt+Enter on Windows) to keep it on.
I can't remember the principle names.
No need. Say what you want in your own words, like “don’t add a check later on, find the real cause.” The names are just shorter and more precise.
I pulled it back, and a while later it drifted again.
First check whether you switched tasks without saying new task. If the same problem keeps coming back, use /pstack:correct.