My Garmin says I'm "exhausted", but I have a 10 AM interview. Sleep trackers are broken. Let's play a game.

Hey guys. It’s 5 AM here, I’m in the middle of a 6-day AI hackathon, and I’m about to get exactly 4 hours of sleep.

When I wake up, my Garmin is going to see my 4 hours of sleep (with maybe 12 minutes of deep sleep) and give me a generic notification like: "Your recovery is critical. Take it easy today."

But Garmin doesn't know I have a high-stakes interview at 10:00 AM that I can't cancel. It also doesn't understand my chronotype — I’m a night owl, and 1 AM to 4 AM is my only uninterrupted "flow state". A generic "go to bed earlier" notification is completely useless to me. Data without future context is just a guilt trip.

My team and I are trying to fix this at our hackathon. We are building an AI agent that pulls your tomorrow's Google Calendar events, looks at your latest sleep data, and gives you a pragmatic survival directive (e.g., "You only slept 4 hours. Don't nap before your 10 AM interview due to sleep inertia. Do a 25-minute Nappuccino at 1:30 PM instead").

Before we code the backend, I want to manually test our core LLM logic.

Let’s play a game. Drop a comment with:

1. Your recent sleep/recovery state (e.g., "Sleep score 55, woke up twice").
2. Your rough schedule for tomorrow (e.g., "3 Zoom calls, gym session, hard deadline at 5 PM").
3. (Optional) Any weird habits/chronotypes (e.g., "I'm a night owl", "I crash at 3 PM").

I will manually run your scenario through our AI's system prompt and reply with the exact directive our app would give you.

Roast our logic! Tell me if the advice is actually helpful for surviving a crazy schedule, or if it's just generic AI fluff.