I built a small open-source CLI called CAML-Lint that validates and explains JSON adventure / quest data used in games and simulations.

It’s meant to catch practical issues like: - duplicate IDs - broken references - unreachable content patterns - name/type mismatches (e.g. “negotiation” marked as combat)

The goal is to help tool builders and indie devs debug narrative logic without replacing Ink/Yarn/Twine, Unity, VTTs, or existing pipelines.

Repo + examples: https://github.com/<you>/caml-lint

npm: npm install -g caml-lint

Happy to answer questions or take feedback.