Pine Script Generator
AI-powered Pine Script v5 strategy and indicator generation from plain-English descriptions — describe your trading rules in natural language and receive production-ready TradingView code you can paste and deploy immediately. Every generated script includes the Quant Validator's analysis: look-ahead bias check, sample size sufficiency, overfitting risk assessment, and an overall edge validity score with specific improvement recommendations. Supports multi-timeframe indicators, complex conditional logic, and can mirror any of the 8 HMIE analytical engines in Pine Script form.
What this page covers
- How to write effective prompts that generate quality Pine Script
- How the Quant Validator catches errors before you deploy to TradingView
- How to convert Strategy Builder strategies to Pine Script
- Best practices for testing AI-generated code safely
Writing Effective Prompts
The quality of generated Pine Script is directly proportional to the specificity of your prompt. Vague prompts produce vague code; precise prompts produce production-ready code.
| Vague prompt (bad) | Specific prompt (good) |
|---|---|
| 'Make an RSI indicator' | 'Create a Pine Script v5 indicator that plots RSI(14) with overbought/oversold levels at 70/30. Color the RSI line red when above 70, green when below 30, and white otherwise. Show background shading in the overbought/oversold zones.' |
| 'Make a moving average study' | 'Create a Pine Script v5 indicator that plots the 20 EMA and 50 EMA on a 1H chart and annotates their crossovers and subsequent closes below the 20 EMA for historical study. Show visual markers only; do not place or simulate orders, calculate position size, or make a performance promise.' |
| 'Alert for volume spike' | 'Create an alert condition that fires when volume exceeds 2.0 times the 20-bar simple moving average of volume AND the close is above the open (bullish candle). The alert message should include the pair name and the volume ratio.' |
Generating Pine Script
- Choose output type
Select from three output types: Indicator (plots on chart, no order simulation), Strategy (simulates trades with P&L tracking), or Alert Condition (fires an alert when conditions are met).
- Set Pine Script version
Default is Pine Script v5 (current standard). Only change to v4 if you specifically need compatibility with an older script that uses v4 functions.
- Write your prompt
Be specific about: indicators used and their parameters, conditions for entry/exit/alert, visual elements (colors, labels, plot styles), risk parameters (for strategies), and any edge cases to handle.
- Generate
Click Generate. Code streams in line-by-line within 10–20 seconds. The Quant Validator runs automatically after generation completes.
- Review the validation report
Read any warnings or errors flagged by the validator before copying to TradingView. Fix issues in place by clicking 'Regenerate with fix' on any flagged item.
- Copy to TradingView
Click 'Copy to Clipboard'. In TradingView, open the Pine Script Editor (Alt+E), paste, and click 'Add to chart'.
Quant Validator — What It Checks
| Check | Why it matters |
|---|---|
| Repainting risk | Scripts that use security() calls on the current bar, or look-ahead functions, repaint — they show different results in real-time vs historical. The validator flags all repainting-risk patterns. |
| Strategy commission | Backtests without commission settings are unrealistically profitable. The validator warns if commission is not set. |
| Barstate usage | Using barstate.isrealtime without a barstate.ishistory check causes real-time bars to behave differently than historical bars. Flagged automatically. |
| Series vs value errors | Pine Script has strict type rules between series (time-varying) and values (fixed). Incorrect usage causes runtime errors. The validator catches common patterns. |
| Missing strategy.close() | Strategies that never explicitly close positions can hold trades indefinitely in backtests. Flagged if no exit logic is found. |
| Deprecated functions | Pine v5 deprecated several v4 functions (e.g. study() → indicator()). The validator replaces deprecated calls automatically. |
Advanced Prompt Engineering
Beyond basic prompts, these techniques significantly improve the quality and specificity of generated Pine Script:
| Technique | Example | Effect |
|---|---|---|
| Specify Pine version + function list | 'Using Pine Script v5, use ta.rsi(), ta.ema(), and ta.crossover() only' | Prevents deprecated function usage; generates cleaner code |
| Define output format explicitly | 'Plot entry signals as green up-arrows on the chart. Plot exits as red down-arrows. Add a table in top-right corner showing current RSI value.' | Precise visual outputs match your expectations |
| Include edge cases | 'Handle the case where the RSI signal fires inside a kill zone and outside a kill zone differently — color code the arrows' | Generates robust conditional logic instead of basic if/else |
| Specify alert message format | 'When the alert fires, include: Pair, Timeframe, Signal (LONG/SHORT), Entry price, and RSI value in the message' | Produces webhook-ready alert messages for Telegram integration |
| Request comments in the code | 'Add a comment above every major section explaining what it does in plain English' | Produces maintainable, self-documenting code you can modify |
| Set explicit backtest parameters | 'Set commission to 0.02% per side, initial capital to $10,000, default_qty_type to percent_of_equity, default_qty_value to 1' | Generates realistic backtests that account for trading costs |
Example — Multi-Timeframe Kill Zone + RSI Alert
//@version=5
indicator("Hanzo MTF Kill Zone RSI Alert", overlay=false)
// ── Inputs ───────────────────────────────────────────────
rsiLen = input.int(14, "RSI Length", minval=2)
rsiOB = input.int(70, "RSI Overbought")
rsiOS = input.int(30, "RSI Oversold")
lnOpenH = input.int(9, "London-NY Open (UTC hour)", minval=0, maxval=23)
lnCloseH = input.int(11, "London-NY Close (UTC hour)", minval=0, maxval=23)
htfTF = input.timeframe("240", "HTF for RSI (4H default)")
// ── Kill Zone ─────────────────────────────────────────────
utcH = hour(time, "UTC")
inKillZone = utcH >= lnOpenH and utcH < lnCloseH
// ── RSI (current TF) ─────────────────────────────────────
rsiVal = ta.rsi(close, rsiLen)
// ── RSI (HTF via request.security) ───────────────────────
// NOTE: use barmerge.lookahead_off to prevent repainting
htfRsi = request.security(syminfo.tickerid, htfTF,
ta.rsi(close, rsiLen), barmerge.gaps_off, barmerge.lookahead_off)
// ── Signal Logic ─────────────────────────────────────────
longSignal = inKillZone and rsiVal < rsiOS and htfRsi < 50
shortSignal = inKillZone and rsiVal > rsiOB and htfRsi > 50
// ── Plot ─────────────────────────────────────────────────
plot(rsiVal, "RSI", color=color.white)
hline(rsiOB, "OB", color=color.red, linestyle=hline.style_dashed)
hline(rsiOS, "OS", color=color.green, linestyle=hline.style_dashed)
bgcolor(inKillZone ? color.new(color.green, 90) : na, title="Kill Zone")
plotshape(longSignal, style=shape.triangleup, location=location.bottom,
color=color.green, size=size.small, title="Long Signal")
plotshape(shortSignal, style=shape.triangledown, location=location.top,
color=color.red, size=size.small, title="Short Signal")
// ── Alerts ────────────────────────────────────────────────
alertcondition(longSignal, "Kill Zone Long",
"{{ticker}} | LONG | Kill Zone Active | RSI: " + str.tostring(math.round(rsiVal, 1)))
alertcondition(shortSignal, "Kill Zone Short",
"{{ticker}} | SHORT | Kill Zone Active | RSI: " + str.tostring(math.round(rsiVal, 1)))Example — Kill Zone Highlight Indicator
//@version=5
indicator("Hanzo Kill Zone Highlighter", overlay=true)
// ── Inputs ──────────────────────────────────────────
lnOpen = input.int(9, "London-NY Open Hour (UTC)", minval=0, maxval=23)
lnClose = input.int(11, "London-NY Close Hour (UTC)", minval=0, maxval=23)
nyOpen = input.int(12, "NY Midday Open Hour (UTC)", minval=0, maxval=23)
nyClose = input.int(14, "NY Midday Close Hour (UTC)", minval=0, maxval=23)
colLN = input.color(color.new(color.green, 85), "London-NY Color")
colNY = input.color(color.new(color.blue, 85), "NY Midday Color")
// ── Kill Zone Logic ─────────────────────────────────
utcHour = hour(time, "UTC")
isLondonNY = utcHour >= lnOpen and utcHour < lnClose
isNYMidday = utcHour >= nyOpen and utcHour < nyClose
// ── Plot ─────────────────────────────────────────────
bgcolor(isLondonNY ? colLN : na, title="London-NY Zone")
bgcolor(isNYMidday ? colNY : na, title="NY Midday Zone")Frequently asked questions
Can the Pine Script Generator create multi-timeframe (MTF) scripts?
Yes. Include 'use request.security() to fetch the 4H RSI value for use on the 1H chart' in your prompt. The generator handles the MTF call syntax correctly and the validator checks for repainting risk in the implementation.
What if the generated code produces an error in TradingView?
Copy the exact TradingView error message and paste it back into the generator with 'Fix this error in my Pine Script: [error message]'. The AI will diagnose and correct the issue in context.
Can I generate a script for alerts that send to Telegram?
Yes. TradingView's native webhook alert system can send to a Telegram bot. Prompt the generator: 'Create an alert condition for X and format the alert message as JSON with pair, direction, and price fields for a Telegram webhook.' The generator will output a properly formatted alert.message string you can paste into TradingView's alert setup.
What Pine Script version should I use?
Always default to Pine Script v5 — it is the current standard and is the only version actively maintained by TradingView. The validator automatically upgrades any deprecated v4 syntax (like study() → indicator()) in generated code. Only specify v4 if you need to modify an existing legacy script that cannot be cleanly ported.
Does generated Pine Script work on all chart types?
Generated scripts default to standard OHLCV candlestick charts. If you want compatibility with Heikin Ashi, Renko, or other chart types, specify it in your prompt. Some indicator logic (especially open-relative calculations) behaves differently on non-standard chart types — the Quant Validator flags the most common incompatibilities.
Prompt Template Library
Copy and modify these educational prompts to generate chart annotations and indicators for historical study. Replace the bracketed sections with your specific requirements; these templates do not place or simulate orders:
| Study type | Prompt template |
|---|---|
| Trend-following annotation | 'Create a Pine Script v5 indicator that plots the [20] EMA and [50] EMA on the [1H] chart and marks their crossovers for historical annotation. Also mark closes below the [20] EMA and show the [1.5]× ATR(14) and [2.5]× ATR(14) reference bands as visual study levels only. Do not place or simulate orders, calculate position size, or provide live trading instructions.' |
| Kill zone alert | 'Create a Pine Script v5 alert condition that fires when all of: (1) current hour is between [9] and [11] UTC, (2) RSI(14) is below [35] on the current timeframe, (3) the close of the HTF ([4H]) RSI is below [50]. Alert message should include: ticker, direction (LONG), current RSI, and the phrase KILL ZONE ACTIVE. Use barmerge.lookahead_off to prevent repainting.' |
| Volume spike detector | 'Create a Pine Script v5 indicator that detects volume spikes. A spike = current volume > [2.0] × SMA(volume, [20]). When a spike occurs on a bullish candle (close > open), plot a green dot below the candle. When on a bearish candle, plot a red dot above. Add a table in the top-right corner showing: current volume, 20-bar SMA volume, and the volume ratio.' |
| Multi-timeframe RSI filter | 'Create a Pine Script v5 indicator showing RSI(14) on the current timeframe AND the [4H] RSI using request.security(). Plot both lines on the same pane — current TF in white, HTF in orange. Shade background green when both RSI values are below [35] simultaneously (double oversold). Shade red when both are above [65]. Use barmerge.lookahead_off.' |
| Fibonacci auto-draw | 'Create a Pine Script v5 indicator that automatically identifies the last significant swing high and low (using [20]-bar pivot detection) and draws Fibonacci retracement levels at 0.236, 0.382, 0.5, 0.618, and 0.786. Label each level with its percentage and price. Use dashed lines. Redraw when a new swing is detected.' |