It's not just you. If I write out the markup and css in a single session, I find I can keep it relatively organised and clean. Going back to code from ~6 months ago and making changes, however, is a different story.
I tend to format my css with indentations - something a lot of people don't do. I also try and be as minimal with my css declarations as possible, use short-hand, etc. There are definitely a lot of different ways to format css, just try and find a style that suits you.
You are a genius - why am I not doing this?
I really want to be able to do:
#id
{
/*some styles*/
.class
{
/*some more styles*/
}
}
without any javascript parsers - dunno why it wasn't part of the original spec.
The only issue that I can think with that is being able to distinguish between #id.class and #id .class which could have been cleared up with a double dot or something. It would have made CSS so much better.
It wasn't actually the structure of the CSS file that I was referring to but the use of the classes within the project - I always tend to use too many classes. Each unique element pretty much has its own class. I also tend to set something like float:left; on .setting div. As 60% of the divs float left but then have to add .no-float to all the other ones and it just ends up being messy.
I suck at logically using classes to maximise code reuse.