It would be cool if there was a way to say publish a .cursorrules file in a NPM package and give the LLM/Agent access to this, that way you can effectively write documentation for LLMs that is automatically picked up when used.
Just curious—what’s the motivation for publishing .cursorrules to npm? Wouldn’t each project’s rules be pretty unique and tightly coupled with its architecture or implementation? In theory, general patterns are something LLMs already learn during training, so maybe the rules are better focused on what makes the project itself special?
LLMs dont do well in cases where a library was either not popular, or created after the training date of said LLM. For example LLMs struggle with Tailwind V4 configuration because it is so recent. If you could ship a .cursorrules alongside your library you could provide up-to-date context about the library and its usage even if the LLM was not trained on it.
Oh, you’re right—I forgot that LLMs have a time-sensitive dataset, so they might struggle with newer libraries or versions. 
Publishing to NPM? I added a npx command for mine to make it easy to clone and bootstrap any project GitHub - usrrname/cursorrules: A wicked npx-able lib of cursorrules with Otaku AI agents, optional lean workflow 🎀