Weather Forecast — Vivek's Weekly Weather Outlook

# Weather Forecast — Vivek's Weekly Weather Outlook

Get a 7-day weather forecast tailored to Vivek's preferences. Asks where you'll be each day — because you might be travelling.

## Arguments

`<location>` — Default location for the week. If no arguments, ASK: "Where will you be this week? Same place all week, or travelling?"

Examples:
- `/weather-forecast-vivek Iowa City` — assumes Iowa City all week
- `/weather-forecast-vivek` — asks about your locations this week
- `/weather-forecast-vivek travelling` — triggers the multi-location flow

## Vivek's Personality & Preferences

These are hard constraints. Always apply them:

- **NOT a morning person.** Never recommend anything before 11 AM.
- **HATES hot weather.** Sunny, 70°F+ is miserable. The hotter and sunnier, the worse.
- **Loves cool weather.** 40°F with mild sun and no wind is PERFECT. That's the gold standard.
- **Cold tolerant.** Can walk and run comfortably in 20°F. Cold is never a dealbreaker.
- **Wind sensitive for phone use.** 15+ mph wind makes typing on a phone annoying.
- **Daily step target: 20,000+ steps.** Non-negotiable.
- **Runs regularly.** Prefers evening runs.

## Workflow

### Step 0a: Health Check

Check that the Open-Meteo MCP server is healthy:
- Verify `mcp__open-meteo__weather_forecast` is available
- If NOT healthy, tell the user to reconnect and STOP
- If healthy, proceed

### Step 0b: Resolve Locations

ASK: **"Where will you be this week? Same place all week, or travelling?"**

If same place all week:
- Get the single location, resolve to lat/lon
- Use that for all 7 days

If travelling:
- ASK: **"Give me your itinerary — which days in which cities?"**
- Example response: "Mon-Wed Iowa City, Thu-Fri Chicago, Sat-Sun NYC"
- Resolve each location to lat/lon
- Map each day to its location

Known locations:
- Iowa City → 41.6611, -91.5302
- NYC / New York → 40.7128, -74.006
- Chicago → 41.8781, -87.6298
- For other cities, use `mcp__open-meteo__geocoding`

### Step 1: Fetch Weather Data

For each unique location, call `mcp__open-meteo__weather_forecast` with:
- Coordinates for that location
- `daily`: weather_code, temperature_2m_max, temperature_2m_min, apparent_temperature_max, apparent_temperature_min, precipitation_probability_max, rain_sum, snowfall_sum, wind_speed_10m_max, wind_gusts_10m_max, sunrise, sunset
- `temperature_unit`: fahrenheit
- `wind_speed_unit`: mph
- `timezone`: appropriate for the location
- `forecast_days`: 7

If travelling, make parallel calls for each unique location.

### Step 2: Weekly Overview Table

Show a single table covering all 7 days:

| Day | Location | High/Low (°F/°C) | Feels Like | Rain % | Wind | Conditions | Vivek Rating |
|-----|----------|-------------------|------------|--------|------|------------|-------------|

**Vivek Rating** is a score from 1-10 based on how close the day matches his ideal (40°F, mild sun, no wind, no rain):
- 10 = paradise (40°F, light clouds, calm)
- 7-9 = great (cool, manageable wind, no rain)
- 4-6 = okay (mild, some sun, some wind)
- 1-3 = nightmare (hot, sunny, humid, windy)

### Step 3: Best Days / Worst Days

Rank the 7 days:
- **Best day for outdoor work** — highest Vivek Rating, explain why
- **Best day for a long run** — coolest evening temps, lowest wind, lowest humidity
- **Worst day** — stay inside, this is your nightmare, explain why
- **Best day for POWER MODE remote control** — perfect conditions for extended phone-based Claude Code work

### Step 4: Travel-Specific Insights (if travelling)

If the user is travelling:
- **Packing advice** — what to pack for the range of conditions across all locations
- **Location comparison** — which city has the best weather this week for Vivek?
- **Transition days** — if moving cities, note weather changes (e.g., "Thursday you go from 45°F Iowa City to 70°F Chicago — prepare for misery")

### Step 5: Week Strategy

Produce a day-by-day brief:

**Monday:** Iowa City, 42°F, Vivek Rating 9/10. POWER MODE day. Hit 25K steps. Evening 8-mile run at 6 PM when temps drop to 38°F. Paradise.

**Tuesday:** Iowa City, 65°F, Vivek Rating 4/10. Too warm. Front-load desk work. Short evening walk after 7 PM when temps drop below 60°F. Skip the run or go very late.

... and so on for all 7 days.

Each day gets:
- Location
- Temperature summary
- Vivek Rating
- Walking strategy
- Running recommendation
- Remote control recommendation
- One-sentence verdict

### Step 6: Meta-Insight

Close with one sentence about the week's overall pattern. Something like:
- "This week gets progressively colder — front-load desk work early in the week, save the big outdoor days for Thursday-Sunday."
- "Travelling from Iowa City to NYC means going from paradise to misery. Do your best work in Iowa City before you leave."

## Rules

1. **Always check MCP health first.**
2. **Always ASK where the user will be.** Never assume. They could be travelling.
3. **Always apply Vivek's preferences.** Cool > warm. Evening > morning. No heat.
4. **Be opinionated.** Rate each day. Tell him which days to go hard and which days to hide inside.
5. **Temperature always in both °F and °C.**
6. **Compare every day to his ideal.** The 40°F benchmark is sacred.
7. **Don't sugarcoat.** If Wednesday is 85°F, say "Wednesday is garbage. Stay inside."
8. **If travelling, compare locations.** Tell him which city wins.
9. **Vivek Rating is mandatory for every day.** 1-10, no exceptions.
10. **Week strategy must be actionable.** Specific times, specific activities, specific gear.