Added initial macOS scripts.

- These scripts are tailored for my setup but are meant to be an
  example for others to expand upon for their particular setup.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,16 @@
+## Expected Behavior
+<!-- Required. Describe, in detail, the behavior experienced. -->
+
+## Actual Behavior
+<!-- Required. Describe, in detail, what should be the correct behavior. -->
+
+## Steps to Recreate
+<!-- Required. List the exact steps to the reproduce errant behavior. -->
+
+0.
+
+## Environment
+<!-- Optional. What is your operating system, software version(s), etc. Delete if unused. -->
+
+## Screenshots/Screencasts
+<!-- Optional. Attach screenshots/screencasts that demo the behavior. Delete if unused. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+## Overview
+<!-- Required. Why is this important/necessary? -->
+
+## Details
+<!-- Optional. List the key features/highlights as bullet points. -->
+
+## Notes
+<!-- Optional. List additional notes/references as bullet points. Delete if unused. -->
+
+## Screenshots/Screencasts
+<!-- Optional. Provide image/video support. Delete if unused. -->

CHANGELOG.md

@@ -0,0 +1,3 @@
+# v1.0.0 (2016-10-05)
+
+- Initial version.

CODE_OF_CONDUCT.md

@@ -0,0 +1,61 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
+participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
+disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
+appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
+project or its community. Examples of representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed representative at an online or offline
+event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
+[[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in
+a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain
+confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be
+posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
+repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Overview
+
+Thanks for taking an interest in this open source project. Your support and involvement is greatly appreciated. The
+following details what you need to know in order to contribute.
+
+# Requirements
+
+- Follow these [Basic Programming Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/basic.md).
+- Follow these [Code Review Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/code_reviews.md).
+- Follow these [Git Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/git.md).
+- Follow these [Bash Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/languages/bash.md).
+- Follow these [CSS Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/languages/css.md).
+- Follow these [Ruby Styles](https://github.com/bkuhlmann/style_guides/blob/master/programming/languages/ruby/ruby.md).
+
+# Contributing Code
+
+0. Read the project README thoroughly before starting.
+0. Fork the master branch of the repository.
+0. Ensure there are no setup, usage, and/or test issues (again, follow the README).
+0. Add tests for new functionality (refactoring and documentation changes can be excluded).
+0. Ensure all tests pass.
+0. Push your feature branch and submit a pull request.
+
+# Submitting Issues
+
+0. Submit an issue via the GitHub Issues tab (assuming one does not already exist).
+0. Clearly describe the issue (including steps to reproduce).
+0. Specify your enviroment setup (OS, browser, language, etc. with version info).
+0. Provide a stack dump (if possible).
+0. Explain any additional details that might help diagnose the problem quickly.
+
+# Feedback
+
+Expect a response within one to three business days.
+Changes, alternatives, and/or improvements might be suggested upon review.

LICENSE.md

@@ -0,0 +1,20 @@
+Copyright (c) 2016 [Alchemists](https://www.alchemists.io).
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.