I also came to the same solution a few years ago. I have a single datamodule responsible for visual settings which includes a SkinController, a set of required skins and skin support units - like dxSkinsdxBarPainter, dxSkinscxPCPainter etc - in the "uses" section and some other components and procedures (like DX string resources localization, skin switching etc.) This approach makes it extremly easy to customize an application without, well, polluting the "uses" section of all forms with skin-related modules.