poteto-mode

Poteto mode

Platform Adaptation

These skills use Claude Code tool names (the Skill tool, the Agent tool, AskUserQuestion) and Claude model slugs (claude-*). On Claude Code they work as written. On Codex, read references/codex-tools.md for the Codex equivalent of a Claude tool, model, or built-in skill (run, verify, plugin-dev:skill-development). Other runtimes can discover the same Agent Skills tree, but they must use their own tool, model, and configuration equivalents. codex-tools.md is not a cross-runtime map.

Non-negotiables

Start every multi-step task with a todolist whose first item is to read the Principles section below in full. The principles ground every trigger here. In your reply, name the principles that shaped decisions and the choice each changed. A sentence per principle carries both; the justification stays in the work, not the reply. A citation with no decision behind it means you skipped its leaf skill; it must trace to a real choice the leaf's rule drove.

Remaining triggers:

• Nontrivial change, architecture decision, or "are we sure?" → the how skill.
• About to AskUserQuestion 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. The ask is the slow path. A throwaway probe usually answers faster, and it hands the human a result to react to instead of a decision to make.
• 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.
• Nontrivial multi-step → write the throughput checkpoint (Feature step 3).
• Any prose surface → the unslop skill. Your reply is a prose surface; write it per Writing the reply. Agent-facing prose also follows the plugin-dev:skill-development skill (Claude Code's authoring guidance for SKILL.md files).
• Docs, RFCs, readmes, PR descriptions, commit messages → the technical-writing skill (/technical-writing) for structure and sentence discipline, on top of unslop.
• Before commit → the deslop skill (/deslop).
• Before review → the no-comments skill (/no-comments).
• Shipping UI / IDE / CLI → the driver skill (run for CLIs/TUIs, verify for UIs). Both ship as Claude Code built-ins. For bug fixes, reproduce first on the same surface yourself; hand to the user only under the narrow Bug fix step 1 exception.
• Any PR-status request → the Babysit playbook (playbooks/babysit.md), not the bundled babysit skill, whose description matches the same words. That includes "babysit this", "get it green", "address the review-bot comments", and the commonest phrasing, "check on PR X" / "anything outstanding on X". 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.
• An automated PR-review bot 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.