mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
71ed0d1076
* chore(pstack): bump plugin version to 0.15.0 Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): sync playbook count and table to twenty-three The tree ships 23 playbooks, and the README table omitted opening-a-pr. Add the row and change the two README counts and the guide's front-door count from twenty-two to twenty-three. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): fix principle count in guide index and 08 heading The guide index and the 08 heading still said 21 while the tree and the 08 body list 23 principles. Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
31 lines
2.0 KiB
Markdown
31 lines
2.0 KiB
Markdown
# The pstack guide
|
|
|
|
pstack works best when you stop micromanaging the agent. You describe what you want and how you'll know it's done. `/poteto-mode` picks the playbook, runs the other skills as the steps need them, and shows you the evidence. This guide teaches that habit with realistic prompts.
|
|
|
|
Here's what you'll learn:
|
|
|
|
1. [Set up pstack](./01-setup.md). Install the plugin and pick your models.
|
|
2. [Route work through `/poteto-mode`](./02-poteto-mode.md). Give it a goal and watch it pick a playbook.
|
|
3. [Understand the code](./03-understand.md). `/how`, `/why`, `/teach`, and `/recall` before you edit anything.
|
|
4. [Design the change](./04-design.md). `/architect`, `/arena`, `/swarm`, and `/interrogate` before code locks in a shape.
|
|
5. [Build and clean the change](./05-build-and-clean.md). The build playbooks, `/tdd`, `/unslop`, and `/no-comments`.
|
|
6. [Verify and ship](./06-verify-and-ship.md). Prove behavior on the real app, then open a focused PR and drive it to merged.
|
|
7. [Run work while you sleep](./07-overnight.md). An overnight contract, a decision log you can audit, and the playbooks that scale past one agent.
|
|
8. [Steer with principle names](./08-principles.md). The 23 names that redirect an agent mid-task.
|
|
9. [Make it yours](./09-make-it-yours.md). Your own mode, plus how to test a skill change.
|
|
10. [Recipes and pitfalls](./10-recipes-and-pitfalls.md). Prompts to copy and mistakes to skip.
|
|
|
|
Read the pages in order the first time. After that, each page stands alone.
|
|
|
|
## If you only remember one thing
|
|
|
|
Give the agent a goal and a way to check it, in your own words:
|
|
|
|
```text
|
|
/poteto-mode the export writes duplicate rows when a retry lands mid-run. repro first, then fix and verify.
|
|
```
|
|
|
|
You don't need to name a playbook or list skills. "repro first" and a checkable outcome are all the routing signal `/poteto-mode` needs. It matches the Bug fix playbook, copies the steps into a todo list, and calls the right skills as each step fires.
|
|
|
|
Next: [Set up pstack](./01-setup.md).
|