From 83fadb8de307ada885f336e8da7ed346d0ca281d Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Fri, 29 May 2026 23:14:48 -0500 Subject: [PATCH] Add additional detail to the daypart instructions for the daily weather report --- prompts/weather/daily_report/daily_report.user.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/prompts/weather/daily_report/daily_report.user.md b/prompts/weather/daily_report/daily_report.user.md index 07b62f4..6e86376 100644 --- a/prompts/weather/daily_report/daily_report.user.md +++ b/prompts/weather/daily_report/daily_report.user.md @@ -95,6 +95,8 @@ For dayparts with meaningful precipitation, thunder, snow, ice, fog, high wind, Keep sky/general condition separate from precipitation probability. For example, do not write only “slight chance of showers” when the broader condition is “mostly cloudy with a slight chance of showers.” +When precipitation is likely during only part of a daypart, describe the precipitation timing first, then describe the sky/temperature trend after that. Do not use a benign sky condition such as “mostly sunny” as the leading phrase for a daypart if showers, storms, snow, ice, fog, or other impacts are likely during that same daypart. + Avoid unsupported timing precision. Do not say precipitation “develops after,” “moves in around,” “clears after,” or “ends by” unless the hourly data, narrative forecast, or discussion clearly supports that timing. If the signal is broad, use broader wording such as “a slight chance continues,” “possible during the period,” or “most favored late in the period.” Avoid “throughout the day” unless the same weather risk is meaningfully present across most dayparts. When possible, distinguish lower-impact shower chances from more specific thunder chances. @@ -122,7 +124,7 @@ If `briefing.daily.discussion.longTerm` contains interesting context about the f Use this structure: -# [Today’s/Tomorrow’s] Weather — [Location Name] +# [Today’s/Tomorrow’s/DOW's] Weather — [Location Name] [Valid date]