docs(issue-templates): add bug report and feature request templates to enhance issue tracking

Author: dgarciasquare1

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,35 @@
+---
+name: "Bug report"
+description: "Report a reproducible bug or regression."
+labels: [bug]
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Run '...'
+3. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual behavior
+
+What actually happened instead?
+
+## Environment (please complete the following information):
+
+- OS: [e.g. iOS, Android]
+- Dart/Flutter version: [e.g. 3.0.0, 2.10.0]
+- Library version: [e.g. 1.2.3]
+
+## Additional context
+
+Add any other context about the problem here. Include logs, error messages, or screenshots if possible.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: "Feature request"
+description: "Suggest an idea or enhancement for this project."
+labels: [enhancement]
+---
+
+## 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/pull_request_template.md

@@ -1,33 +1,34 @@
-# Pull Request Template
+# Pull Request
 
-## Summary
+## Description
 
-<!-- Provide a concise description of your changes. What does this PR do? -->
+Please include a summary of the change and which issue is fixed. Also include relevant motivation and context.
 
-## Motivation & Context
+Fixes # (issue)
 
-<!-- Why is this change necessary? What problem does it solve? Reference any related issues. -->
+## Type of change
 
-## Related Issues
-
-<!-- List any related issues, e.g., Fixes #123 or Closes #456. -->
-
-## Implementation Details
-
-<!-- Briefly describe your approach, design decisions, and any patterns or principles followed. -->
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+- [ ] Other (please describe):
 
 ## How Has This Been Tested?
 
-<!-- Describe the testing strategy. List manual steps, automated tests, and edge cases considered. -->
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
 
 ## Checklist
 
-- [ ] My code follows the project's code style and conventions
-- [ ] I have added/updated relevant documentation
-- [ ] I have added/updated tests to cover my changes
-- [ ] All existing and new tests pass locally
-- [ ] I have considered security and data validation aspects
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] 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
+- [ ] Any dependent changes have been merged and published in downstream modules
 
-## Notes for Reviewers
+## Additional context
 
-<!-- Add any extra context, open questions, or areas where you'd like feedback. -->
+Add any other context or screenshots about the pull request here.