A Few Clarifications (priorities, roadmap, raison d'etre, ...)

[intellectronica]

I realise I never communicated these clearly and to a broad audience, so here we go:

• Ruler was created for groups of people collaborating on the same codebase using different and incompatible AI coding tools - for example in a team or an open-source project. That remains the main purpose of the tool and how I think about roadmap decisions.
• If you're using Ruler as an individual to manage multiple tools, good for you, and I'll do what I can to keep it working for you, but I won't prioritise new features that cater specifically for this mode. I don't use Ruler that way and don't really understand why anyone would. My best recommendation to individual developers is to pick up one or two tools that work for them, learn to work with them, and configure them directly.
• Following from that, I have almost no interest in supporting any feature that isn't widely supported by multiple agents with a significant market and mind share, or at least support from a separate tool that is available widely (like Skillz).
• Also following from that is that stability is much more important than new fancy features - there are actual teams relying on Ruler for real work - failing them in order to satisfy the needs of individual developers chasing the latest feature (myself included) is never an option.
• Ruler is a workaround for an industry failure - tools all having their own config instead of a common standard. It is not supposed to be some kind of powerful toolbox for using AI coding tools. I hope Ruler becomes obsolete as a result of the industry standardising. We're half way there, with AGENTS .md, and I hope additional components like slash-commands, subagents, and skills will follow. If I still have to maintain and extend Ruler a year from now, something has gone terribly wrong.