I like this idea, but unfortunately, we don’t have the capacity to work on this front right now. However, we can recommend @wreiske’s package in the documentation for the time being.
This is a good direction, but I don’t think the focus for this narrative should be limited to Blaze. We still need to improve our documentation to cover many other APIs. In my opinion, LLMs currently struggle with Meteor apps because of incomplete documentation and a lack of real-world open-source applications to learn from.
It’s a nice idea for now, but I wouldn’t just add it to the skeleton. I’d prefer to integrate it into the Meteor CLI and make it dynamic, as it should be optional and receive updates over time. (If we were to use something like claude /init , we could avoid this issue entirely).
you can find it here
Just linking this related forum topic: How can Meteor position itself for the LLM age?