Overview
This prompt aims to guide developers in enhancing an Expert Advisor by adding configurable input parameters for user flexibility. Programmers and traders will benefit by gaining more control over trading strategies without altering the core EA code.
Prompt Overview
Purpose: The enhancements aim to provide user-configurable settings for trade limitations and indicator breakout thresholds.
Audience: This information is intended for developers and traders using Expert Advisors in trading platforms.
Distinctive Feature: New input parameters allow users to customize trading behavior without modifying the EA’s core logic.
Outcome: Users can easily configure their trading strategies to meet specific needs and preferences.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Cryptocurrency & Blockchain, Fintech & Digital Banking, Productivity & Workflow
- Techniques: Output Constraints, Role/Persona Prompting, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
You are tasked with enhancing an existing Expert Advisor (EA) for trading by adding new input parameters that enable specific user configurations without modifying the EA’s underlying code or logic.
**Specifically, add the following inputs:**
1. Trade Limitation Input:
– An input to limit the EA to one trade per day.
– Include options to specify whether the trade can be long, short, or both within that day.
2. Indicator Breakout Threshold Input:
– Inputs to set a threshold (“x times”) after an indicator breakout occurs.
– This will trigger the placement of pending orders.
Your enhancements should consist solely of input parameters, enabling these functionalities through configuration changes rather than code logic modifications.
**# Steps**
– Define input variables corresponding to “one trade per day” controls, including options for:
– Long trades
– Short trades
– Both trades
– Define an input variable to specify the number of times the indicator breakout must occur before placing pending orders.
– Ensure these inputs can be integrated with existing EA functionality without altering internal code logic.
**# Output Format**
Provide the definitions of the new input parameters in the format appropriate for the EA’s input settings (e.g., MQL4/MQL5 input variables), with a clear explanation of each input’s purpose and usage.
**# Notes**
– Do not change any existing code or logic; only add input parameters.
– Inputs should be named clearly and descriptively.
– Assume the EA code will internally read these inputs and implement the logic accordingly.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Open your EA code file in a suitable editor.
- Paste the prompt into the editor for reference.
- Define new input variables as specified in the prompt.
- Ensure inputs are descriptive and clear for user understanding.
- Save the changes and test the EA with new parameters.
Tips for Best Results
- Trade Limitation Input: Limit the EA to one trade per day, with options for long, short, or both types of trades.
- Long Trade Option: Enable or disable long trades for the day based on user preference.
- Short Trade Option: Enable or disable short trades for the day based on user preference.
- Indicator Breakout Threshold: Set the number of times an indicator breakout must occur before triggering pending orders.
FAQ
- What is the purpose of the trade limitation input?
It allows users to limit the EA to one trade per day, specifying long, short, or both. - How can users configure trade types for the EA?
Users can select options for long trades, short trades, or both within the daily limit. - What does the indicator breakout threshold input do?
It sets a threshold for how many times an indicator breakout must occur before placing orders. - Can these inputs be integrated without changing the EA's code?
Yes, these inputs are designed to enhance functionality without modifying the existing code logic.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
