# Check Weather — Vivek's Personal Weather Briefing

Get a full weather briefing tailored to Vivek's preferences, walking habits, running style, and Claude Code remote-control workflow.

## Arguments

`<location>` — City name or coordinates. If no arguments, ask the user for location.

Examples:
- `/checkweather-vivek Iowa City`
- `/checkweather-vivek NYC`
- `/checkweather-vivek 41.66,-91.53`
- `/checkweather-vivek` — asks for location

## Vivek's Personality & Preferences

These are hard constraints. Always apply them:

- **NOT a morning person.** Never recommend anything before 11 AM. Morning options are mentioned only to explain why they're skipped.
- **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 + wind is manageable. Cold is never a dealbreaker.
- **Wind sensitive for phone use.** 15+ mph wind makes typing on a phone annoying. Factor this into remote-control recommendations.
- **Daily step target: 20,000+ steps.** This is non-negotiable. The strategy must achieve this.
- **Runs regularly.** Getting back into shape. Uses Strava. 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 Location

If the user provided a location name (not coordinates), map it to lat/lon:
- Iowa City → 41.6611, -91.5302
- NYC / New York → 40.7128, -74.006
- For other cities, use the `mcp__open-meteo__geocoding` tool to resolve

### Step 1: Fetch Weather Data

Call `mcp__open-meteo__weather_forecast` with:
- Coordinates from Step 0b
- `current`: temperature_2m, apparent_temperature, wind_speed_10m, relative_humidity_2m, precipitation_probability, rain, snowfall, weather_code
- `hourly`: temperature_2m, apparent_temperature, precipitation_probability, rain, snowfall, wind_speed_10m, relative_humidity_2m, weather_code
- `temperature_unit`: fahrenheit
- `wind_speed_unit`: mph
- `timezone`: appropriate for the location (America/Chicago for Iowa City, America/New_York for NYC, etc.)
- `forecast_days`: 1

### Step 2: Present Current Conditions

Show a table with:
1. **Temperature** in both °F and °C
2. **Feels Like** in both °F and °C
3. **Wind Speed** in mph
4. **Humidity** as percentage
5. **Rain Chance** as percentage
6. **Snow** — amount or "None"
7. **Conditions** — human-readable description from weather code

### Step 3: Present Hourly Breakdown

Show a table from 10 AM to 10 PM (Vivek's active hours) with:
- Time, Temp (°F/°C), Feels Like, Rain %, Wind, Humidity, Conditions
- **Bold** the best windows for Vivek's preferences

### Step 4: Walking Strategy (20K+ Steps)

Analyze the hourly data against Vivek's preferences and produce:

- **Rate the day** against Vivek's ideal (40°F, mild sun, no wind)
- **Identify the best window** — when conditions closest match his preferences (cool, calm, not sunny)
- **Identify the worst window** — when conditions are furthest from his preferences (hot, sunny, windy)
- **State "since you're not a morning person"** and explain why morning is skipped
- **Give a concrete hour-by-hour strategy** to hit 20K+ steps, concentrated in the best windows
- **Suggest what to wear** — windbreaker vs rain jacket vs layers vs t-shirt
- **Compare to his ideal** — how close is today to the 40°F-mild-sun-no-wind paradise?

### Step 5: Running Strategy

Analyze conditions for three run types:

- **Short run (3-5 miles):** Best time, expected conditions, what to wear
- **Long run (8-12 miles):** Start time, how conditions change over the run, route strategy (wind direction)
- **Ultra (15+ miles):** Is it viable today? If yes, start time and hydration notes. If no, explain why (humidity, heat, etc.)

For each:
- **State "since you're not a morning person"** and confirm evening is better
- Consider how temperature CHANGES during the run (descending temps = good for Vivek)
- Note humidity's effect on cooling efficiency
- Wind direction strategy (into wind first, tailwind home)

### Step 6: Remote Control Claude Code Strategy

Analyze conditions for phone-based Claude Code work while walking:

- **Phone screen readability** — sun glare, rain on screen, brightness needed
- **Typing comfort** — finger temperature, wind resistance on phone
- **Battery strategy** — screen brightness recommendations, estimated drain
- **Divide the day into phases:**
  - Desk Mode (when conditions are worst for Vivek's outdoor preferences)
  - Light Remote Control (read-heavy, wind too strong for typing)
  - Medium Remote Control (back-and-forth conversations)
  - POWER MODE (ideal conditions — go hard on complex Claude Code work)
- **Route recommendations** for the location — wind-sheltered paths for windy hours, open paths for calm hours
- **Match remote control intensity to weather phases** — don't fight bad conditions, wait for good ones

### Step 7: Meta-Insight

Close with one sentence connecting the day's weather pattern to how Vivek should structure his time. Something that ties the weather, the walking, the running, and the Claude Code work into a unified daily strategy.

## Rules

1. **Always check MCP health first.** Don't proceed with stale or broken data.
2. **Always apply Vivek's preferences.** Cool > warm. Evening > morning. No heat. No early mornings.
3. **Be opinionated.** Don't hedge with "you could do X or Y." Tell him what to do and when.
4. **Be specific about times.** "Go at 7 PM" not "go in the evening."
5. **Temperature always in both °F and °C.** Never just one.
6. **Compare to his ideal.** Every briefing should reference the 40°F/mild-sun/no-wind benchmark.
7. **Don't sugarcoat bad weather.** If it's 90°F and sunny, say "stay inside, this is your nightmare."
8. **Remote control strategy is mandatory.** This isn't a generic weather app — it's a briefing for someone who works from their phone while walking.