title: SASS project setup: mixins that depend on other mixins
body: <p>I organizing my sass (scss) files in the way outlined <a href="http://thesassway.com/beginner/how-to-structure-a-sass-project" rel="nofollow">here</a>...</p>
  
  <pre><code>stylesheets/
  |
  |-- modules/              # Common modules
  |   |-- _all.scss         # Include to get all modules
  |   |-- _utility.scss     # Module name
  |   |-- _colors.scss      # Etc...
  |   ...
  |
  |-- partials/             # Partials
  |   |-- _base.sass        # imports for all mixins + global project variables
  |   |-- _buttons.scss     # buttons
  |   |-- _figures.scss     # figures
  |   |-- _grids.scss       # grids
  |   |-- _typography.scss  # typography
  |   |-- _reset.scss       # reset
  |   ...
  |
  |-- vendor/               # CSS or Sass from other projects
  |   |-- _colorpicker.scss
  |   |-- _jquery.ui.core.scss
  |   ...
  |
  `-- main.scss            # primary Sass file
  </code></pre>
  
  <p>I understand the purpose of differentiating <strong>partials</strong> and <strong>modules</strong>: partials output css whereas modules define mixins, variables, etc that are more easily reused.</p>
  
  <p><strong>My question:</strong>
  What if I want to write a module that uses mixins from <em>another</em> module? For example, I have a module that defines a mixin for media queries. I have another module that defines a mixin for scaling typo responsively (adjusting line-height, font-size, etc). I want the latter to use my responsive mixin, but I don't want to copy/paste the first module into the second. Should I just @import the first into the second? What's the best practice for this? </p>