additional CSS includes?

[wolfspyre]

Would it be reasonable to extend the current blowfish behavior WRT CSS inclusion?

In ADDITION to allowing css found in custom.css to override blowfish defaults (IE: what exists currently)

to have a globbed directory where one could put singleton CSS files to have them be included?

adding @import "$cssfile"; to custom.css doesn't work, unfortunately, or this would be a non-issue.

My reason for asking this, is that I maintain several shortcodes, which each have some css requirements.
for ease of version management, it's preferential to have each shortcode's css bits in an isolated file;

This facilitates a practice of

this shortcode, and all the various odds and ends which facilitate its' implementation, may be distributed independently.

having to push them all together into one amalgamated override file is a bit clunky...
if there were a directory path ie [custom.css,css_includes/*css] that one could have multiple files consumed from, it would make it a lot easier for blowfish and other template/shortcode/component themes to cohabitate...

thoughts?