feat(community): add discussion templates and routing (#349)

Co-authored-by: sickn33 <sickn33@users.noreply.github.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,11 +1,13 @@
 ---
 name: Bug Report
-about: Create a report to help us improve the skills
+about: Report a reproducible bug in the repository, docs, tooling, or skill behavior
 title: "[BUG] "
 labels: bug
 assignees: sickn33
 ---
 
+> For setup help, troubleshooting questions, or “am I using this correctly?” discussions, please use GitHub Discussions Q&A instead of Issues.
+
 **Describe the bug**
 A clear and concise description of what the bug is.
 

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a question or get help
+    url: https://github.com/sickn33/antigravity-awesome-skills/discussions/new?category=q-a
+    about: Use Discussions Q&A for setup help, troubleshooting, and usage questions.
+  - name: Share an idea first
+    url: https://github.com/sickn33/antigravity-awesome-skills/discussions/new?category=ideas
+    about: Use Discussions Ideas for new skills, repo improvements, and early-stage proposals.
+  - name: Show what you built
+    url: https://github.com/sickn33/antigravity-awesome-skills/discussions/new?category=show-and-tell
+    about: Share custom skills, bundles, integrations, demos, and wins with the community.
+  - name: Report a security issue
+    url: https://github.com/sickn33/antigravity-awesome-skills/security/policy
+    about: Please use the security policy instead of opening a public issue for vulnerabilities.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,19 +1,24 @@
 ---
-name: Skill Request
-about: Suggest a new skill for the collection
+name: Actionable Improvement Request
+about: Request a concrete, scoped improvement once the work is clear enough for an Issue
 title: "[REQ] "
 labels: enhancement
 assignees: sickn33
 ---
 
-**Is your feature request related to a problem? Please describe.**
+> For early-stage ideas, brainstorming, and “would this be useful?” proposals, please start in GitHub Discussions Ideas. Open an Issue when the request is concrete and actionable.
+
+**What problem should this improve?**
 A clear and concise description of what the problem is. Ex: I'm always frustrated when [...]
 
-**Describe the solution you'd like**
-A description of the skill you want. What trigger should it have? What files should it effect?
+**What concrete change are you asking for?**
+A description of the skill, workflow, docs change, or repo improvement you want. What should be added or changed?
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**What does success look like?**
+Describe the expected outcome, acceptance criteria, or user-visible result.
+
+**Related discussion or prior art**
+Link any relevant discussion, similar skill, docs, issue, or external reference.
 
 **Additional context**
 Add any other context or screenshots about the feature request here.