mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
02c03a9ded
* pstack: add public usage tutorial Co-authored-by: lauren <poteto@users.noreply.github.com> * pstack: document verification skill workflows Co-authored-by: lauren <poteto@users.noreply.github.com> * pstack: mention verification setup offer Co-authored-by: lauren <poteto@users.noreply.github.com> * pstack: clarify optional verification setup Co-authored-by: lauren <poteto@users.noreply.github.com> * pstack: rewrite tutorial prompts to match real usage The example prompts read like specs. Real prompts are short, informal, and goal-first, so every example now uses that register. The prose reshapes around them: friendly second-person tutorial voice, goals before mechanics, pitfalls where readers actually trip, and the playbook reference table replaced with prompts in context. Every skill claim re-checked against the skill files at this commit. * pstack: make the README guide link an invitation Point new readers at what the guide walks them through instead of listing its topics. * pstack: drop the version bump This PR only adds documentation, so the plugin manifest stays at main's 0.11.7. * pstack: add illustrations to the guide One hero image per major guide page (routing, understanding, design, verification, overnight runs, recipes), 1200px JPEGs under docs/guide/images/. --------- 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, and/interrogatebefore code locks in a shape. - Build and clean the change. The build playbooks,
/tdd, and/unslop. - Verify and ship. Prove behavior on the real app, then open a focused PR.
- Run work while you sleep. An overnight contract and a decision log you can audit.
- Steer with principle names. The 21 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.