Before the AI says “done,” make it try the thing itself
pstack is a free, open-source set of work rules you install into your AI. With it, the AI first makes sure it knows what you want, then changes only what needs changing. You don't need to know how to code.
The beginner track is three lessons, 20 minutes.
Has this happened to you?
- The AI says “done!” You open it, and the button does nothing.
- You say “still broken.” It says “sorry, fixed now.” Same result, again and again.
- You wanted one small change, and it changed a pile of things you never asked about.
What changes once it's installed
| When | AI as usual | With pstack |
|---|---|---|
| Before it starts | Starts without checking what you want | Repeats your goal in its own words first, so you can correct it right away |
| While it changes things | Changes things somewhere that looks about right | Figures out the problem first, then changes as little as it can |
| When it says it's done | “Should be fine now” | Lists what it actually checked and what it saw, and says plainly what it couldn't check |
Beginners need just three lessons
Read them in order, 20 minutes in all. After these three you can use it. Everything else on the site is for looking up later.
- What it does for you3 minutes · What pstack is, what you need, what it costs
- Install it5 minutes · Type two lines in Claude Code and pick one option
- Use it for the first time10 minutes · Make a small web page with one three-part message
Is it for you?
Yes, if
- You've made small pages, plug-ins or tools with AI and been burned by “done” that wasn't
- You already have Claude Code (or Cursor or Codex) and can chat with the AI in it
- You'd rather get it right than get it fast
Not yet, if
- You haven't used a tool like Claude Code yet: install it with the official guide first, and come back once you can chat
- It's a tiny change like a typo or a color: just ask the AI directly
- You only want fastest and cheapest: pstack checks more, so it's slower and uses more of your plan
If you write code
pstack is the pack of skills poteto (on the React core team, working at Cursor) uses for their own code every day: 34 skills, 23 playbooks and 24 engineering principles. Below are the four steps it takes for every task, and the 9-step full guide.
You say one sentence
The goal, plus how you'll know it's done. For example: “reproduce it first, then fix, then verify.”
/pstack:poteto-mode picks a playbook
It chooses one of 23 playbooks and copies its steps into the todo list as they are.
Skills run step by step
/pstack:how to read code, /pstack:architect to settle a design, /pstack:interrogate to pick holes; subagents when there's a lot to do.
It checks before handing back
Real command output, screenshots, before-and-after. If something can't be verified, it says so.
- What pstack is5-minute read · What it's for, what it costs, what you need
- Install pstack5 minutes · One way each for Claude Code, Cursor and Codex
- Pick models and budget (optional)10 minutes · Works without it; read this to save money or switch models
- Your first task15 minutes · Say it in one message, then check its restatement and results
- Understand before you change15 minutes · Have the AI explain how the code works before deciding to change it
- Design, build, clean up20 minutes · Settle the plan for big changes, have other models pick holes, cut what isn't needed
- Verify and ship20 minutes · Make sure it really works, then hand it in for merging
- Let it run on its own15 minutes · Brief it before bed, read its log in the morning
- Once you're comfortableAs needed · Pull it back in one line; stop the same mistake from happening twice
Questions and discussion
This airali copy is based on the original open-source guide. Visit the source repository for its history and updates.
Before asking, check the FAQ: many answers are already there.
Before sending screenshots, blur out API keys, company code and account details.