The Indicator Lab

Describe the indicator. Watch it get built. Review its preview and verification report.

You have a dozen indicators on your chart and you trust none of them. Type the one you want in plain English. The Lab drafts it with AI, runs it on real futures data, and reports the checks and known gaps for the sample it tested. Included with your Taking Prophets membership.

Your Discord role is your login. The Lab opens with an active Taking Prophets membership.

indicator lab — build consoleNQ · 5m
you ›First FVG after the open.
  1. Consulting Pine v6 reference
  2. Checking the TP playbook — FVG definition
  3. Drafting indicator
  4. Running on real NQ futures data
  5. Tracing logic bar by bar
  6. Reviewing rendered chart
  7. Repaint check — replay test

Scripted build demonstration. Timings and results are illustrative.

sample checks passedbuilt in 6 steps · 9 verification checks · 74s

lab › On your chart. Keep talking to revise — every change re-verifies.

The Indicator Lab: start from an idea in plain English, or fork indicators other members built

The Lab itself. Start from an idea, or fork what other members already built.

Custom Pine development takes iteration. And you still had to trust it.

The old way

A custom indicator needs implementation and review. When it finally lands on your chart, you are left trusting that it compiles, that the sessions are right, and that it isn't quietly repainting history.

The Lab

The Lab cuts that to minutes. And it doesn't ask for your trust. It shows receipts.

How it works. Four steps, then keep talking.

  1. Say what you want.

    Type it like you'd say it in the server. "First FVG after the open." "Mark breakers on the 5." Or tap a starter and go.

  2. Watch it work.

    The AI builds like an engineer, in the open. It reads the Pine v6 reference. It checks the Taking Prophets playbook. It drafts, runs the script on real NQ futures data, traces the logic bar by bar, looks at its own rendered chart, and runs a repaint check.

  3. It lands on a live chart.

    Real CME futures data, NQ, ES or BTC on the 1m, 5m or 15m, with a receipt:

    Illustrative receipt: completed checks and known gaps vary by build
  4. Then just keep talking.

    "Dim the boxes after mitigation." "Add alerts." "Add SMT vs ES." Every revision goes back through verification before it hits your chart. Tweak inputs live from the settings. No rebuild needed.

The Lab mid-build: a plain English request on the left, the build queued, a live NQ one minute chart on the right

Every result has a verification status. Anyone can bolt a chat window onto an AI and spit out Pine Script. The Lab runs every build before you see it.

pine-sim

It executes. It doesn't just generate.

Our interpreter supports a documented subset of Pine. Builds run compile and runtime checks on bounded samples. Unsupported language features and missing coverage must be reviewed in the result.

replay-test

Repaint checks with stated limits.

Static checks and bounded causal replay comparisons look for future dependence in supported plots and drawings. Lawful drawing updates are allowed. Passing the tested windows is not a universal non-repainting guarantee; partial or skipped coverage is reported.

tv-parity

Check the export on TradingView.

Our local compiler catches supported Pine errors. TradingView uses a separate engine, so compile and inspect your exported script there before relying on it.

vision-review

It has eyes.

Before shipping, the AI screenshots its own rendered chart and grades it against the house cleanliness rubric: overlap, occlusion, color discipline. Signal-style indicators ship alert-ready.

It already speaks ICT. Your words mean what they mean in the server.

Ask a generic AI to "mark breakers" and you get whatever the internet taught it. The Lab is pinned to the Taking Prophets canon, distilled from the published TP indicators, with killzones on exact ET windows.

FVGiFVGOrder blocksBreakersBPRSweepsKillzonesSilver bulletOTESMTCISDMSSPD ArraysRejection BlocksCRT

Build it once. Keep it everywhere. Then take it to the Proving Ground.

Everything you build saves to your library and syncs across devices. When you make something worth showing off, one tap publishes it to the community gallery. The chart posts to Discord on its own and gets a public share page with your chart as the card.

Published indicators show previews only. Nobody can lift your code.

The Lab invents it. The Proving Ground proves it. Your exact build, loaded onto a bar by bar CME futures replay, run against real prop firm rules before you ever risk a funded account. Same engine, same membership.

The community library inside the Lab: top builds, a community leader, and preview buttons

What it costs. The Lab comes with the membership you already pay for.

Included with membership
Membership

See current pricing and terms

  • The Lab is a paid membership benefit. Your member role in Discord is your login.
  • Every membership includes $20 of build usage every month.
  • Running your indicators on the Lab chart never uses build usage.
Get the membership →
Build top-ups
$20 / $50 / $200
  • Burn through your included usage? Top up and keep building.
  • $50 adds +10% bonus credit.
  • $200 adds +20%.
Own your code
$100 one-time
  • Want your indicator on your own TradingView account? $100 gets you the raw .pine source of your own build.
  • Licensed to you, with a TradingView setup walkthrough.
  • Covers every future revision of that indicator.

Inspect each preview, its verification coverage and known gaps before using the result. Build time depends on the request.

Questions, answered.

Do I need to know Pine Script?

No. You describe what you want in plain English. If you do know Pine, you can get specific. The Lab keeps up.

Does it repaint?

Read the build’s actual verification coverage. Bounded replay checks can detect supported forms of future dependence, but do not guarantee all data, settings or TradingView behavior.

Will it work when I paste it into TradingView?

The export includes Pine source and setup guidance. Compile and test it on TradingView; the two engines have documented differences and supported-feature limits.

Can someone copy my indicator?

No. The gallery shows chart previews only, and every published build carries a structural fingerprint. Your code stays yours.

What markets and timeframes?

ES, NQ, YM, GC, SI and their micros, from one-second bars up to daily. Real CME futures data, not synthetic candles.

What happens if I run out of included usage?

Running your saved indicators on the Lab chart never uses build usage. Top-ups only gate new builds and revisions.

The indicator you've been sketching in your head is about a minute away.

Log in, type it, and watch it get built and verified. Not a member yet? The membership is the login.