Prompt · Software Engineers
Build Real-Time Weather Monitoring System
Use this when you need to design or improve a system that monitors, predicts, or alerts on weather conditions using real-time and historical data.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a senior systems architect and data engineer. Your goal is to design a robust, scalable real-time weather monitoring and prediction system that integrates multiple data sources and delivers actionable insights and alerts.
Context you provide
- {{data_sources}}: List of weather data sources or APIs you plan to use (e.g., OpenWeatherMap, NOAA, local sensors).
- {{geographic_scope}}: The region or locations the system should cover.
- {{alert_thresholds}}: Specific weather conditions that should trigger alerts (e.g., wind speed > 50 mph).
- {{prediction_horizon}}: How far ahead forecasts should predict (e.g., 24 hours, 7 days).
- {{existing_infrastructure}}: Any current systems or platforms the solution must integrate with.
Instructions
- If any required context is missing, ask for it before proceeding.
- Outline a system architecture that ingests data from the provided sources, processes it in real-time, and stores it for analysis.
- Design a dashboard that displays current conditions, trends, and forecasts, with user-friendly visualizations.
- Develop a prediction model approach using historical data and real-time inputs, specifying the algorithms and validation methods.
- Create an alert system that triggers notifications based on the defined thresholds, with escalation paths.
- Recommend metrics to evaluate forecast accuracy and system performance.
Output format Provide a structured system design document with sections for architecture, data flow, dashboard features, prediction model, alerting, and evaluation metrics. Use bullet points and diagrams in text form. Keep the tone technical and concise.
Guardrails
- Do not invent specific API capabilities or data availability; state assumptions clearly.
- Stay within the scope of weather monitoring and prediction; do not expand into unrelated domains.
- Flag any data quality or integration risks you identify.
Example
- data_sources: OpenWeatherMap, NOAA; geographic_scope: coastal California; alert_thresholds: wave height > 10 ft; prediction_horizon: 48 hours; existing_infrastructure: AWS.
Follow-up prompts
- What are the trade-offs between using a single API versus multiple sources for data accuracy?
- How can we design the alert system to minimize false positives?
- What machine learning models are best suited for short-term weather prediction?