The author runs Claude Code from a fixed folder with saved scripts to process new travel booking emails into their calendar.
The author runs Claude Code from a fixed folder with saved scripts to process new travel booking emails into their calendar.
The author keeps a numbered Johnny.Decimal folder tree, with one folder holding saved scripts and documentation for adding travel bookings to their calendar. They jump to it with a small command, `jd tripsy`, launch `claude` there, and tell it a new email has arrived. Earlier conversations can be picked up with `/resume`.
The source says the process works with that single prompt and calls it done, but it gives no numbers, error rates, or details of what the scripts do.
The trick is a static, well-named folder per task, where Claude Code finds its saved scripts and docs each time, rather than any special tooling.
Open this folder: [path to your travel folder]. Search my email for new travel booking confirmations from [date range] (flights, hotels, rentals) and add each one to my calendar with the dates, times, confirmation number and address. Save the steps as a reusable script so I can rerun it later, and show me the list of events you plan to add before creating any of them.
A Claude Code-built agent checked ESPN every 30 minutes and sent each 2026 World Cup final score, written up in a persona, to a 3-person Signal group, with a code check on scores.
The poster exports Garmin data into a Claude project and meal planner, where Claude spotted a link between eating more on one day and reduced medication efficacy.
A Claude Cowork skill tracks diet and medical metrics in a spreadsheet, and meals told to Claude on mobile are logged in the daily record.