Prompting your AI
How to describe scripts and backtests so your connected AI gets them right the first time.
Most disappointing results from a connected AI aren't AI failures — they're underspecified requests. The AI can read StrategyTune's built-in documentation topics, so it knows the script APIs and the platform. What it can't know is what you want: the exact rules, the parameters, the look. These tips help you describe the target — one request at a time — so it can hit it.
Be specific about the math and the rules
- Name the formula or describe it precisely.
- For signals and filters, say exactly when the condition starts and ends — "signal when the fast SMA crosses above the slow SMA", "filter is on while price is inside the bands".
- For Strategy scripts, spell out entries, exits, stop-loss and take-profit rules, and position sizing.
Pin parameter names and ranges
Inputs default to whatever the AI guesses if you don't say otherwise. Tell it what's
reasonable: "length int, default 20, min 2, max 200." Parameters show up in
the indicator's settings dialog and in backtest run dialogs, so tight, well-named ranges
pay off every time you (or the AI) re-run with different values.
Describe the visual you want
For indicators, say what the output should look like, not just what it computes:
- "Three lines, the middle one bolder than the bands."
- "Histogram in green when positive, red when negative."
- "Dashed horizontal lines at 30 and 70, with a translucent fill between."
- Say whether it belongs on the price pane or in its own pane below.
Ask it to verify, not to guess
A connected AI doesn't have to speculate about what it did — it can check. Use that:
- After a save, ask it to read the saved script back and confirm the rules match what you asked for.
- After changing what's on a chart or timeline, ask it to read the current state — which indicators are on, with which parameters.
- Never accept a prediction of how a strategy would perform. Ask it to run the backtest and report the actual results — the statistics, equity, and logs come from the run, not from the AI's imagination.
You don't need to paste API documentation — the AI can read StrategyTune's built-in documentation topics itself.
Something missing or wrong? Email support@strategytune.com.