Add initial prompts for weather.daily_report

prompts/weather/daily_report/daily_report.user.md

@@ -0,0 +1,94 @@
+Generate a Daily Weather Report from the following weatherreporter JSON data package.
+
+The report may be for today or tomorrow. Determine the correct framing from `report.variant`, `report.validPeriod`, `briefing.metadata.validPeriod`, and `briefing.daily.forecastSummaryDate`.
+
+Use Markdown.
+
+# SOURCE PRIORITY
+
+Use the package in this order:
+
+1. Use `briefing.daily.bottomLine` for the overall daily theme, temperature range, and maximum precipitation probability.
+2. Use `briefing.daily.dayparts` for daypart timing, temperatures, precipitation chances, wind, dominant conditions, and notable conditions.
+3. Use `briefing.daily.narrativePeriods` to confirm and reconcile the official day/night forecast wording.
+4. Use `briefing.daily.discussion.keyMessages` for broader forecast context.
+5. Use `briefing.daily.discussion.shortTerm` for confidence, uncertainty, local/regional nuance, and what-to-watch notes that affect the report’s valid period.
+6. Use `briefing.daily.discussion.longTerm` only if it affects the valid day, the overnight period immediately following it, or a brief what-to-watch note. Do not let multi-day or next-week discussion take over a Daily Report.
+7. Use `briefing.metadata.alerts` and any alert details if present.
+8. Use `recentChanges.items` only if it contains meaningful changes.
+9. Use `sourceWarnings` only to avoid overclaiming. Do not mention missing internal sources unless they materially limit the report.
+10. Use `currentConditions` only as context at generation time. For tomorrow or future reports, do not describe current conditions as if they are forecast conditions.
+
+# INTERPRETATION RULES
+
+- Do not overstate low precipitation probabilities. A 20–30% chance should usually be described as “slight chance,” “spotty,” “isolated,” “not widespread,” or “potential,” unless other package data supports stronger wording.
+- Do not let a benign `dominantCondition` hide a lower-frequency but more important hazard. If thunderstorms, snow, ice, fog, high wind, extreme heat, flooding, or alerts appear in any relevant hourly, daypart, narrative, or discussion data, mention them appropriately.
+- If hourly/daypart data and narrative forecast wording differ slightly, reconcile them conservatively. Prefer wording that captures both without overstating either.
+- If AFD context describes hazards that apply to portions of the forecast area that are clearly outside the report location, preserve that limitation. Do not imply a direct local threat unless the hourly forecast, narrative forecast, alerts, or discussion clearly support it for the report location.
+- Treat AFD discussion as important context, not as the backbone of the report. Do not quote or summarize the AFD at length.
+- If there are no active alerts, mention that briefly only if useful.
+- If `recentChanges.items` is empty, omit the Recent Changes section.
+- If outdoor-window data appears inconsistent, unhelpful, or unsupported by the daypart forecast, do not rely on it. Instead, infer practical planning windows cautiously from the daypart data.
+- Do not include raw JSON, internal field names, source hashes, endpoint names, implementation details, or debugging notes.
+- Do not apologize for missing data.
+- Do not include generic safety advice unless it is specifically supported by the forecast.
+
+OUTPUT FORMAT
+
+Begin with:
+
+# [Today’s/Tomorrow’s] Weather — [Location Name]
+
+On the next line, include the valid date in natural language.
+
+Then include the following sections.
+
+## Bottom Line
+
+Write 1–3 short sentences summarizing the day. Include the overall character of the weather, the expected temperature range, and the main planning concern, if any.
+
+## At a Glance
+
+Use short bullets. Include only items supported by the data. Possible bullets include:
+
+- High / low
+- Main weather theme
+- Rain or storm chance
+- Wind
+- Alerts
+- Best or most usable outdoor window, if supportable
+- Main thing to watch
+
+## Daypart Forecast
+
+Write one concise bullet per available daypart. Use natural language timing.
+
+For each daypart, include:
+- Expected temperature range or trend
+- Main condition
+- Precipitation or storm chance, if relevant
+- Wind only if meaningful
+- Practical planning note, if useful
+
+Keep each bullet to one or two sentences.
+
+## Planning Notes
+
+Include 2–4 practical bullets focused on decisions such as commute, school/workday, outdoor plans, evening plans, rain gear, heat/cold comfort, or timing to monitor. Omit this section if there are no useful planning notes.
+
+## Recent Changes
+
+Include this section only if `recentChanges.items` contains meaningful changes. Summarize the changes in plain English. Do not fabricate changes.
+
+## Confidence / What to Watch
+
+Include 1–3 sentences. Mention uncertainty only if supported by the forecast discussion, recent changes, or conflicting forecast signals. Otherwise, identify the main item to monitor, such as shower/storm timing or coverage.
+
+# STYLE
+
+- Plainspoken, calm, and useful.
+- Avoid hype.
+- Avoid filler.
+- Avoid unsupported precision.
+- Do not sound like a TV meteorologist.
+- Do not include caveats about being an AI model.