Chore(#72): conform to dev guidelines

[andybeet]

Your commits explain the what and where you made changes in the code. Your commit messages explain why you made the commits. You do not need to reiterate this. This PR is meant to address the big picture, Why

Justification

Updated repo with dev guideline components to make collaboration efforts more streamlined

Fixes #72
closes #67

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• OtherUpdate (if none of the other choices apply)

Checklist/Reminders

Put an x in the boxes that apply

• I have updated relevant documentation? (run pkgdown::build_site() to check)
• I have created unit tests and run devtools::test() to ensure all unit tests pass locally?
• I have run devtools::check() to ensure package builds locally?
• I have followed the proposed CONTRIBUTING guideline?

Further comments

For this repo i added a specific checklist/reminder section in this PR template, since i often forget to go through these steps

Reviewer instructions:

Compare to checklist of features to add to make sure all added

Formatting

This repo contains an air.toml file that automatically formats code to a set of standards.
It is preferred that contributors and reviewers install the air formatting tool.