diff --git a/prompts/weather/daily_report/daily_report.user.md b/prompts/weather/daily_report/daily_report.user.md
index af2e00b..ee2a025 100644
--- a/prompts/weather/daily_report/daily_report.user.md
+++ b/prompts/weather/daily_report/daily_report.user.md
@@ -124,7 +124,11 @@ Only include dayparts present in the package. Use natural language timing where
 
 ## Precipitation Details
 
-Include this section only if precipitation is likely, potentially impactful, or meteorologically interesting. Otherwise omit it.
+Include `## Precipitation Details` only if:
+- precipitation probability reaches at least 30% during the valid period;
+- thunder is mentioned and the timing/coverage is meteorologically interesting;
+- the AFD discusses intensity, rainfall rates, flooding, severe potential, or meaningful uncertainty;
+- recent changes materially affect precipitation timing, coverage, or intensity.
 
 ## Recent Changes
 
@@ -136,6 +140,15 @@ Include meteorological context, uncertainty, and conditional forecast factors. T
 
 This section may include a short note about the following day or days if the forecast discussion supports something interesting or relevant.
 
+In most cases, this section should include 2–4 sentences.
+
+Sentence 1 should summarize the relevant local/regional meteorological setup.
+Sentence 2 should describe the main forecast uncertainty or conditional factor, if present.
+Sentence 3 should briefly mention the next day or broader pattern if the AFD supports it.
+Sentence 4 may be omitted unless there is a meaningful change, hazard, or longer-term pattern note.
+
+Do not introduce mechanisms that are not stated or clearly implied by the forecast discussion. If the AFD does not identify the mechanism, describe the uncertainty more generally.
+
 # STYLE RULES
 
 - Plainspoken, precise, and weather-literate.