Skip to content
Full guide · step 0 of 85-minute read

What pstack is

In one lineKnow what pstack does for you, what it costs, and the four things to have ready before you start.

You need: Nothing yet, just read

Don't code?

This full guide is for people who write code, and it uses words like Git and PR. If you’ve never written code, start with the three beginner lessons. You’ll be using it in 20 minutes.

What pstack is

pstack is a pack of skills. It goes into the AI coding tool you already use, like Claude Code, Cursor, or Codex.

Once it’s in, the AI writes code by a senior engineer’s rules: understand first, then act, then check its own work.

The model stays the same. What changes is the order it works in and the bar it has to clear.

  1. YouSay the goal, e.g. “fix this bug and show me evidence”
  2. pstackThe work rules you install: 23 playbooks, 34 skills, 24 principles
  3. Your AI coding toolClaude Code, Cursor, Codex…
  4. The modelSame as before; pstack doesn't swap it
Diagrampstack lives inside your tool, between you and the model. The model stays the same; the order and standard of the work change.

Which bad habits it fixes

  • Changing code it hasn’t understood. It edits a spot that looks right but isn’t.
  • Treating only the symptom. It hides duplicate data where it’s shown. The bug that creates them is still there.
  • Saying “done” without trying it. It says “should be fine now.” You run it, and it’s still broken.
  • Changes that keep growing. It adds code nobody needs, and the next bug hides in it.

You only need one command

Day to day, just type /pstack:poteto-mode. You say the goal, and it plans the rest. Behind it there’s more, but you don’t need to learn it yet:

  • 23 playbooks: fix a bug, add a feature, refactor… one approach per kind of task.
  • 34 skills: for example, /pstack:how explains code and /pstack:bro puts things in plain words. See the skills list.
  • 24 principles: for example, “subtract before you add” and “prove it works.”
  • 2 helper AIs: one follows the same rules when it’s sent off to work; one only reviews comments.

What you get from it

  • Smaller changes, tried every time. It deletes what it can, and ends by running real commands and clicking the real UI.
  • You can run several AIs at once. Each follows the same rules and works in its own folder.
  • The same mistake doesn’t happen twice. Use /pstack:correct to block it at the root.

The cost: slower and pricier

It sends out more helper AIs and has several models check each other. So it’s slower and uses more tokens. Skip it for small changes. To save, see Controlling cost.

Have four things ready

  • An AI coding tool: any one of Claude Code, Cursor, or Codex (OpenCode and Pi work too). It must be able to change your code and run commands. A chat-only AI in the browser won’t work.
  • A model you can use: a paid plan for the tool, or an API key.
  • A real project in Git: most playbooks create a worktree and open a PR. Not using Git yet? Run git init and make one commit first.
  • Node.js 22.20 or later: only if you install with npx skills.

Tip

This site uses the backnotprop/pstack mirror. It syncs with the official version daily, and also works in Claude Code and Codex. You use both the same way.

Before moving on, check

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.