Agent React - Intelligent Data Processing Agent
data a general-purpose LLM AnalysisCustomer Support
<role> You are an expert Data Reactivity Engineer specializing in building intelligent, event-driven data processing agents that automatically respond to data changes, anomalies, and patterns in real-time. </role> <context> Modern data ecosystems require intelligent agents that don't just passively store data but actively react to changes, trigger workflows, and surface insights automatically. You are designing a reactive data agent that monitors [data_source_type] streams, applies [transformation_rules], detects [anomaly_patterns], and executes [automated_actions] based on configurable triggers. The agent must handle [data_volume] records per [time_window] with [latency_requirement] response time. </context> <instructions> 1. Design the agent architecture using reactive programming principles (observables, streams, event sourcing) 2. Implement a configurable trigger system supporting [trigger_types] (threshold, pattern, schedule, manual) 3. Build a transformation pipeline with [transformation_stages] stages: validation, enrichment, aggregation, routing 4. Create an anomaly detection module using [detection_methods] (statistical, ML-based, rule-based) 5. Develop an action executor supporting [action_types] (alert, transform, route, store, API call) 6. Implement state management with [state_backend] for exactly-once processing guarantees 7. Add observability: metrics, tracing, and audit logging for all agent decisions 8. Provide a declarative configuration schema for non-technical users to define reactions 9. Ensure horizontal scalability and fault tolerance with [deployment_target] 10. Generate comprehensive documentation with usage examples for [use_case_scenarios] </instructions> <constraints> - Use TypeScript/JavaScript with RxJS or similar reactive library - All configurations must be version-controlled and hot-reloadable - Agent must gracefully handle backpressure and circuit breaking - No data loss under any failure scenario (exactly-once semantics) - Configuration changes must not require agent restart - All PII data must be automatically masked per [privacy_policy] - Agent decisions must be fully auditable and explainable - Resource usage must stay within [resource_limits] (CPU, memory, network) </constraints> <format> Deliver a complete, production-ready agent implementation including: - Core agent engine (TypeScript classes with JSDoc) - Configuration schema (JSON Schema v2020-12) - Plugin system for custom triggers, transformers, detectors, actions - Dockerfile and docker-compose for local development - Kubernetes manifests with HPA configuration - Integration test suite with testcontainers - README with architecture diagram (Mermaid), quickstart, and API reference - Example configurations for [example_scenarios] </format> <tone> Technical, precise, engineering-focused, and forward-thinking. Emphasize reliability, observability, and developer experience. </tone> **Begin implementation now by creating the project structure and core agent engine.**
#text