(apologies for my English)

I manage to create my own indicator and strategy from scratch without a single knowledge of coding or whatsoever.

I recommend to download any possible information about ACSIL from Sierra Chart and paid both subscriptions for ChatGpt and Claude Sonnet.

ChatGpt has nearly no limitations about uploading EXTENSIVE pdf files. And Claude Sonnet is better at coding.

I use ChatGpt o3 mini for reasoning what i want and o4 mini for coding with the sierra chart code plugin and upload ALL the documentation at once (you CAN'T do that with Claude Sonnet).

When I have the heavy part of the code with chatgpt i will use Claude Sonnet to fine tune it.

ALWAYS, ALWAYS use the option under Build ---> Build With Visual C++ - Debug

This will indicate the error in the code (believe me, you will have tons) you only have to paste what Sierra Chart Debug is telling you on the IA, and the Ia will solve the issue.

It is not the holy grail, lots of trial an error.. but believe me, is more cheaper than a coder and more EASY to do than learning coding. It took me like a month starting 9:00 am and finishing when my back hurts... at night.. very late.

But the satisfaction you experience when finish is nearly orgasmic.

Tin44 

(apologies for my English) I manage to create my own indicator and strategy from scratch without a single knowledge of coding or whatsoever. I recommend to download any possible information about ACSIL from Sierra Chart and paid both subscriptions for ChatGpt and Claude Sonnet.

@Tin44,

Brilliant approach using AI for ACSIL development! Your workflow (ChatGPT for docs, Claude for coding) is exactly what I recommend. Let me add some battle-tested tips:

AI Coding Power Tips:

1. Context is King - Feed the AI your exact error messages AND surrounding code. Don't just say "it crashes" - paste the full Debug output.

2. Iterative Refinement - Start with basic functionality, then layer complexity. "Make a simple MA cross" → "Add volume filter" → "Add time filter"

3. ACSIL Gotchas AI Struggles With:
- Array indexing (sc.Index vs sc.ArraySize)
- Persistent variables between bars
- Study subgraph initialization

Pro Workflow Enhancement:
Create a "context file" with:
- Your exact SC version
- Common ACSIL patterns you use
- Your naming conventions
Feed this to AI first - dramatically improves accuracy.

Debug Like a Pro:
Instead of just Build→Debug, add SCString debug messages:

 

Code

sc.AddMessageToLog("Variable X = " + SCString(myVariable), 0);

This shows exactly where code fails.

Anyone else using AI for indicator development? What's your success rate?

-- Fi
"There is no spoon. Then you'll see that it is not the spoon that bends, it is only yourself."