diff --git a/.github/ISSUE_TEMPLATE/BUG_REPORT.md b/.github/ISSUE_TEMPLATE/BUG_REPORT.md
new file mode 100644
index 00000000..c17ef233
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/BUG_REPORT.md
@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Something is crashing or not working as intended
+
+---
+
+## Environment
+
+**App version:**  <!-- Add branch if necessary -->  
+**Device information:**
+ - SO name and version:
+ - Manufacturer:
+ - Model:
+
+## Description
+
+**Expected behavior:**
+
+**Current behavior:**
+
+## Steps to reproduce
+
+1. This
+2. Than that
+3. Then
+
+## Others <!-- if available, else delete -->  
+
+Images
+
+<details>
+  <summary>Logs</summary>
+
+<!--
+      Run your application with `flutter run --verbose` and attach all the
+      log output below between the lines with the backticks. If there is an
+      exception, please see if the error message includes enough information
+      to explain how to solve the issue.
+-->
+```
+```
+<!-- Finally, paste the output of running `flutter doctor -v` here. -->
+
+```
+```
+</details>
diff --git a/.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md b/.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md
new file mode 100644
index 00000000..b28c299a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md
@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+## Environment
+
+**App version:**
+**Device information:**
+ - SO name and version:
+ - Manufacturer:
+ - Model:
+
+## Description
+
+**What you'd like to happen:**
+
+**Alternatives you've considered:** <!-- if available, else delete -->  
+
+**Images:** <!-- if available, else delete -->  
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..fd2002a3
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,23 @@
+## Connection with issue(s)
+
+Resolve issue #???
+
+<!-- Required: this reference (one or many) will be closed upon merge. Ideally it has the acceptance criteria and designs for features or fixes related to the work in this Pull Request -->
+
+Connected to #???
+
+<!-- Optional: other issues or pull requests related to this, but merging should not close it -->
+
+## Testing and Review Notes
+
+<!-- Required: steps to take to confirm this works as expected or other guidance for code, UX, and any other reviewers -->
+
+## Screenshots or Videos
+
+<!-- Optional: to clearly demonstrate the feature or fix to help with testing and reviews -->
+
+## To Do
+
+<!-- Add “WIP” to the PR title if pushing up but not complete nor ready for review -->
+- [ ] double check the original issue to confirm it is fully satisfied
+- [ ] add testing notes and screenshots in PR description to help guide reviewers