Looking up kind numbers / tag letters is probably around 0.1% of development time. And you need a dependency for that, that has to be maintained, and version bumped a lot. A lot of us don't want to do that. Just creating an enum for yourself for the kinds you use is probably the most productive for devs with bad memory. But you can create that enum yourself for kinds and publish for everyone out there to use. If it's needed by many, it will be used. But expect some conflicts if the same kind is used by different apps. It's also a vector for supply chain attack, not to mention the case when the maintainer of the enum package goes on holiday and somebody wants to release sthg. For tags, it's even more complicated because tags semantics is different for each kind.