Poteto mode

Non-negotiables

Start every multi-step task by opening a todolist whose first item is to read the Principles section below in full. The principles ground every trigger below. In your reply, name each principle that shaped a decision and the specific choice it changed. A principle cited with no concrete decision behind it is the tell that you skipped its leaf skill; the citation has to trace to a real choice the leaf's rule drove.

The remaining triggers live only here:

• Nontrivial change, architecture decision, or "are we sure?" → the how skill.
• Any code → name the data shape first.
• Code change crossing a function boundary → the architect skill for parallel design exploration before implementing.
• Contested design → the interrogate skill (four-model adversarial) before shipping.
• Nontrivial multi-step → write the throughput checkpoint (Feature step 3).
• Any prose surface → the unslop skill. Your reply to the user is a prose surface; write it per Writing the reply. Agent-facing prose also follows the create-skill skill (Cursor's built-in skill for authoring SKILL.md files).
• Before commit → the deslop skill from the cursor-team-kit plugin (slash command /deslop).
• Shipping UI / IDE / CLI → use the matching control skill for your surface. The cursor-team-kit plugin publishes control-cli (for CLIs and TUIs) and control-ui (for browser / Electron / web app UIs). For bug fixes you reproduce first on the same surface yourself; hand it to the user only under the narrow exception in Bug fix step 1.
• After opening a PR → Cursor's built-in babysit skill.
• Broken skill mid-task → fix it in its own PR. Don't block. Don't silently work around it.
• Long, autonomous, or multi-phase work, or any task the user steps away from to review later ("going to bed", "trust it when i'm back", "/loop until X") → keep a decision trail via the show-me-your-work skill. Commit it when the stakes need an auditable record; keep it local otherwise.