Add a local Gemfile.dev.sample
Small typo fix
Add bower support
Use sass instead of scss
Add pry gem and load it only in development mode
Add bourbon/neat/bitters support

Also use a smacss approach to scss. I'm aware of problem with using
sprockets directives and sass `@import`, but it's a nice approach
specially when developing, since we can expand, and have a better look
to each generated css.

Also, it's important to keep in mind that globals/_alls.css.scss, doesn't
produce any css output, because if it does, it is going to get repeated
in almost every stylesheet.

@see: http://blog.55minutes.com/2013/01/lightning-fast-sass-reloading-in-rails-32/
Use stylesheet_tag instead stylesheet_path

This is basically because we can make run a lot of options through
sprockets-helpers (like `expand: true` for instance).
Allow different types of options through $NANOC_ENV variable

The `_` it is because it is a little hack to make sure it gets loaded
first.
Fix issue with the debug/expand option with stylesheet_tag

While stylesheet_tag was working, and the layout was actually pointing
to different assets, the sprockets datasource wasn't creating the files.
This change attemps to create a css for every scss/sass/css file on the
sprockets assets directory that is **not** a partial.

Meanwhile, I will hardcode files inside bower_components, because
I couldn't find a way to alter the `config[:compile]`, later when the
sprockets environment is loaded.
Add guard livereload and bundler
Add server command that includes rack-livereload middleware
Add `Checks` file

+ Add environment check so it  make sure I don't accidentaly deploy
while I'm testing.