Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Recipes and Tips

This chapter collects prompts that you can copy and adapt. Replace the paths and finish conditions with your own. The prompts are deliberately informal, because that is how people type them in practice, and the skills interpret intent well enough. Most prompts come from the guide’s recipes page; each is followed by a short note on why it works and, where one applies, the principle it relies on.

Fixing bugs

/poteto-mode repro the duplicate write first. if there's a cheap test path, /tdd it. then fix and rerun.

Because reproduction happens first, the fix targets a failure that has been confirmed rather than one that is assumed. The condition “if there’s a cheap test path” is deliberate: a test pushed through fragile mocks proves less than running the real command, and the playbook may say exactly that. The relevant principle is Fix Root Causes, which means following every symptom back to the earliest point where the system went wrong.

/poteto-mode read this thread. restate the underlying issue in your own words, in plain english. don't change any code yet.

For a long or noisy report, a restatement exposes any misreading at the cost of one message. Keep your own theory of the cause to yourself until the agent has stated its own. If you want only the restatement, without a playbook, use in-your-own-words.

/poteto-mode repro this with /verify-<app>. if it repros on main, fix it and show me a video as proof.

In this prompt, /verify-<app> is a placeholder for the verification skill that create-verification-skill generated for your project. Thanks to the condition “if it repros on main”, the run can end early if the bug no longer exists, and the video allows you to confirm the fix before reading the diff.

Building features

/poteto-mode prototype a few options for the settings layout. put them behind a switcher and send me screenshots of each.

You choose among things that run, instead of among descriptions. The agent answers its own questions about layout and timing along the way. The principle is Exhaust the Design Space (build 2 or 3 competing prototypes before committing).

/poteto-mode turn this design into a plan. small verifiable PRs, each with its own proof.

Ask for a plan only once the design has settled. The plan itself is the deliverable, and it names the playbook that will execute it. The principle is Sequence Work into Verifiable Units.

ask /arena for a second opinion on this thread and our approach

arena treats your current design as one candidate among several. Its synthesis tells you whether the panel found something better or confirmed what you had, which costs little compared with a design that is expensive to reverse.

Investigating

use /how first to understand how this initialization works. then use /why to figure out why it broke recently.

Mechanics first, history second. Each skill’s report names the sources it searched, so you know what the answer is based on. The choosing chapter explains how the two skills differ.

/interrogate the whole branch, but skeptically. don't change anything yet. no nitpicks unless it's an actual bug or regression in behavior.

This is a read-only adversarial review through interrogate. The qualifiers carry weight: “don’t change anything yet” keeps the run read-only, and the rule about nitpicks filters out noise in advance. What remains are findings that a rerun has proven.

Refactoring and repository hygiene

/correct agents keep adding new config flags without registering them in the schema

Instead of fixing the same mistake again by hand, correct puts the fix into the repository as architecture, a type, a lint, or a test, so the next agent cannot repeat it. The principle is Encode Lessons in Structure.

/swarm check every package under packages/ against its check.sh. one worker per package. one report.

Independent slices are checked in parallel by swarm. Each worker owns one package, and the parent waits for every slice before returning a single PASS, ISSUES, or BLOCKED report instead of raw worker output.

Opening a PR and handling review

/poteto-mode open a PR for this change. put the real-artifact evidence in the description.

This routes to the Opening a PR playbook, which works from a git worktree off trunk and writes a short body whose last heading is ## Verification. Asking for real evidence keeps that section about the actual flow or output, not about a green build. The principle is Prove It Works.

/interrogate the review comments on this branch. keep only what a rerun proves, and list what you dropped and why.

Bots and humans both file real catches and noise in the same list. Accepting or rejecting all of them is wrong either way. interrogate keeps the findings a rerun proves and reports the dropped ones with reasons, so you can still override its judgment in either direction.

Verifying claims

/create-formal-verification-skill the retry queue. a message must never be delivered twice.

The result is a single property checked across every case inside a declared scope, a counterexample expressed in the terms of your code if the code violates the property already, and a project skill that later agents run whenever that code changes. See create-formal-verification-skill.

/benchmark-checklist vet this 40% speedup before it goes in the pr description

The number is vetted before anyone else sees it. benchmark-checklist returns one of four verdicts (faster, slower, no measurable difference, or inconclusive) with the run count, the range, and the factor that limits the number. The principle is Explain the Number.

Running unattended and resuming

im going to bed, keep going autonomously until every fixture passes. do not stop. keep a decision log i can audit in the morning.

This short form works once the task and the finish condition are already in the conversation. The full handoff contract is in the overnight chapter.

/poteto-mode pause here. i'm about to go offline.

The Pause safely playbook stops at a safe boundary, records a wip: commit, and writes a resume note. Use it whenever you expect an interruption.

pick up where the previous session left off. read its resume note and decision log, then tell me the resume point.

In a new chat, the Session pickup playbook reads the previous trail as authoritative input and does not redo finished work. It still verifies the inherited claims against the goal on the real artifact. The principles are Guard the Context Window (a long transcript is parsed in a subagent) and Prove It Works.

Catching up and reading replies

/ketchup

ketchup summarizes in plain language what has happened since your previous message, and then lists every decision that is waiting for you, each with a recommended option, its evidence, and its risk. Reporting does not modify anything. If you would rather watch the update, run /ketchup-video.

/bro

That is the whole prompt. bro restates the last message more simply and briefly, without jargon. Use it when a reply is thorough but you still cannot tell what it said.

/poteto-help how do i get poteto-mode to stay on every turn?

poteto-help responds to questions about pstack by giving an explanation, a ready-to-send prompt, and a link to the relevant source. No work starts until you actually send the prompt.

Improving the setup itself

These prompts come from the guide’s make-it-yours page.

/automate-me

automate-me mines your recent transcripts for repeated preferences, asks which patterns are really yours, and drafts a personal <your-name>-mode skill that it opens as a PR. Run it again later with “update my mode skill with everything since its last edit”.

/reflect that took way too long. capture what we learned so the next run doesn't repeat it.

reflect keeps only lessons that would change a future agent’s work and waits for your approval before editing any skill. Approve a proposal only if it would change a future decision; one unusual session is an anecdote.

/poteto-mode update the review skill so it flags missing migrations, and eval the change.

Asking for the evaluation in the same prompt keeps the edit honest, because a fix written from one bad session tends to overfit that session. The Eval playbook runs the variants blind so that the candidate agents do not know they are being evaluated.

Tips

  • Do not list skills in the prompt. “use /architect then /arena then /interrogate” overrides an order that the playbook already defines. State the goal and the constraints, and name a skill only to override a default.
  • Write finish conditions that can pass or fail. “Make it better” or “work on it for an hour” gives /loop nothing to check.
  • If a prompt feels thin before you send it, run sharpen on it, for example /sharpen write the onboarding doc for the new billing service. It does not perform the task; it returns your prompt rewritten to ask for what an expert would do.
  • When a run drifts, correct it with a single line that names a principle, such as “i said the goal is to repro. i did not ask for a fix yet.” or “apply prove it works. show me the real output, not the build log.” The names of the principles serve as the shared vocabulary for such corrections.
  • To clean up prose in one step, a line such as /unslop that, no emdashes is enough.