Overview
This prompt aims to guide developers in enhancing an Expert Advisor’s input handling for dynamic indicator integration. Programmers working with trading algorithms will benefit from these instructions to improve functionality without disrupting existing code.
Prompt Overview
Purpose: This task aims to enhance an existing Expert Advisor by integrating dynamic indicator input capabilities.
Audience: The intended audience includes developers familiar with trading algorithms and the structure of Expert Advisors.
Distinctive Feature: The solution focuses on adding new input parameters without altering the existing logic or functionality of the EA.
Outcome: The result will be an EA that allows users to select indicators dynamically while preserving its original behavior.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Development Tools & DevOps, Productivity & Workflow
- Techniques: Prompt Templates, Structured Output, Zero-Shot Prompting
- 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
- [IndicatorInput] – Indicatorinput
- [OriginalEAcode] – Originaleacode
Example Variables Block
- [IndicatorInput]: Moving Average Period
- [OriginalEAcode]: Expert Advisor v1.0
The Prompt
You are tasked with integrating additional indicator inputs into an existing Expert Advisor (EA) for trading. Your objective is to enable dynamic loading of indicator inputs when a specific indicator is selected within the EA’s input parameters, while ensuring that the existing code logic and functionality remain unchanged.
Specifically, when a user selects an indicator option from the EA’s input interface, your solution must seamlessly load and utilize the corresponding indicator inputs, preserving all current behaviors and logic.
# Steps
1. Analyze the Current Input Structure
Examine how indicator selections are currently managed within the EA.
2. Design an Approach
Create a method to conditionally append or load indicator-specific input parameters based on the user’s selection.
3. Maintain Existing Code Integrity
Ensure that this addition does not modify any existing code or alter the internal logic of the EA.
4. Implement Input Loading
Develop the input loading mechanism so that the EA continues to function as it did before, but with enhanced flexibility for dynamic indicator inputs.
5. Validate the Solution
Confirm that there are no changes in EA behavior, except for the newly added indicator input functionality.
# Output Format
Provide detailed instructions or code snippets that demonstrate how to dynamically add these indicator inputs without altering existing code and logic. If necessary, use placeholders such as [IndicatorInput] and [OriginalEAcode] to represent existing components. Include explanations for each step to clarify how the preservation of existing functionality is achieved.
# Notes
– Do not suggest rewriting or refactoring the entire EA.
– Focus exclusively on input handling additions.
– Assume the user has a basic understanding of the EA environment and how indicators integrate within it.
Screenshot Examples
How to Use This Prompt
- [IndicatorSelection]: User-selected indicator option.
- [DynamicInputs]: Inputs loaded based on selection.
- [InputStructure]: Current management of indicator inputs.
- [LoadingMechanism]: Method for appending indicator inputs.
- [PreserveLogic]: Maintain existing EA functionality.
- [ValidationProcess]: Confirm unchanged EA behavior.
- [UserInterface]: Interface for selecting indicators.
- [CodeIntegrity]: Ensure no existing code modifications.
Tips for Best Results
- Analyze Current Structure: Review the EA’s input parameters to identify how indicators are currently selected and managed.
- Design Dynamic Loading: Create a function that checks the selected indicator and appends the relevant input parameters dynamically.
- Preserve Logic: Ensure that the new input handling does not interfere with the existing code by using conditional statements that only activate when specific indicators are selected.
- Test Thoroughly: Run multiple scenarios to validate that the EA operates as intended, confirming that only the new indicator inputs are affected by the changes.
FAQ
- How can I analyze the current input structure?
Review the EA's input parameters section to identify how indicators are currently defined and selected. - What method should I use for dynamic input loading?
Implement a conditional statement that checks the selected indicator and loads corresponding input parameters accordingly. - How do I ensure existing code remains unchanged?
Add new input handling logic without modifying existing functions or variables in the EA's code. - What steps validate the new functionality?
Test the EA with various indicator selections to ensure behavior remains consistent while new inputs are functional.
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.
