CodeSatori
This is what happens when modules are't designed to be automatically extending in multiple template situations, but are rather hard-coded to go with a particular skin. Module templates should be free of specific styling, and use the styling of the current skin instead. If all module templates are symmetric, implementing this is no problem. However...

In Dolphin 7, for example a blog unit CSS class is called "blog_unit", and in articles module the corresponding snippet (albeit with a see more different filename) has a class called "alr-post". What to speak of using a generic CSS class (such as "module_unit" or "module_post"), they are all named individually, and don't even follow uniform naming conventions.

This is one of the areas of the code that should be reworked for a future major release, if not sooner, to make Dolphin a bit more easy to extend and customize.
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.041901111602783