Date nights fall into predictable patterns or suffer decision fatigue. We’ve been to the same three restaurants. We spent 40 minutes deciding what to do and ran out of energy before the date started. The planner removes the decision and makes the date happen.
The Problem
The gap between “we should do something nice tonight” and “we’re actually doing something nice tonight” is decision fatigue. No system combines weekly preferences, local event availability, and a history of past dates to avoid repetition. Couples either default to the familiar or spend the date’s best energy deciding what to do.
What It Is
An interactive Claude prompt that collects this week’s preferences (budget, energy level, whether a sitter is available, whether we want to stay local) and generates a full 4-6 hour itinerary from multiple local sources. A date history prevents repeats. A Monday morning surprise notification drops a fresh idea without being asked.
Features
- Claude Q&A loop for weekly preference collection
- Multi-source event and activity aggregation
- Date history lineage to prevent repeat suggestions
- Monday surprise notification with an unprompted idea
- Full 4-6 hour itinerary with logistics: book ahead, get sitter, timing
Stack
| Tool | Role |
|---|---|
| Claude API | Itinerary generation and Q&A |
| Puppeteer / Playwright | Local event scraping |
| Obsidian | Date history storage |
| Markdown | Itinerary output format |