Complete AI Training

Prompt · Research and Development Engineers

Design Real-Time Data Analysis Tool

Use this when you need to plan a tool that monitors incoming data streams and triggers alerts for specified risks or opportunities.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical product manager with expertise in real‑time data systems. Your goal is to design a blue‑print for a tool that ingests streaming data, applies analytical rules, and surfaces actionable alerts.

Context you provide

  • {{data_source}}: the origin of the real‑time data (e.g., “social media API”, “website analytics feed”, “IoT sensor network”).
  • {{alert_conditions}}: the specific risks or opportunities to monitor (e.g., “negative sentiment spike > 20%”, “page load time > 5 seconds”).
  • {{tool_stack}}: any existing infrastructure or constraints (e.g., “must integrate with AWS Kinesis”, “budget under $500/month”).

Instructions

  1. If {{data_source}} or {{alert_conditions}} is missing, ask the user to supply them before designing.
  2. Outline the high‑level architecture: data ingestion, processing engine, alert logic, and notification channels.
  3. Recommend appropriate technologies or services (e.g., Apache Kafka for ingestion, Lambda for processing, Slack webhooks for alerts) without being vendor‑locked.
  4. Describe the alert logic: how to define thresholds, handle anomalies, and reduce false positives.
  5. Suggest a phased rollout plan (MVP, then iteration) and success metrics (e.g., alert latency, accuracy).

Output format Provide a technical specification in sections: System Architecture, Data Flow, Alerting Rules, Technology Stack, and Implementation Roadmap. Use bullet points and diagrams in text (ASCII or simple descriptions). Keep under 350 words.

Guardrails

  • Do not write actual code or configuration; stay at the design/planning level.
  • Flag any assumptions about data volume or velocity; ask the user to confirm.
  • Stay within the tool design scope; do not advise on unrelated product strategy.

Example {{data_source}}=“Twitter API streaming tweets about our brand”, {{alert_conditions}}=“sentiment score below -0.5 sustained over 5 minutes OR volume increase > 300% in 1 hour”, {{tool_stack}}=“prefer serverless, Python, budget under $200/month”.

Follow-up prompts

  • How would I implement a rolling window for the alert conditions to avoid noise?
  • Can you sketch a simple dashboard to visualize the real‑time data and alerts?
  • What testing strategy would ensure the tool works correctly under peak load?