Describe the strategy the way you would explain it to a colleague. The Script Builder writes Pine Script v6 with your SignalForge alerts already embedded, validates the result against a local checker, and self-corrects before handing you the code.
Three modes: a guided wizard, free chat, and improve my existing script. Every output is Pine Script v6 built for SignalForge (the JSON webhook alerts are embedded for you), validated before delivery against a local checker with a whitelist of 616 official v6 functions, and re-prompted automatically if the first draft fails. A RAG layer grounds it in the official v6 documentation so it does not invent functions.
It is not a profitability oracle. It writes syntactically valid, SignalForge-compatible Pine; whether the strategy makes money is your backtest and your risk. The companion backtester in the same TOOLS tab helps you check before you commit an evaluation account.
No. You describe entries, exits, filters and risk in plain language (English or Spanish), and the builder writes the v6 script with the alert() calls already shaped for SignalForge webhooks.
Inside the customer dashboard: TOOLS, then Script Builder / Backtester. It is included with an active SignalForge subscription; the dashboard shows whether your plan includes it.
Strategies and indicators. You can also paste your existing script and ask it to adapt it: fixing deprecated v5 calls, wiring the SignalForge alerts, or adjusting inputs.
It can draft something invalid; that is why the validator exists. Every script is checked locally (whitelisted functions, balanced blocks, SignalForge contract) and the builder rewrites up to twice before showing you the result.
Start on the free trial, open TOOLS, and describe your first strategy in a sentence.
Start the free trial →