Skip to main content

Documentation Index

Fetch the complete documentation index at: https://uncoded.ch/docs/llms.txt

Use this file to discover all available pages before exploring further.

Recipes are validated, worked-example strategies you can build in the SignalEditor. Each recipe is end-to-end: what to build, when to use it, when to avoid it, what the expected behavior looks like, and the most common mistakes. Use these as starting points — don’t run them blindly.

​
Recipes vs Modes — the difference

ModesStrategy Recipes
WhatPre-built complete strategiesOperator-authored signal graphs
Where they liveTradingBot’s imageSignalEditor’s strategies directory
Authored byunCoded teamYou
Direct executionTradingBot runs themSignalEditor evaluates → SignalsBot writes config → TradingBot trades
CustomizationLimited (parameters only)Full graph control
Best forPredictable starter strategiesCustom logic beyond modes
Modes are simpler. Recipes are more flexible. Most operators run modes for their first month, then explore recipes once they have intuition.

​
The 4 recipes in this section

RSI Mean-Reversion

The textbook starter strategy. RSI(14) on 15m price. Buy when RSI is oversold and price is below trend. Reliable in chop and ranging markets.

EMA-Cross Trend-Follow

The classic trend-follower. EMA(20) crossing EMA(50) on 1h price. Late-but-confirmed entries on uptrends. Whipsaws in chop, captures trends.

Multi-Timeframe Strategy

Daily trend filter + 15-minute entry. Two-strategy pattern that combines longer-cycle context with faster entry timing.

TradingView Webhook

Connect TradingView’s Pine-Script alerts to your unCoded SignalsBot. Use external charting setups to drive your bot.

​
How to use recipes

1

Read the full recipe before building

Each recipe explains when to use it, when not to use it, and what the expected behavior looks like. Read the “When NOT to use” section carefully — it’s where most failed strategies originate.
2

Build the strategy in the SignalEditor

Open the SignalEditor canvas. Drop the nodes the recipe describes. Connect them as the recipe shows.
3

Preview against history

Run the SignalEditor’s preview against recent historical data. Confirm the firing pattern matches what the recipe predicts. If it fires 100x more than expected, you’ve miswired something.
4

Backtest on longer windows

Submit the strategy to the Backtester for multi-month validation. Validate not just total return but max drawdown, win rate, average trade duration.
5

Forward-test on small capital

Run the strategy live with small capital ($500–$1,500) for 2 weeks. Compare live behavior to backtest behavior — they should agree.
6

Promote to full capital if validated

If forward-test agrees with backtest, you can scale up. If they diverge, investigate before scaling.
7

Document your version

Save the strategy JSON to your operator records. Version-control via Git is ideal. You’ll want to know “what version of this strategy was running on date X” later.

​
What every recipe shares

Every recipe in this section follows the same structure:
  • Goal — what the strategy is trying to capture.
  • When to pick this recipe — regime fit, capital fit, operator profile fit.
  • When NOT to pick this recipe — disqualifying conditions.
  • Prerequisites — what you need to have set up first.
  • Setup steps — the exact sequence to build the strategy.
  • Expected behavior — what live operation should look like.
  • Common mistakes — pitfalls operators make.

​
Universal prerequisites for any recipe

All four core services (TradingBot, TelegramBot, Dashboard, Database) running. SignalEditor and SignalsBot deployed and connected.See Architecture and Quickstart if you’re not there yet.
Your TradingBot connected to your exchange of choice with proper API key permissions and IP allowlist.See API Key Security and the per-venue setup guides.
BasicMode (Mode 4) on BTCUSDT for at least a month. Recipes are level-2 patterns — they assume you have intuition for how the bot behaves on a known-good configuration.
Recipes should be forward-tested on small capital ($500–$1,500) for 2 weeks before scaling up. Have this capital ready before authoring.
Recipes are SignalEditor strategies. The SignalEditor must be running for them to evaluate; the SignalsBot must be running for the resulting signals to update configuration.

​
When to skip recipes entirely

Recipes are not for everyone. If you’re new to unCoded, start with modes — don’t reach for recipes until:
  • You have 1+ month of mode operation under your belt.
  • You understand the buy/sell ladder concepts.
  • You’ve watched your TradingBot handle real-world events (drawdowns, network blips, exchange outages).
Building a custom strategy without this foundation is reaching for the advanced toolset before you’ve mastered the basics. The pre-built modes work well for the vast majority of operators — most never need recipes.

​
What’s next

RSI Mean-Reversion

The textbook starter recipe.

EMA Cross Trend

The classic trend-follower recipe.

Multi-Timeframe

Composition pattern across timeframes.

TradingView Webhook

External charting integration.

SignalEditor

The module where you author recipes.

Modes

The 9 pre-built strategies — start here if you skipped recipes.
Last modified on May 3, 2026