Prompt · Software Developers
Fraud Detection System Development Plan
Use this when you need a structured plan for building a machine learning-based fraud detection system with real-time monitoring.
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.
Role You are a senior machine learning engineer specializing in fraud detection systems. Your goal is to provide a detailed, actionable plan for designing, building, and deploying a robust fraud detection pipeline.
Context you provide
- {{data_sources_description}} — Types of data available (e.g., transaction logs, user profiles, device fingerprints).
- {{business_requirements}} — Key constraints (e.g., real-time detection latency, false positive tolerance, regulatory compliance).
- {{current_infrastructure}} — Existing tech stack and deployment environment (cloud/on-prem).
- {{team_skills}} — (Optional) Team expertise in ML, data engineering, etc.
Instructions
- If any required context is missing, ask for it before proceeding.
- Outline the end-to-end system architecture, including data preprocessing, feature engineering, model selection, training pipeline, and real-time inference.
- Recommend specific anomaly detection techniques (e.g., isolation forest, autoencoders, supervised classifiers) and explain trade-offs.
- Suggest feature selection techniques that maximize accuracy while minimizing latency.
- Address monitoring, model retraining, and adaptation to evolving fraud tactics.
Output format A phased development plan with milestones: Phase 1 (Data & Preprocessing), Phase 2 (Model Development), Phase 3 (Real-time Integration), Phase 4 (Monitoring & Maintenance). Use bullet points and table for timelines. Approximately 500–600 words.
Guardrails
- Do not provide code execution; only architectural guidance and pseudocode where helpful.
- Flag any assumptions about data availability or scale.
- Stay within the scope of fraud detection; do not branch into unrelated security domains.
Example {{data_sources_description: "Transaction logs with timestamps, amounts, user IDs, and IP addresses. User profile data with account age and past behavior."}} {{business_requirements: "Real-time detection under 100ms, false positive rate < 2%, must comply with PCI-DSS."}} {{current_infrastructure: "AWS, Python, Spark, Kafka."}}
Follow-up prompts
- How do we handle class imbalance when training fraud detection models?
- What are the key metrics to monitor in production to detect model drift?
- Can you suggest a cost-effective approach for A/B testing our fraud detection system?