docs: add issue/pr templates and code owners

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# These owners will be the default owners for everything in the repo.
+# They will be added as reviewers for PR related to configuration files.
+*       @cedoor @sripwoud
+
+# When someone opens a pull request that only modifies specific packages,
+# only the following users and not the default owners defined above will be
+# requested for a review.

.github/ISSUE_TEMPLATE/---bug.md

@@ -0,0 +1,34 @@
+---
+name: "\U0001F41E Bug"
+about: Create a report to help us improve
+title: ''
+labels: "bug \U0001F41B"
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Technologies (please complete the following information):**
+
+-   Node.js version
+-   NPM version
+-   Solidity version
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/---crate.md

@@ -0,0 +1,14 @@
+---
+name: "\U0001F4E6 Crate"
+about: Propose a new ZK-Kit Rust crate
+title: ''
+labels: 'feature :rocket:'
+assignees: ''
+
+---
+
+**Describe the package you'd like**
+A clear and concise description of the type of package you have in mind.
+
+**Additional context**
+Add any other context about the package here.

.github/ISSUE_TEMPLATE/---feature.md

@@ -0,0 +1,20 @@
+---
+name: "\U0001F680 Feature"
+about: Suggest an idea for ZK-Kit
+title: ''
+labels: 'feature :rocket:'
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/---refactoring.md

@@ -0,0 +1,17 @@
+---
+name: "\u267B Refactoring"
+about: Suggest any improvements for this project
+title: ''
+labels: 'refactoring :recycle:'
+assignees: ''
+
+---
+
+**Describe the improvement you're thinking about**
+A clear and concise description of what you think could improve the code.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions you've considered.
+
+**Additional context**
+Add any other context or screenshots about the improvement request here.

.github/pull_request_template.md

@@ -0,0 +1,38 @@
+<!-- Please refer to our CONTRIBUTING documentation for any questions on submitting a pull request. -->
+<!-- Provide a general summary of your changes in the Title above. -->
+
+## Description
+
+<!-- Describe your changes in detail. -->
+<!-- You may want to answer some of the following questions: -->
+<!-- What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...) -->
+<!-- What is the current behavior?** (You can also link to an open issue here) -->
+<!-- What is the new behavior (if this is a feature change)? -->
+<!-- Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?) -->
+
+## Related Issue(s)
+
+<!-- This project accepts pull requests related to open issues. -->
+<!-- If suggesting a new feature or change, please discuss it in an issue first. -->
+<!-- If fixing a bug, there should be an issue describing it with steps to reproduce. -->
+<!-- Please link to the issue(s) here -->
+
+<!-- Closes # -->
+<!-- Fixes # -->
+
+## Other information
+
+<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->
+<!-- Feel free to remove this section if you will not use it. -->
+
+## Checklist
+
+<!-- Please check if the PR fulfills these requirements. -->
+
+-   [ ] My code follows the style guidelines of this project
+-   [ ] I have performed a self-review of my code
+-   [ ] I have commented my code, particularly in hard-to-understand areas
+-   [ ] My changes generate no new warnings
+-   [ ] I have run `yarn format` and `yarn compile` without getting any errors
+-   [ ] I have added tests that prove my fix is effective or that my feature works
+-   [ ] New and existing unit tests pass locally with my changes

README.md

@@ -88,7 +88,7 @@
 ## 👥 Ways to contribute
 
 -   🔧 Work on [open issues](https://github.com/privacy-scaling-explorations/zk-kit.rust/contribute)
--   📦 Suggest new [packages](https://github.com/privacy-scaling-explorations/zk-kit.rust/issues/new?assignees=&labels=feature+%3Arocket%3A&template=---package.md&title=)
+-   📦 Suggest new [crates](https://github.com/privacy-scaling-explorations/zk-kit.rust/issues/new?assignees=&labels=feature+%3Arocket%3A&template=---crate.md&title=)
 -   🚀 Share ideas for new [features](https://github.com/privacy-scaling-explorations/zk-kit.rust/issues/new?assignees=&labels=feature+%3Arocket%3A&template=---feature.md&title=)
 -   🐛 Create a report if you find any [bugs](https://github.com/privacy-scaling-explorations/zk-kit.rust/issues/new?assignees=&labels=bug+%F0%9F%90%9B&template=---bug.md&title=) in the code