mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
5bf2b1544d
* feat(pstack): setup-pstack budget ask (max/xhigh/high/medium) Step 3 of /setup-pstack asks for a budget first (unlimited, large, medium, small), rewrites the effort token of every real slug in the working table to the budget's target, clamps to the detected set within the same family, and then shows the roles for confirmation. Step 2 reads the recorded budget line and step 5 writes it. No version bump. Co-authored-by: lauren <poteto@users.noreply.github.com> * docs(pstack): mention the setup-pstack budget in README and setup guide Co-authored-by: lauren <poteto@users.noreply.github.com> * refactor(pstack): tighten setup-pstack step 3 to three short parts Drop the four-by-four example table, the repeated family and fast explanations, and the re-run essay. Keep the four budget labels, one remap rule with a one-line example, the confirm paragraph, and the budget line in the written rule. Co-authored-by: lauren <poteto@users.noreply.github.com> * fix(pstack): setup-pstack step 3 rebuilds before the budget, keeps aliases, records the chosen budget Bugbot on #366. The working table is built from the defaults first, on every run, so unlimited on a re-run restores the default efforts. The carry-over set names alias roles. Step 5 says the budget line holds the chosen label and target effort. Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
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:
- Set up pstack. Install the plugin and pick your models.
- Route work through
/poteto-mode. Give it a goal and watch it pick a playbook. - Understand the code.
/how,/why,/teach, and/recallbefore you edit anything. - Design the change.
/architect,/arena,/swarm, and/interrogatebefore code locks in a shape. - Build and clean the change. The build playbooks,
/tdd,/unslop, and/no-comments. - Verify and ship. Prove behavior on the real app, then open a focused PR and drive it to merged.
- Run work while you sleep. An overnight contract, a decision log you can audit, and the playbooks that scale past one agent.
- Steer with principle names. The 23 names that redirect an agent mid-task.
- Make it yours. Your own mode, plus how to test a skill change.
- Recipes and pitfalls. 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:
/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.