agent sidequestsIdeas worth trying
Make something

Give your recipe a next button for messy hands

Stop scrolling through a recipe with flour on your fingers. Turn one recipe into a private step-by-step player with clear ingredient amounts, a place to resume and optional voice controls.

You get: A private recipe step player, editable source, a checked ingredient-to-step map and a record of device testsOriginal prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Build a small kitchen step player for this recipe that I own or may adapt: [recipe and source]. I will use [phone or tablet, browser] at [preferred text size]. My hands may be wet or covered in flour, so make the next step easy to reach. Create new private files and preserve the original recipe.

First read the complete recipe you can access and identify its ingredients, amounts, units, ordered steps and relevant notes. Preserve its stated temperatures, durations, warnings and completion cues. Ask about missing or contradictory instructions that would change the result. Do not fill gaps from another recipe, invent cooking guidance or silently scale quantities.

Make an ingredient-to-step map with source references. Keep the recipe's total quantities separate from amounts explicitly assigned to a step. If an ingredient is used twice but the recipe does not say how to divide it, flag that for my confirmation; do not display the full quantity as a new amount to add each time. Keep the original ingredient list and full recipe one tap away from the step view. Let me approve unresolved interpretations before treating them as instructions.

Build a compact browser page with one step at a time, large next and back buttons, keyboard controls, adjustable readable text and a visible step number. Show only the ingredients relevant to that step, with assigned quantities when the source states them. Include a way to review earlier steps and deliberately reset. Save the current position locally only when supported, and make a resumed session obvious. Advancing the display records where I am in the instructions; it does not verify that I performed the step or that food is cooked. A timer, if I request one, must preserve the recipe's completion cues and cannot replace them.

Make manual controls work first. If I request voice commands, check the intended browser's current support and how its speech recognition processes audio. Explain whether audio leaves the device. Start listening only after my explicit permission and visible start action; provide a clear listening indicator and stop control. Do not enable cloud speech processing or introduce an external audio service without my approval. If processing cannot be established or voice is unreliable, leave it off and keep the manual player useful. Limit commands to next, back and repeating the current instruction; an unclear command must not skip ahead. Do not enable the camera.

Check first and last steps, next/back navigation, ingredient totals versus step amounts, reset and resume, readable layout on my intended screen, and any enabled voice behavior. If keeping the screen awake is supported, test it and explain any limitation. Test a disconnected reload before claiming offline use; otherwise say that offline availability is unverified. Do not claim a device test you could not perform.

Return the player, editable source, ingredient-to-step map, opening instructions and a short test record separating observed results from checks I still need to do. Do not publish the recipe, upload it to a new service, install software or create an account without my approval.
What the result could look like

Illustrative: one amount, even when it appears in two steps

A recipe lists 200 g of flour and refers to it during two stages. The player preserves 200 g as the total and flags an unstated split instead of telling you to add 200 g twice. You can return to the previous instruction with a large button or an explicitly enabled voice command. This is an imagined interface, not a tested build.

Illustrative example. This is not an observed result or a verified recommendation.
The real-world spark

Inspired by a reported use

Silveira describes building a cookbook with Claude Code and using its voice- or gesture-controlled cooking mode herself.

Vitória Silveira’s personal AI-assisted cookbook project

Creator self-report and portfolio project; no displayed publication date. We read the writeup and opened the app shell, but did not test the controls or verify weekly use. Our recipe-to-step quantity checks and device-first workflow are original untested extensions. The prompt above is our original extension, not the author's exact prompt or a tested result.

Make it more you

Start with one frequently cooked recipe and manual controls on the actual kitchen device. Add optional voice navigation only after the quantities and step order are useful in that first version.

Get more from this idea

Keep the ideas coming

All sidequests
Make something

See your trip before you take it

Plan a real route, then give it a visual life. Get a usable itinerary paired with clearly labeled illustrations of the trip you are imagining.

You get: A source-linked itinerary and illustrated trip previewGet the promptCommunity-inspired idea