메뉴
Use when building online communities, defining moderation policies, managing community engagement, handling crises, designing ambassador programs, or measuring community health. Covers community building frameworks, engagement tactics, forum/Discord/Slack management, user-generated content, community events, feedback loops, community-led growth, and toxicity handling.
Use when managing Laravel Forge servers, sites, deployments, SSL, databases, queue workers, scheduled jobs, security rules, and server provisioning. Covers Forge CLI, API, deployment scripts, Nginx templates, daemon management, and zero-downtime deployments.
Project-specific Ansible operations template — customize with your inventory, playbook catalog, deployment workflows, and host group details
Use when implementing or auditing accessibility features. Covers WCAG 2.1 AA/AAA compliance, ARIA roles and attributes, keyboard navigation, screen reader support, color contrast, focus management, and accessible component patterns.
Use when evaluating AI/LLM systems — benchmark design, automated evaluation pipelines, human evaluation protocols, A/B testing, hallucination detection, factuality checking, bias testing, safety evaluation (red teaming), latency/cost metrics, eval datasets, regression testing for prompts, and model comparison frameworks.
Use when building KPI frameworks, designing dashboards, analyzing marketing performance, setting up attribution models, or creating automated reports. Covers Google Analytics 4, social media analytics, funnel analysis, cohort analysis, A/B test analysis, ROI calculation, competitive benchmarking, and stakeholder reporting.
Use when designing or implementing REST APIs. Covers RESTful conventions, versioning, pagination, filtering, error handling, rate limiting, HATEOAS, OpenAPI documentation, and API security best practices.
| name | community-management |
| description | Use when building online communities, defining moderation policies, managing community engagement, handling crises, designing ambassador programs, or measuring community health. Covers community building frameworks, engagement tactics, forum/Discord/Slack management, user-generated content, community events, feedback loops, community-led growth, and toxicity handling. |
| user-invocable | true |
| allowed-tools | ["Read","Write","Edit","Grep","Glob","Bash"] |
| Stage | Size | Focus | Key Activities | Duration |
|---|---|---|---|---|
| Inception | 0-100 | Seed founding members | Personal invites, daily posts, respond to every post within 1hr | 1-3 mo |
| Establishment | 100-1K | Build habits and culture | Recurring events, nurture power users, member spotlights | 3-6 mo |
| Growth | 1K-10K | Scale without losing quality | Moderation team, self-serve resources, sub-communities | 6-12 mo |
| Maturity | 10K+ | Sustain and evolve | Member-led initiatives, governance model, strategic partnerships | Ongoing |
Risk at each stage: Inception = ghost town. Establishment = quality dilution. Growth = moderation overwhelm. Maturity = stagnation.
| Platform | Best For | Strengths | Weaknesses |
|---|---|---|---|
| Discord | Developer/gaming/tech communities | Real-time chat, bots, roles, channels | Overwhelming for non-tech users |
| Slack | Professional/B2B communities | Threaded discussions, integrations | Expensive at scale, message limits (free) |
| Circle/Discourse | Brand/course communities | Structured forums, SEO-friendly | Less real-time engagement |
| Public discussion, broad reach | Organic discovery, voting | Less brand control, toxicity risk | |
| Facebook Groups | Broad consumer audiences | Familiar UX, large user base | Algorithm-controlled visibility |
Decision framework: Choose Discord/Slack for real-time, high-engagement technical communities. Choose Circle/Discourse for async, structured knowledge-sharing. Choose Reddit for organic growth and public discourse.
WELCOME & INFO
#rules-and-guidelines
#introductions
#announcements
DISCUSSION
#general
#topic-specific-1 (e.g., #frontend, #backend, #devops)
#topic-specific-2
#off-topic
SUPPORT
#help-and-questions
#bugs-and-issues
#feature-requests
ENGAGEMENT
#showcase (member projects)
#events
#jobs-and-opportunities
MODERATION (staff-only)
#mod-log
#mod-discussion
#reports
Channel hygiene: Archive inactive channels quarterly. Pin important resources. Use slow mode (1 msg/30s) on high-traffic channels during events.
| Level | Behavior | Response | Example |
|---|---|---|---|
| 1 - Minor | Off-topic, mild spam | Gentle redirect, move post | "This fits better in #off-topic" |
| 2 - Warning | Disrespect, repeated minor | Written warning (DM) | First formal notice |
| 3 - Temp ban | Harassment, NSFW, doxxing | 24h-7d ban, log incident | Cooling-off period |
| 4 - Perm ban | Hate speech, threats, illegal | Immediate permanent ban | Zero tolerance |
| Community Size | Mod Ratio | Structure |
|---|---|---|
| < 500 | Founder + 1-2 volunteers | Informal |
| 500-5K | 1 mod per 500 members | Lead mod + team, weekly sync |
| 5K-50K | 1 mod per 1K + automod | Tiered roles, mod queue, documented policies |
| 50K+ | Paid community managers + volunteer mods | Formal program, training, SLAs |
Automod essentials: Keyword filters (slurs, spam patterns), link restrictions for new members, rate limiting, duplicate content detection, new account quarantine (e.g., 10-min wait before posting).
| Program | Frequency | Purpose | Format |
|---|---|---|---|
| Welcome thread | Daily/weekly | Onboard new members | Intro template, ice-breaker question |
| AMA (Ask Me Anything) | Monthly | Bring in experts | Scheduled Q&A with guest |
| Challenge/hackathon | Monthly/quarterly | Drive creation | Theme + deadline + prizes |
| Member spotlight | Weekly | Recognize contributors | Interview or showcase post |
| Feedback Friday | Weekly | Collect input | Structured feedback thread |
Activating lurkers: Low-barrier polls and reactions. "React with your answer" posts. Welcome DMs with a specific ask ("Share one thing you're working on").
Selection criteria: Active 3+ months, helpful to others, aligned with values, diverse representation.
Tiers:
Management: Monthly check-ins, quarterly reviews, clear expectations document, graceful off-ramp for inactive ambassadors.
| Severity | Example | Response Time | Actions |
|---|---|---|---|
| P1 Critical | Data breach, legal threat, member safety | < 1 hour | Lock channels, leadership involved, legal review |
| P2 High | Raid/brigading, viral negative content | < 4 hours | Temp lockdown, mod all-hands, public statement |
| P3 Medium | Heated debate, misinformation spreading | < 24 hours | Mod intervention, pin clarification, cool-down |
| P4 Low | Complaint thread, minor policy violation | < 48 hours | Normal moderation process |
CRISIS COMMUNICATION:
1. Acknowledge: "We're aware of [situation] and are investigating."
2. Action: "Here's what we're doing: [specific steps]."
3. Timeline: "We'll provide an update by [time]."
4. Follow-up: "Here's what happened, what we learned, and what changes we're making."
Post-crisis: Debrief within 48 hours. Document lessons learned. Update policies if gaps identified. Communicate changes to community.
Flywheel: Great community -> members create content/referrals -> attracts new users -> some become community members -> repeat.
Tactics:
Measuring CLG impact: Track signups with community referral attribution. Measure time-to-value for community members vs non-members. Compare retention rates: community participants vs general users.
| Metric | Formula | Healthy Range | Frequency |
|---|---|---|---|
| DAU/MAU ratio | Daily active / Monthly active | 15-30% | Weekly |
| Post-to-member ratio | Posts per week / Total members | 5-15% | Weekly |
| Response time | Avg time to first reply | < 4 hours | Daily |
| Resolution rate | Questions answered / Questions asked | > 80% | Weekly |
| New member activation | New members who post in first 7 days | > 30% | Weekly |
| Churn rate | Members inactive 30+ days / Total | < 20%/month | Monthly |
| Sentiment score | Positive posts / Total posts | > 70% positive | Monthly |
| Escalation rate | Mod actions / Total posts | < 2% | Weekly |
COMMUNITY HEALTH SCORECARD
Period: [Date range]
Engagement: [DAU/MAU] [trend] | Growth: [Net new members] [trend]
Activity: [Posts/week] [trend] | Quality: [Resolution rate] [trend]
Sentiment: [Score] [trend] | Churn: [Rate] [trend]
Red flags: [Any metric trending in wrong direction for 2+ periods]
Actions: [Specific interventions for underperforming metrics]
Collection methods: In-community polls, quarterly surveys (NPS + open-ended), feature request voting boards, exit interviews for churned members, sentiment analysis on posts.
Processing: Categorize feedback (product, community, content, support). Prioritize by frequency and impact. Close the loop publicly ("You asked for X, we built X").
Cadence: Weekly feedback review (community team). Monthly feedback report to product/leadership. Quarterly community survey with published results.