I've been tinkering with my own version of this idea off and on for months, and it's great to see someone finally make the thing that I've been wanting since LLMs hit the scene. Congrats on everything you've shipped!
IMO rails is a victim of it's own success. By being incredibly productive and easy to get things up and running, you don't have to reason about your data design as much, meaning you are more likely (not guaranteed) to throw together a bunch of badly related garbage.
People love to blame the language and the framework, but in reality once you're past the proof of viability point, it's usually worth taking the time to review some of those initial decisions... except now you need to GrOw! :)
The fact that it's rails is irrelevant. It could be any tool that makes you really efficient by never erecting guard rails.
Another pro-tip in this vein is `object.methods` to see a list of the methods to which the object you're messing with will respond. I use this all of the time when I'm diving into something trying to figure out what's going on.