Ember: Proper way to structure Sass-Hierarchy

In bigger ember projects there is a need for a more powerfull Stylesheet-Language than just CSS. Since Sass or Less brings the power to split up style-definitions on several files, it seems to be an good idea to think about an modular approach.

My current approach based on the idea that the main-file app.scss includes one scss-file for each single ember route. To avoid that style definition for different routes (containing definitions for simliar content-elements) overriding each other, I "wrap" every template for each route in an extra-div with a class which descripes the current route.

Unfortunaly that can result in a very deep nested div-approach.

So what do you would say would be a good way to handle that?