Welcome.
Start here.

No. The entire approach in this book is designed for traders, not programmers. You describe your logic in plain English, Claude translates it into Pine Script, and the videos show every step on screen. You will review code — but you will not need to write it from scratch.

Version 6 is the current standard and what all resources on this site are built with. Always include "Using Pine Script version 6" at the start of your Claude prompt. If your script was written in version 5, Claude can convert it — just paste the code and ask for a version 6 upgrade.

Check what your broker offers first — that often decides it. If both are available, MT4 is the simpler starting point for forex traders. MT5 is better if you trade multiple asset classes or your broker requires it. The MT4 vs MT5 Guide download covers this in full, including a decision tree and setup checklists for both.

This almost always means your signal condition is true across multiple bars, not just at the crossover event. In TradingView, make sure the alert is set to "Once Per Bar Close." In your Pine Script, the signal should use ta.crossover() or ta.crossunder() rather than a simple greater-than/less-than comparison. Video 6 and the Debugging Quick Reference Card cover exactly this scenario.

Yes — and this is one of the most powerful uses of Claude in this workflow. Paste the EA scaffold code into a Claude conversation, describe what you want to change (lot size logic, additional filters, notification settings), and Claude will make targeted modifications. Always test any changes on a demo account before going live.

Only after thorough demo testing. The webhook pipeline delivers real trade commands the moment an alert fires. A misconfigured EA on a live account can open unintended positions instantly. Test every link in the chain separately on a demo account — the TradingView alert, the webhook listener, and the EA execution — before enabling anything live. This point is repeated throughout the book because it matters.