diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 0000000..c41b214
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1,15 @@
+#
+# CODEOWNERS for ProxmoxVE
+#
+
+# Order is important; the last matching pattern takes the most
+# precedence.
+
+
+# Codeowners for specific folders and files
+# Remember ending folders with /
+
+
+# Set default reviewers
+*                                                                           @community-scripts/Contributor
+
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..a344bd0
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,50 @@
+name: "🐞 Script Issue Report"
+description: Report a specific issue.
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## ⚠️ **IMPORTANT - READ FIRST**  
+        - 🔍 **Search first:** Before submitting, check if the issue has already been reported or resolved in [closed issues](https://github.com/community-scripts/ProxmoxVE-Local/issues?q=is%3Aissue+is%3Aclosed). If found, comment on that issue instead of creating a new one.  
+        Thank you for taking the time to report an issue! Please provide as much detail as possible to help us address the problem efficiently.  
+
+     
+  - type: input
+    id: guidelines
+    attributes:
+      label: ✅ Have you read and understood the above guidelines?
+      placeholder: "yes"
+    validations:
+      required: true
+
+  - type: textarea
+    id: issue_description
+    attributes:
+      label: 📝 Provide a clear and concise description of the issue.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps_to_reproduce
+    attributes:
+      label: 🔄 Steps to reproduce the issue.
+      placeholder: "e.g., Step 1: ..., Step 2: ..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: error_output
+    attributes:
+      label: ❌ Paste the full error output (if available).
+      placeholder: "Include any relevant logs or error messages."
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional_context
+    attributes:
+      label: 🖼️ Additional context (optional).
+      placeholder: "Include screenshots, code blocks (use triple backticks ```), or any other relevant information."
+    validations:
+      required: false
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 0000000..7f06527
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,33 @@
+name: "✨ Feature Request"
+description: "Suggest a new feature or enhancement."
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # ✨ **Feature Request**
+        Have an idea for a new feature? Share your thoughts below!
+
+  - type: input
+    id: feature_summary
+    attributes:
+      label: "🌟 Briefly describe the feature"
+      placeholder: "e.g., Add support for XYZ"
+    validations:
+      required: true
+
+  - type: textarea
+    id: feature_description
+    attributes:
+      label: "📝 Detailed description"
+      placeholder: "Explain the feature in detail"
+    validations:
+      required: true
+
+  - type: textarea
+    id: use_case
+    attributes:
+      label: "💡 Why is this useful?"
+      placeholder: "Describe the benefit of this feature"
+    validations:
+      required: true
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..fbd9308
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,24 @@
+<!--🛑 All Pull Requests need to made against the development branch. PRs against main will get closed. -->
+## ✍️ Description  
+
+
+
+## 🔗 Related PR / Issue  
+Link: #
+
+
+## ✅ Prerequisites  (**X** in brackets) 
+
+- [ ] **Self-review completed** – Code follows project standards.  
+- [ ] **Tested thoroughly** – Changes work as expected.  
+- [ ] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues.  
+
+## Screenshot for frontend Change
+
+---
+
+## 🛠️ Type of Change (**X** in brackets)  
+
+- [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality.  
+- [ ] ✨ **New feature** – Adds new, non-breaking functionality.  
+- [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates.