Create a TradingView indicator from your rules

An example prompt

Create a Pine Script v6 overlay indicator with a configurable 20-period EMA. Mark a bar when its close crosses above the EMA, but only after the bar closes. Add an alert condition for that confirmed crossover. Do not place orders or use future data.

This is an educational specification, not a tested trading system or a performance claim.

Step-by-step workflow

1. 1. Define one observable condition

   Start with a single moving average crossover. Specify the moving-average length, price source, plot location, and whether the signal waits for a closed bar. An indicator draws information; a strategy simulates orders. Choose the indicator for this example.

2. 2. Generate and review the script

   Choose PineScript in TradeScriptAI and submit the example prompt below. Check that the result declares Pine v6 and uses indicator(), exposes the EMA length as an input, and checks bar confirmation before showing the signal. Ask for corrections if any rule is missing.

3. 3. Open the code in TradingView

   Open a chart and its Pine Editor. Create a new indicator, replace the template with the complete exported source, save it, and select Add to chart. If compilation fails, copy the exact error and line number back into your TradeScriptAI conversation.

4. 4. Check the plotted result

   Compare the EMA and crossover marks against a few closed candles. Change the input length and inspect another timeframe. The current candle can change while it forms, so confirm that no signal appears before its close.

5. 5. Configure and test alerts

   Create an alert from the indicator's named condition and use a bar-close frequency. Confirm that the event corresponds to a visible crossover. An alert does not by itself place a brokerage order.

Check the result against your rules

• The EMA uses the selected length and price source.
• The crossover mark appears on the intended closed bar.
• No future-looking values or negative plot offsets are introduced.
• Changing symbol or timeframe does not break the indicator.

When something does not work

If signals seem to move, review bar confirmation and any higher-timeframe data requests. If there are no signals, inspect whether the chart actually contains a crossover. Include the symbol, timeframe, and expected candle when asking for a revision.

What validation tells you

Pine code can be checked through the TradingView compiler integration. Read the returned validation status, then compile and inspect the script in your own TradingView chart. A compiler check does not establish that signals are profitable or free from repainting.