Guide walkthrough
Start reading here
This is the main article body, where the page shifts from summary cards into the actual workflow and decision-making notes.
On this page
Key terms for this guide
These glossary pages cover the ideas and platform language most likely to matter as you work through this guide.
Backup before importing
Before installing custom scripts, back up templates, workspaces, and custom indicators. A few minutes of backup work can save a lot of platform cleanup later.
- Backup workspaces, templates, and custom scripts before large import sessions.
- A simple backup makes it much safer to remove conflicts if needed.
- This is especially important when testing several third-party tools.
Prefer source-readable packages
Unlocked or source-readable packages are easier to inspect, troubleshoot, and modify. Locked packages can still be legitimate, but they ask you to trust more and verify less.
- Source-readable packages are easier to verify and adapt later.
- Locked packages may still be fine, but they increase the trust burden.
- When both exist, the source-readable option is usually the better long-term workflow.
Test in simulation first
Load the indicator on a clean chart, review settings, test alerts, and watch behavior in simulation before using it in live trading.
- Simulation reveals alert spam, redraw behavior, and unwanted chart clutter quickly.
- A clean test chart shows what the tool is really doing without workspace noise.
- Even simple tools should earn trust before they touch a live workflow.
