DocumentationResourcesBest Practices

Best Practices

A practical checklist for using Atlas Pro, Scribe Studio, and TradingView responsibly.

Trust the closed bar, not the forming one

The single highest-leverage habit in this entire doc set: act on Confirmed Signals, not on the Live Bias Marker. The Live Bias Marker is the engine's current read — it moves with the candle. Confirmed Signals are closed-bar events that stay anchored. Most "Atlas Pro looked great then lost the trade" stories begin with someone acting on a live read that never confirmed.

The Four Pillars

Atlas Pro

Start with defaults: Balanced Signal Mode, Default Dashboard, Live Bias Marker, Key Zone, Invalidation Line, Atlas Pro Oscillator.
Separate the Live Bias Marker (current chart state) from Confirmed Signals (closed-bar output).
Use the Dashboard before enabling every overlay — it often gives enough context on its own.
Turn on overlays one at a time. Learn Order Blocks, Fair Value Gaps, Structure Levels, Liquidity Levels, and Premium / Discount Zones independently before stacking them.
Use Signal Mode intentionally: Aggressive for more cadence, Conservative for selectivity, Balanced as the baseline.

Scribe Studio

Be specific. Include rules, timeframes, visuals, inputs, alerts, and risk logic in the same prompt.
Stay in the same chat when refining a script — Scribe Studio keeps conversation context inside the chat.
Paste exact TradingView error messages, not summaries. Exact errors produce better fixes.
Ask for the full updated script after every change to avoid copy/paste mistakes.
Save strategy outputs worth keeping. Do not rely on chat memory for important code.
Always test the generated script in TradingView before trusting it. Compile success is not behavior success — run it on real charts and watch how it behaves across symbols and conditions.

TradingView Workflow

Keep a clean chart while learning. Other tools can hide what Atlas Pro is showing.
Save chart layouts after configuring Atlas Pro so the setup survives a refresh.
Use Once Per Bar Close as the trigger frequency for any Atlas Pro confirmed signal alert.
Use descriptive alert names — BTCUSD 1H Atlas Confirmed beats Alert 17.
Recreate alerts after changing important script settings; old alerts hold their old configuration.

Risk-Aware Use

Treat ChartMystic as decision support, not a trading plan. Never risk capital on one marker, one prompt, or one backtest.
Define risk before the trade: position size, invalidation, exit logic, maximum loss.
Do not chase every alert. Alerts bring charts to your attention — they are not entries.
Review losing trades as seriously as winning trades. The goal is to improve your process, not to prove a tool right.

Risk management is yours

Atlas Pro and Scribe Studio organize the chart and the code. They do not size positions, set stops, or manage drawdown. Every trade decision — and every consequence — sits with you.

The Four Pillars

Atlas Pro

Start with defaults: Balanced Signal Mode, Default Dashboard, Live Bias Marker, Key Zone, Invalidation Line, Atlas Pro Oscillator.

Separate the Live Bias Marker (current chart state) from Confirmed Signals (closed-bar output).

Use the Dashboard before enabling every overlay — it often gives enough context on its own.

Turn on overlays one at a time. Learn Order Blocks, Fair Value Gaps, Structure Levels, Liquidity Levels, and Premium / Discount Zones independently before stacking them.

Use Signal Mode intentionally: Aggressive for more cadence, Conservative for selectivity, Balanced as the baseline.

Scribe Studio

Be specific. Include rules, timeframes, visuals, inputs, alerts, and risk logic in the same prompt.

Stay in the same chat when refining a script — Scribe Studio keeps conversation context inside the chat.

Paste exact TradingView error messages, not summaries. Exact errors produce better fixes.

Ask for the full updated script after every change to avoid copy/paste mistakes.

Save strategy outputs worth keeping. Do not rely on chat memory for important code.

Always test the generated script in TradingView before trusting it. Compile success is not behavior success — run it on real charts and watch how it behaves across symbols and conditions.

TradingView Workflow

Keep a clean chart while learning. Other tools can hide what Atlas Pro is showing.

Save chart layouts after configuring Atlas Pro so the setup survives a refresh.

Use Once Per Bar Close as the trigger frequency for any Atlas Pro confirmed signal alert.

Use descriptive alert names — BTCUSD 1H Atlas Confirmed beats Alert 17.

Recreate alerts after changing important script settings; old alerts hold their old configuration.

Risk-Aware Use

Treat ChartMystic as decision support, not a trading plan. Never risk capital on one marker, one prompt, or one backtest.

Define risk before the trade: position size, invalidation, exit logic, maximum loss.

Do not chase every alert. Alerts bring charts to your attention — they are not entries.

Review losing trades as seriously as winning trades. The goal is to improve your process, not to prove a tool right.

Risk management is yours

Atlas Pro and Scribe Studio organize the chart and the code. They do not size positions, set stops, or manage drawdown. Every trade decision — and every consequence — sits with you.