Skip to content

Cursor plugin specification and official plugins

TypeScript

pstack: frame reply impact for the consumer and the maintainer (#103)

laurenc532aa167cdb
diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.md
index ea0153fb..c9975c7b 100644
--- a/pstack/skills/poteto-mode/SKILL.md
+++ b/pstack/skills/poteto-mode/SKILL.md
@@ -88,6 +88,7 @@ Write the reply clean as you draft it. Don't write slop and strip it afterward.
- **The long-dash character is banned outright.** Two cases we keep catching. A file-list bullet joining a filename to its description with a dash: write it as a sentence ("`main.js` owns persistence and the IPC handlers"), not the dash form. A bold section header joined to its text by a dash: write the header as its own sentence ("**Verification.** End to end via CDP"), not the one-line dash form.
- **A colon as a mid-sentence connector is also out** (unslop rule 14). A colon before a list is fine.
- **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 say what changes for them before any implementation detail. Then say 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 actually produced or read this session.
Every playbook ends with a reply written this way, with the PR link as `https://github.com/<owner>/<repo>/pull/<number>`. The per-playbook lines below name only the content unique to that playbook.
diff --git a/pstack/skills/principle-experience-first/SKILL.md b/pstack/skills/principle-experience-first/SKILL.md
index 641dbd9b..be15f055 100644
--- a/pstack/skills/principle-experience-first/SKILL.md
+++ b/pstack/skills/principle-experience-first/SKILL.md
@@ -14,4 +14,6 @@ The product is the experience. Every technical decision either helps or hurts it
- Sweat the details (transitions, alignment, spacing, feedback, error states)
- Tighten the core loop (every feature should serve the central workflow or get out of the way)
+The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their seat.
+
Foundations should serve the experience, not the other way around. Foundational thinking governs the *sequence* of work; this principle governs the *target*.