There are many cases, just for example, where your power-names wouldn't work as you like. One is with mixed-level CMOS. Most CMOS has no Vcc, (that's the collector voltage, and it has no collectors) but, rather is labelled Vdd. That voltage can range between about 3 volts and 15 volts without offending the logic standard CMOS logic. The TTL-workalike families, however, seem to use Vcc, since they work at voltages similar to TTL.

My own library, which I use for modified symbols, and for new parts that were released after DOS-OrCAD was no longer supported, is pretty large. However, because of the extremely compact format of these libraries, they take up less space than one might guess, so having all parts of every kind in memory is not at all unrealistic. I once though it better to keep them on disk, but that was not necessary. There are about 10 million parts in my total libraries, and they all fit readily in about 10% of all available memory. While Windows app's take their own sweet time about searching for things, this software, unencumbered by Windows nonsense, does not. Even back in the old days of 16 MHz '386SX CPU's and 16 MB of RAM, it had the component symbol on the screen before my finger was off the <enter> key.

Your method of assigning a suffix reflecting the supply voltage looks like a good one.

My setup has evolved over the years, but I've had to support Vdd, Vcc, Vbb, Vss, Vee, Vtt, and others and, in order to maintain readability as well as consistency with the datasheets, I simply try to label the supplies as I have to. Sometimes it means Vdd1, Vdd2, etc, just as separate ground planes can mean GND, Gnd1, Gnd2, Vss1, Vss2, etc. I guess it's the burden of using the same tools for 20+ years. It does make for real consistency, though.

RE