SCREENERBOTDocs
DocsDashboard GuidesAuto TraderStrategies
Auto Trader / Strategies

Build rule-based entry and exit strategies

Create, edit, validate, test, prioritize, and enable reusable rule trees directly inside Auto Trader.

Dashboard/Auto Trader/Strategies

Types

ENTRY and EXIT strategies

Logic

Nested AND, OR, and NOT groups

Catalog

Eight implemented condition types

Workflow

Validate and test before enabling

What the Strategies tab is for

Strategies is the full rule editor embedded inside Auto Trader. Each strategy is an ENTRY or EXIT definition with a timeframe, priority, enabled state, and recursive AND, OR, or NOT rule tree built from the condition catalog.

Reading the interface

Use each control with the rest of the automated trading pipeline in mind.

Strategy definition

The editor stores the identity and evaluation context for each rule tree.

Type, timeframe, and priority

Choose whether the strategy opens or exits positions, select its OHLCV timeframe, and set evaluation order.

Recursive rule tree

Combine condition leaves into nested AND, OR, and NOT groups. Short-circuit evaluation avoids unnecessary work.

Validation and testing

Validate the structure before saving and use the test action to evaluate an existing strategy against a token.

Implemented condition catalog

These are the condition types currently registered by the trading engine.

Price analysis

Price Change %, Price vs Moving Average, and Price Breakout.

Candles and volume

Consecutive Candles, Candle Size Pattern, and Volume Spike.

Market and position context

Pool Liquidity Level and Position Holding Time.

Recommended workflow

  1. 1

    Create an ENTRY or EXIT strategy and give it a clear name that describes the market thesis.

  2. 2

    Choose the timeframe, then build the smallest rule tree that expresses the intended signal.

  3. 3

    Edit each condition parameter and validate the complete strategy.

  4. 4

    Test where practical, save it, then enable it from the editor or Strategy Control.

Practical guidance

  • Prefer a small explainable rule tree over many loosely related conditions.
  • OHLCV conditions use candle data; trade execution and P&L still use live pool prices.
  • Position Holding Time is meaningful for EXIT strategies because it requires position context.

The editor does not provide RSI or MACD conditions. Document and build only from the condition types actually shown in the catalog.