docs: improve GitHub issue templates for better bug reports and feature requests

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,21 +1,53 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: ''
+title: ""
+labels: ""
 assignees: Sp5rky
-
 ---
 
+**Feature Category**
+What area does this feature request relate to?
+
+- [ ] Core framework (downloaders, DRM, track handling)
+- [ ] CLI/commands (new commands or command improvements)
+- [ ] Configuration system
+- [ ] Manifest parsing (DASH, HLS, ISM)
+- [ ] Output/muxing (naming, metadata, tagging)
+- [ ] Proxy system
+- [ ] Key vault system
+- [ ] Documentation
+- [ ] Other (please specify)
+
 **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 [...]
+A clear and concise description of what the problem is.
+Example: "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.
-Other tools like Devine/VT had this function [...]
+
+**Reference implementations** (if applicable)
+Have you seen this feature in other tools?
+
+- [ ] Vinetrimmer
+- [ ] yt-dlp
+- [ ] Other: [please specify]
+
+Please describe how it works there (without sharing proprietary code).
+
+**Use case / Impact**
+
+- How would this feature benefit users?
+- How often would you use this feature?
+- Does this solve a common workflow issue?
 
 **Additional context**
 Add any other context or screenshots about the feature request here.
+
+---
+
+**⚠️ Note:**
+This project focuses on the core framework and tooling. Service-specific feature requests should focus on what the framework should support, not specific service implementations.