chore(project): add issue templates

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,136 @@
+---
+name: "🐛 Bug Report"
+description: Report a bug
+title: "(plugin name): (short issue description)"
+labels: [bug, needs-triage]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to fill out this bug report!
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: What is the problem? A clear and concise description of the bug.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: |
+        What did you expect to happen?
+    validations:
+      required: true
+  - type: textarea
+    id: current
+    attributes:
+      label: Current Behavior
+      description: |
+        What actually happened?
+
+        Please include full errors, uncaught exceptions, stack traces, and relevant logs.
+        If service responses are relevant, please include wire logs.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction Steps
+      description: |
+        Provide a self-contained, concise snippet of code that can be used to reproduce the issue.
+        For more complex issues provide a repo with the smallest sample that reproduces the bug.
+
+        Avoid including business logic or unrelated code, it makes diagnosis more difficult.
+        The code sample should be an SSCCE. See http://sscce.org/ for details. In short, please provide a code sample that we can copy/paste, run and reproduce.
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Possible Solution
+      description: |
+        Suggest a fix/reason for the bug
+    validations:
+      required: false
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Information/Context
+      description: |
+        Anything else that might be relevant for troubleshooting this bug. Providing context helps us come up with a solution that is most useful in the real world.
+    validations:
+      required: false
+
+  - type: input
+    id: plugin-version
+    attributes:
+      label: Plugin Version
+    validations:
+      required: true
+
+  - type: input
+    id: marketplace-version
+    attributes:
+      label: Marketplace Version
+    validations:
+      required: true
+
+  - type: input
+    id: ai-assistant
+    attributes:
+      label: AI Assistant
+      description: E.g. Claude Code | Cursor
+    validations:
+      required: true
+
+  - type: input
+    id: ai-assistant-version
+    attributes:
+      label: AI Assistant Version
+      description: E.g. Claude Code (3.8.3) | Cursor (1.0.0)
+    validations:
+      required: true
+
+  - type: input
+    id: operating-system
+    attributes:
+      label: OS
+    validations:
+      required: true
+
+  - type: input
+    id: region
+    attributes:
+      label: Region experiencing the issue
+      description: For instance, us-east-1
+    validations:
+      required: true
+
+  - type: textarea
+    id: modified
+    attributes:
+      label: Code modification
+      description: |
+        Was the solution modified from the version published on this repository? If the answer to the previous question was yes, are the changes available on GitHub?
+    validations:
+      required: true
+
+  - type: textarea
+    id: other
+    attributes:
+      label: Other information
+      description: |
+        e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, slack, etc
+    validations:
+      required: false
+
+  - type: checkboxes
+    attributes:
+      label: Service quota
+      description: Have you checked your [service quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) for the services this sample uses?
+      options:
+        - label: I have reviewed the service quotas for this construct
+          required: true

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,27 @@
+---
+name: "📕 Documentation Issue"
+description: Report an issue in the documentation or Developer Guide
+title: "(plugin name): (short issue description)"
+labels: [documentation, needs-triage]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to fill out this documentation issue!
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the issue
+      description: A clear and concise description of the issue.
+    validations:
+      required: true
+
+  - type: textarea
+    id: links
+    attributes:
+      label: Links
+      description: |
+        Include links to affected documentation page(s).
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,51 @@
+---
+name: 🚀 Feature Request
+description: Suggest an idea for this project
+title: "(plugin name): (short issue description)"
+labels: [feature-request, needs-triage]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to fill out this feature request!
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the feature
+      description: A clear and concise description of the feature you are proposing.
+    validations:
+      required: true
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: |
+        Why do you need this feature? For example: "I'm always frustrated when..."
+    validations:
+        required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: |
+        Suggest how to implement the addition or change. Please include prototype/workaround/sketch/reference implementation.
+    validations:
+      required: false
+  - type: textarea
+    id: other
+    attributes:
+      label: Other Information
+      description: |
+        Any alternative solutions or features you considered, a more detailed explanation, stack traces, related issues, links for context, etc.
+    validations:
+      required: false
+  - type: checkboxes
+    id: ack
+    attributes:
+      label: Acknowledgements
+      options:
+        - label: I may be able to implement this feature request
+          required: false
+        - label: This feature might incur a breaking change
+          required: false

.github/ISSUE_TEMPLATE/rfc.yml

@@ -0,0 +1,77 @@
+name: 🚧 Request for Comments (RFC)
+description: Feature design and detailed proposals
+title: "RFC: TITLE"
+labels: ["RFC-proposal", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for submitting a RFC. Please add as many details as possible to help further enrich this design.
+  - type: input
+    id: relation
+    attributes:
+      label: Is this related to an existing feature request or issue?
+      description: Please share a link, if applicable
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Please provide an overview in one or two paragraphs
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Use case
+      description: Please share the use case and motivation behind this proposal
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: Please explain the design in detail, so anyone familiar with the project could implement it
+      placeholder: What the user experience looks like before and after this design?
+    validations:
+      required: true
+  - type: textarea
+    id: scope
+    attributes:
+      label: Out of scope
+      description: Please explain what should be considered out of scope in your proposal
+    validations:
+      required: true
+  - type: textarea
+    id: challenges
+    attributes:
+      label: Potential challenges
+      description: Nothing is perfect. Please share what common challenges, edge cases, unresolved areas, and suggestions on how to mitigate them
+    validations:
+      required: true
+  - type: textarea
+    id: integrations
+    attributes:
+      label: Dependencies and Integrations
+      description: If applicable, please share whether this feature has additional dependencies, and how it might integrate with other utilities available
+    validations:
+      required: false
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternative solutions
+      description: Please describe what alternative solutions to this use case, if any
+      render: markdown
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        ---
+
+        **Disclaimer**: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
+
+        Metadata information for admin purposes, please leave them empty.
+
+        * RFC PR:
+        * Approved by: ''
+        * Reviewed by: ''