Cursor plugin specification and official plugins
TypeScript
pstack: every claim carries its evidence or its label (#341)
laurenf8abeddd1862
diff --git a/pstack/.cursor-plugin/plugin.json b/pstack/.cursor-plugin/plugin.jsonindex e6c54aee..4b9eca38 100644--- a/pstack/.cursor-plugin/plugin.json+++ b/pstack/.cursor-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "pstack","displayName": "pstack",- "version": "0.15.0",+ "version": "0.15.1","description": "if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence.","author": {"name": "Lauren Tan"diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.mdindex 22d8b050..2de0216e 100644--- a/pstack/skills/poteto-mode/SKILL.md+++ b/pstack/skills/poteto-mode/SKILL.md@@ -104,6 +104,7 @@ Write the reply clean as you draft it. A cleanup pass after drafting does not re- **Terse is not an excuse to drop content.** Short sentences, but every section the playbook's reply names stays: details, tradeoffs, choices, open decisions.- **Frame impact for the consumer and the maintainer.** Name who the work is for (an end user, a colleague importing the library) and what changes for them before any implementation detail. Then what the next engineer who owns this code inherits. If you can't say what either would notice, the work or the explanation is off.- **Never fabricate a link, citation, or transcript reference.** Link only artifacts you produced or read this session.+- **Every claim carries its evidence or its label in the same sentence.** Measured, inferred, or guess. A prediction or an unseen cause is a guess. Never hand the human a check you could run.Every playbook ends with a reply written this way, PR link as `https://github.com/<owner>/<repo>/pull/<number>`. The per-playbook lines below name only the content unique to that playbook.