Updated the weather daily report prompt to include more detailed writing style instructions

This commit is contained in:
2026-05-29 22:41:27 -05:00
parent d31dc03a57
commit 2fb5fdcf2c

View File

@@ -37,10 +37,11 @@ The first sentence must state the most likely weather outcome for the day, inclu
The second sentence must state the most important caveat, uncertainty, or alternate outcome, if one exists. If there is no meaningful caveat, the second sentence may briefly say that no major complications are apparent.
Examples of the desired style:
In the lead, distinguish the main weather outcome from the caveat. If showers and thunderstorms have different timing, state that difference rather than combining them as a single all-day risk.
- “Saturday is expected to be warm, mostly cloudy, and mostly dry, with a high around 83.”
- “A few isolated showers or thunderstorms are possible during the afternoon and early evening, but coverage looks limited and most of the day should remain dry.”
Example of the desired style:
- "Tomorrow is expected to be warm, mostly cloudy, and mostly dry, with a high near 72. A slight shower chance lingers at times, with isolated thunder more favored late afternoon into early evening."
Do not open with generic planning advice.
@@ -73,13 +74,30 @@ If precipitation chances are low and no meaningful impacts are expected, do not
# DAYPART RULES
Include a `## Daypart Forecast` section.
In `## Daypart Forecast`, each daypart bullet should normally follow this pattern:
Write one concise bullet per available daypart. For generally dry or quiet dayparts, one short sentence is enough. Include the expected temperature range or trend and general conditions.
`- **Daypart:** [Sky/general condition] with [temperature trend or approximate temperature]. [Precipitation/storm sentence only if relevant.] [Wind sentence only if meaningful.]`
If precipitation is likely to begin, end, peak, or become more intense during a daypart, include more detail for that daypart.
Always include the expected sky or general condition when the data supports it, such as mostly cloudy, partly cloudy, sunny, overcast, rainy, snowy, foggy, or stormy.
Do not force equal detail across all dayparts.
Do not describe a daypart temperature maximum as “High of X” unless the daypart covers the main daily high period and that phrasing sounds natural. Prefer:
- “temperatures around 82”
- “temperatures rising from the upper 60s into the low 70s”
- “temperatures near 80”
- “cooling from the low 80s into the low 70s”
- “holding in the upper 60s”
- “peaking near 83 late in the day”
For quiet or mostly dry dayparts, keep the bullet to one sentence.
For dayparts with meaningful precipitation, thunder, snow, ice, fog, high wind, or other weather impacts, add a second sentence with timing and caveat details.
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.”
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.
# AFD / METEOROLOGICAL CONTEXT RULES