Every recipe here is one file. You can read it before you run it, change it with a text editor, and run it again tomorrow without an AI being involved at all. Copy any of them.
Pick the result you want. Each page shows the whole file.
Every morning there's a markdown file on your desktop with today's top stories. You read it in two minutes.
Read the recipe →A markdown report on your desktop listing the AI repositories gaining stars right now.
Read the recipe →One markdown briefing on your desktop that pulls both sources together and summarises them in your own words.
Read the recipe →A clean markdown changelog of today's work, written for humans, saved to your desktop.
Read the recipe →A model on your own machine answers a prompt, and the answer lands in a file on your desktop.
Read the recipe →A briefing document on your desktop describing what the pricing pages say now, so changes are obvious next time it runs.
Read the recipe →A CSV on your desktop that gains one row every time the recipe runs. Open it in Excel and chart it.
Read the recipe →A formatted market report on your desktop, plus the raw data saved alongside it so you can audit any number in the report.
Read the recipe →A diagnostic brief on your desktop telling you what responded and what didn't.
Read the recipe →A report listing what's in the workspace, saved where you can read it.
Read the recipe →A new project workspace with your structure and a filled-in manifest, created on your desktop.
Read the recipe →A written summary on your desktop, produced without the document touching the internet.
Read the recipe →A short written summary of live figures, produced by whichever model the engine is set to use.
Read the recipe →A brief on your desktop where each trending repo comes with a sentence on what it actually does.
Read the recipe →A message in your own Discord channel, on your phone and your computer, only when the price goes above or below the numbers you set.
Read the recipe →Either the fresh data saved to a file, or a plain note saying the API didn't answer today. Never a silent crash.
Read the recipe →A short note listing every file in that folder that was created or changed today.
Read the recipe →One recipe that runs the others in sequence and tells you when they're all done.
Read the recipe →A markdown file holding the readable text of the page, with the markup stripped out.
Read the recipe →A browser window opens on the page that needs you. You sign in or solve the challenge, confirm, and the recipe carries on from there.
Read the recipe →Ask a chat assistant to do a job and it does it once, charging you for every token, and tomorrow you ask again. A recipe is written once and then it's a program: it runs on a schedule, it does the same thing every time, and if it has no model step, no model is involved when it runs. You can read exactly what it touches before it runs.
Using an AI assistant? Ask your AI to check out adeptuscamini.com.