chore: Update GitHub issue templates for the project (#11)

* feat: Add issue templates

* Update ISSUE-TEMPLATE

* docs: add refactor request issue template

Author: Bli-AIk

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,74 @@
+---
+name: Bug report
+about: "Report a bug or unexpected behavior in a C# adapter / bridge library"
+title: 'bug: [Short description]'
+labels: bug
+assignees: ''
+---
+
+### 🐛 Problem Description
+Provide a clear description of the issue. Include:
+- Library name and version (NuGet package, project, or local reference)
+- Library type / context: Core bridge / Engine integration / Runtime only / Editor only
+- Engine name & version (e.g., Unity 2021.3.45f1, Godot 4.3)
+- Type of issue: compile-time / runtime / unexpected behavior
+- Short code snippet showing the context (optional, but helpful)
+
+---
+
+### 📝 Steps to Reproduce
+Provide a minimal, self-contained example:
+
+```csharp
+// Minimal reproducible example
+using MyLibrary;
+
+class Program
+{
+    static void Main()
+    {
+        var obj = new Foo();
+        obj.Bar(null); // Example of problematic call
+    }
+}
+````
+
+1. Which **class** and **method** did you call? What **parameters** did you pass?
+2. Engine-specific context: Editor mode / Play mode / Target platform / Scripting backend
+3. Operating system and .NET runtime version (e.g., Windows 11, .NET 8.0)
+4. How did you **install** and **reference** the library? (NuGet, version number, local reference, etc.)
+5. If applicable, include steps to reproduce in the Editor (scene setup, prefab configuration, etc.)
+
+---
+
+### ✅ Expected Result
+
+Describe what the correct behavior should be.
+Example:
+
+* Method `Bar` should return a non-null string.
+* No exception should be thrown.
+
+---
+
+### 📄 Actual Result / Logs
+
+Include any errors, stack traces, or console output:
+
+```text
+System.NullReferenceException: Object reference not set to an instance of an object.
+   at MyLibrary.Foo.Bar(String input) in Foo.cs:line 42
+```
+
+* Attach Editor log / Player log if available.
+* Include screenshots of errors in Editor if relevant.
+
+---
+
+### ⚙ Additional Information
+
+* Does the issue occur in Update / FixedUpdate / Coroutine / Async callback?
+* Is the library used in a multi-threaded environment?
+* Are there other libraries that might conflict?
+* Does the issue appear on specific hardware or OS versions?
+* Any workarounds tried?

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,42 @@
+---
+name: Feature request
+about: "Suggest a new feature or improvement for the C# adapter / bridge library"
+title: 'feat: [Brief description of the feature]'
+labels: enhancement
+assignees: ''
+---
+
+### 🔗 Is your feature request related to a specific issue?
+Please briefly describe the origin of this feature request. For example:  
+- The library is missing [specific feature], which causes [specific problem]  
+- You want to make certain scenarios easier by achieving [desired effect]
+
+---
+
+### 💡 Feature Description
+Explain in detail the feature you want to add or improve, including:  
+- Expected outcome or effect  
+- Specific implementation ideas, such as classes, methods, parameters, or API design  
+- Usage scenarios or benefits
+- Engine-specific context: Editor mode / Play mode / Target platform / Scripting backend
+- Engine name & version (e.g., Unity 2023.1.2f1, Godot 4.3)
+
+Example:  
+- Add `Foo.BarAsync()` method to allow asynchronous processing without blocking the main thread  
+- The goal is to improve performance and support multi-threaded or coroutine-based environments
+
+---
+
+### ⚖ Alternatives Considered
+List other approaches you tried or considered, and explain why they are not ideal or feasible.  
+
+Example:  
+- Tried using an extension method `FooExtensions` for async, but encountered state management issues  
+- Existing approach only supports single-threaded scenarios and does not meet the requirements
+
+---
+
+### 📝 Additional Information
+Provide any extra background, design sketches, or code snippets to help developers better understand your idea.  
+- If it involves other game engines, you can attach editor screenshots, diagrams, or example scenes  
+- Include example usage, pseudocode, or small scripts attached to GameObjects if relevant

.github/ISSUE_TEMPLATE/refactor-request.md

@@ -0,0 +1,40 @@
+---
+name: Refactor request
+about: Suggest improvements to the project's code structure or design
+title: 'refactor: [Brief description of the refactoring]'
+labels: refactor
+assignees: ''
+
+---
+
+### 🧐 Why is this refactoring necessary?
+Describe the reason for this refactoring, such as:
+- Improving code readability, maintainability, or performance of the C# adapter/bridge library.
+- Reducing technical debt or complexity.
+- Adhering to new design principles or best practices for the library.
+- Addressing a recurring issue or pattern identified from bug reports.
+
+---
+
+### 💡 Proposed Refactoring
+Explain in detail the proposed changes to the C# adapter/bridge library, including:
+- A high-level overview of the proposed refactoring.
+- Specific classes, methods, or components to be refactored (e.g., `MyLibrary.Core.Bridge`, `Foo.Bar()`).
+- The expected outcome or benefit (e.g., better performance, easier to test, improved API design).
+- Engine-specific context: Editor mode / Play mode / Target platform / Scripting backend.
+
+---
+
+### ⚖ Alternatives Considered
+List any other approaches or refactoring strategies you considered and explain why the proposed one is the best fit for the C# adapter/bridge library.
+
+Example:
+- Tried a different memory management approach, but it introduced more overhead.
+- Existing single-threaded implementation does not scale well in multi-threaded environments.
+
+---
+
+### 📝 Additional Information
+Provide any extra context, design sketches, or code snippets that would help explain the refactoring idea. This could include before-and-after examples or diagrams specific to the C# adapter/bridge library.
+- Include example usage, pseudocode, or small scripts.
+- Attach screenshots or diagrams if the refactoring involves editor integration or specific game engine scenarios.