poteto-mode

Poteto mode

Bundled skills live at ../<name>/SKILL.md from this file, so put this file's absolute path in every poteto-agent prompt.

On Codex, read this file whole before acting, in a shell call of its own with max_output_tokens: 10000. A smaller output budget cuts lines out of its middle. If a read of it shows tokens truncated, read it again that way.

Non-negotiables

The Principles section below grounds every trigger. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose leaf SKILL.md you read this session.

Remaining triggers:

• Nontrivial change, architecture decision, or "are we sure?" → the how skill.
• About to ask the user a question on a "which approach", "how should I", or "what should this do" fork → classify it before you ask. If the answer is a fact you could observe by running something (behavior, timing, layout, output, perf, even whether an eval separates), it is not the human's to answer. Sketch it via the Prototype playbook (playbooks/prototype.md) and let the result decide. If the task is a read-only Investigation whose deliverable is a cited answer, stay in it and answer from the evidence rather than building a sketch. Reserve the question for a genuine product or preference call no experiment can settle. Under a full-autonomy grant, decide a call the grant covers, act on it, and report it, with no reply word and no offer. Under the grant, for a call only the operator can make, apply a default, report it with a full explanation, and say in plain words what the operator could tell you to do instead. The operator answers in their own words. Never give a shorthand token to type back. Gates the operator named and the Always-pause list in Autonomy still need the operator.
• Any code → name the data shape first, and choose its organizing structure per principle-model-the-domain.
• Code crossing a function boundary → the architect skill, parallel design exploration before implementing.
• Parallel fan-out → the swarm skill for coverage matrices, races, gauntlets, and exploration partitions. Use arena for design or code bakeoffs with base selection and grafting.
• Contested design → the interrogate skill (multi-model adversarial) before shipping.
• A Bug fix, Feature, or Refactoring diff → the interrogate skill with the interrogate reviewers panel before Opening a PR. Skip it only for a mechanical change, such as a rename or a dependency bump, and say so in the reply. Only findings under interrogate's Act on block, warning correctness findings included. A nit, or an edge case that cannot occur in practice, never blocks: batch accepted nits into one final fix run or drop them, and give each dismissal its reason. Round 1 reviews the whole change, and each later round reviews only the fix diff. After every fix round, a feature, refactoring delegate runs the real artifact and reports pass, fail, or could not run with its evidence. fail blocks like an Act on finding. could not run is not a pass and starts no fix, so report it. After three fix rounds, stop and report the open findings, what kind of failure they suggest, and a recommendation.
• Nontrivial multi-step → write the throughput checkpoint (Feature step 3).
• Any prose surface, your reply to the user included → the unslop skill. Write the reply per Writing the reply. Agent-facing prose also follows the harness's skill-authoring skill (skill-creator where installed, else the Agent Skills format).
• Docs, RFCs, readmes, PR descriptions, or commit messages → the technical-writing skill (/technical-writing).
• Before commit → the deslop skill (/deslop).
• Before review → the no-comments skill (/no-comments).
• Shipping UI / IDE / CLI → the matching control skill. That is the project's verify skill when it has one (/create-verification-skill makes one). Otherwise web UIs run through T3's preview_* tools, simulators through T3's device_* tools, and CLIs and TUIs through their own commands. The evidence is the artifact, such as a preview_snapshot saved with save: true, a recording, or the real output. For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception.
• Running a benchmark, measuring perf yourself, or reporting a speedup or regression you measured → the benchmark-checklist skill before you report or act on the number.
• Any PR-status request ("babysit this", "get it green", "address the bugbot comments", and most often "check on PR X" or "anything outstanding on X") → the Babysit playbook (playbooks/babysit.md). Never triggered by merely opening a PR. Declare its mode before polling. The playbook's step 1 owns the request-to-mode mapping. Reaching for drive inside a phase agent stops that agent finishing its turn.
• Asked to land or ship a green stack → the Shipping playbook (playbooks/shipping.md). Green is not safe. Nothing gets armed before an independent per-PR verdict, and only the contiguous verified run from the root lands.
• Deploying to a managed platform (Cloudflare, Vercel, Fly, Netlify, and the like) → load that platform's skill, project-local or installed, before running its CLI, the same way Shipping step 1 resolves the forge before the first PR operation.
• Bugbot or the agentic security review commented → skeptical posture. They catch real bugs and also file non-issues and nitpicks, so assess each on its merits and dismiss noise with a concrete reason instead of churning code. Triage fix / dismiss / ask per references/bugbot-triage.md.
• 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") → a decision trail via the show-me-your-work skill. Commit it when stakes need an auditable record. Keep it local otherwise.