Menu
Write clear, actionable bug reports with reproduction steps and severity assessment. Trigger with "report a bug", "write a bug report", "found an issue with [feature]", or "something is broken in [area]".
Basé sur la classification professionnelle SOC
Review architectural decisions and design patterns for scalability and maintainability. Trigger with "review the architecture", "is this design scalable", "architecture feedback", or "design review".
Review code for correctness, maintainability, performance, and security. Trigger with "review this code", "check this PR", "code review", or "look at this diff".
Create community engagement strategies with discussion prompts, events, and member activities. Trigger with "engagement plan", "how to increase community activity", "discussion ideas", or "community event ideas".
Handle community conflicts and moderation decisions with empathy and consistency. Trigger with "how should I moderate this", "handle a conflict", "community guidelines", or "member issue".
Write engaging blog posts with structure, hooks, and audience-appropriate tone. Trigger with "write a blog post about [topic]", "draft an article on [topic]", "blog post idea", or "help me write about [topic]".
Transform one piece of content into multiple formats for maximum reach. Trigger with "repurpose this [content]", "turn this blog post into a thread", "make a newsletter from this", or "create a video script from this article".
| name | bug-report |
| description | Write clear, actionable bug reports with reproduction steps and severity assessment. Trigger with "report a bug", "write a bug report", "found an issue with [feature]", or "something is broken in [area]". |
Write a clear, actionable bug report.
## Bug Report
**Title**: [Clear, descriptive title]
**Severity**: Critical / High / Medium / Low
**Component**: [Feature or area affected]
**Environment**: [Browser, OS, version, etc.]
### Description
[One sentence summary of the issue]
### Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Expected Behavior
[What should happen]
### Actual Behavior
[What actually happens]
### Evidence
[Screenshot, error message, or log output]
### Notes
[Additional context, workarounds, or related issues]