You know Rene, I'm beginning to see quite an overkill of classes when it comes to managing sites and multiple skinobjects and honestly - perhaps my approach is too simplistic for some, but I've found it works a treat for me.
In my designs, generally the links are of the same size - the main differences it that they are sitting on a light or darker background.
If you use the skinobject CSS class functions it will set the look and feel for all the skinobjects on the page by default, and that's cool if you've got a single or similar colours that it works with.
But, for most of us, we like to have a few more options, but how do you keep track of it all?
Well I have two sets of classes I work with and have found even in the most complicated skins, unless there is such a variance in the colours and it might need further customisation, it works on every site I'm doing. And you know what's nice, you can copy and paste these into your new job without having to completely redo EVERY single class.
Why not do what I do and create two sets of links. LightBG & DarkBG - get them the same except for the colours obviously, and then you can tweak them to suit.
If you want me to do an example of how I've done it, I will post it here.
It makes the process of working alot simpler.. eg.. pretty obvious on what you're working on - a Light background or a dark one, so you aren't mucking around with 20 different classes just because you changed your mind.
That's my take on this. Give it a try and see if doesn't sort your class challenge. Otherwise you'll need to have a user class, a register class, a date class, a privacy class, a terms class, a copyright class, a host class, a breadcrumb class, a link class, a dotnetnuke class and that's not including any custom skinobjects you might be running. Sure it won't solve 100% of problems but for me, it's proven to be a big help and in fact, we do this on all our work.
That's one of my tips for the day!
Nina Meiers