Algo Trading and Bots

Trading bot prompts and templates

Turn a trading idea into a structured bot specification covering signals, execution, risk controls, testing, monitoring, and failure handling.

A useful addition from our prompt packs: Strategy Template Launch Kit

Edit highlighted fields Copy-ready prompt

10 copy-ready trading bot prompts

Universal Bot Strategy Template Selector

Universal template Medium

Maps market, holding period, execution constraints, and a stated edge hypothesis to an appropriate strategy architecture and test plan.

ID 221

Act as an algorithmic trading architect. My market is stocks/crypto/forex/futures, venue is the crypto market, holding period is 4 hours, and edge hypothesis is trend/mean reversion/spread/arbitrage/liquidity providing. Select a suitable template and specify data, signals, execution, risk, states and transitions, parameters, and telemetry. Explain what evidence the hypothesis requires and reject the premise if it cannot be tested.

Trend-Following Bot Template

Medium

Defines a trend bot through regime filter, entry, controlled additions, exits, execution, position limits, and operational safeguards.

ID 222

Act as a systematic trend-system designer. For the crypto market, specify a regime filter, entry trigger, controlled add-on rules, invalidation, target, trailing or time exit, order types, retries, slippage limits, maximum positions, pyramiding limits, and cooldowns. List parameters with reasoned initial values for 15-minute data that are explicitly not presented as optimal, plus tests needed before deployment.

Mean-Reversion Bot Template

Medium

Includes a regime filter and adverse-move controls so mean reversion is not applied blindly during persistent trends or structural breaks.

ID 223

Act as an algorithmic strategy designer. For instrument universe, specify a trend or regime gate, mean-reversion signal, confirmation, target, partial exit, stop, invalidation, maximum adverse move, time limit, trade-frequency cap, and correlated-exposure control. List windows and thresholds as parameters and explain how to validate them without overfitting.

Pairs Trading and Statistical Arbitrage Template

Pro

Separates pair selection and maintenance, spread construction, signal, exposure, execution of both legs, and live health monitoring.

ID 224

Act as a statistical-arbitrage architect. For the crypto market, define pair selection, liquidity and stability tests, maintenance and replacement rules; spread construction and normalization; entry, exit, stop, and regime-break signals; gross and net exposure and correlation-shock controls; and coordinated execution with partial fills and leg risk. Add telemetry for spread behavior, fill quality, borrow or funding, and exposure drift.

Inventory-Aware Market-Making Template

Pro

Defines reference price, quoting, refresh, inventory skew, adverse selection, cancellation, and emergency shutdown for one market.

ID 225

Act as a market-making strategist. For spot/crypto on the crypto market, specify reference price, quote spread, size and refresh; inventory limits and skew; fee and rebate treatment; volatility response; adverse-selection detection; cancellation and replacement; queue and latency assumptions; stuck-order handling; and kill-switch conditions. Include partial fills, stale data, exchange failure, and a validation plan.

Spot-Perpetual Basis and Funding Template

Pro

Structures a hedged basis or funding strategy with rebalancing, two-leg execution, liquidation, collateral, and exchange risk.

ID 226

Act as a crypto basis-trading specialist. For ETF portfolio, define entry by basis, funding, liquidity, fees, borrow availability, and expected convergence; hedge ratio and rebalancing; and exit by convergence, time, cost, or regime change. Include liquidation, collateral and depeg risk, counterparty concentration, leg sequencing, partial fills, transfer constraints, and emergency flattening. Keep the specification platform-agnostic.

Bot Strategy Skeleton

Beginner

Turns a strategy idea into a minimal structure of parameters, states, signals, execution, risk controls, and telemetry.

ID 227

Convert paste idea into a bot strategy skeleton. Return only: parameters with units; states and transitions; signal rules and timing; execution rules; risk and shutdown controls; and logging and telemetry fields. Mark every ambiguous input that must be resolved before implementation.

Trading Bot Threat Model

Pro

Prioritizes market, liquidity, data, execution, infrastructure, state, and logic failures before a bot reaches production.

ID 228

Threat-model this bot: describe in 3 lines. Prioritize ten failure modes across market behavior, liquidity, data, clock, order lifecycle, exchange or broker, network, state, configuration, and logic. For each, provide impact, detection signal, mitigation, safe state, and a test that demonstrates the control works.

Trading Bot Configuration Schema

Medium

Creates a reusable configuration contract so parameters are typed, bounded, versioned, and not hidden in strategy code.

ID 229

Create a YAML-like configuration schema for a trend-following strategy bot. Cover universe, sessions and timeframes, sizing, signals, execution, risk, safety limits, monitoring, and feature flags. For each parameter include type, unit, valid range, a nonoptimized example value, explanation, required or optional status, and behavior when the value is missing or invalid.

Minimum Logging for Debuggable Trading Bots

Pro

Defines the smallest telemetry set needed to reconstruct signals, decisions, orders, fills, positions, risk interventions, state, and failures.

ID 230

Define the minimum logging and telemetry specification for a trading bot. Group fields by market data, signal, decision, order lifecycle, fill, position, risk, system state, and error. Include correlation IDs, event and receive timestamps, venue identifiers, strategy and configuration version, units, and data-quality flags so an incident can be reconstructed without logging secrets.

Copy the full subcategory

Includes subcategory info, prompt IDs, descriptions, difficulty, and prompt text.

How to use prompts to specify a trading bot

Start with the market and decision rules, then require explicit assumptions, data needs, execution behavior, and risk limits. The goal is an implementable specification, not code that hides unresolved trading logic.

Define entries, exits, position sizing, invalidation, and the market conditions in which the bot should stay inactive.
Describe order types, partial fills, fees, slippage, latency, and exchange or broker constraints.
Require test cases, monitoring metrics, reconciliation, alerts, and a controlled shutdown process.