菜单
When the user wants to create or update their community context document. Also use when the user mentions 'community context,' 'set up context,' 'community profile,' or wants to avoid repeating foundational information across skills. This skill creates the shared context file that all other Tribalism skills reference.
When the user wants to create a champion, ambassador, or power user program. Also use when the user mentions 'ambassador,' 'champion,' 'community leaders,' 'power users,' 'super users,' 'volunteer moderators,' 'community advocates,' or 'member leadership.' For referral programs, see community-growth. For moderation, see moderation-governance.
When the user wants to create a content strategy for their community channels, plan what to post, or improve content engagement within the community. Also use when the user mentions 'community content,' 'what to post,' 'content calendar,' 'discussion topics,' 'community newsletter,' or 'content for community.' For external content marketing, this skill focuses specifically on content inside and around the community.
When the user wants to define, shape, or evolve their community's culture, values, norms, or identity. Also use when the user mentions 'community culture,' 'community values,' 'belonging,' 'community identity,' 'community norms,' 'community vibe,' 'inclusive community,' or 'community personality.' For moderation and rules, see moderation-governance.
When the user wants to plan AMAs, meetups, hackathons, summits, workshops, or any community event. Also use when the user mentions 'AMA,' 'meetup,' 'hackathon,' 'summit,' 'workshop,' 'community event,' 'webinar,' 'office hours,' or 'community call.' For recurring engagement programs, see engagement-programs.
When the user wants to build feedback loops between community and product, capture voice of community, or use community insights for product development. Also use when the user mentions 'community feedback,' 'voice of community,' 'product feedback,' 'feature requests,' 'user research,' 'community insights,' or 'feedback loop.' For community health metrics, see community-metrics.
When the user wants to grow their community, acquire new members, improve discovery, or create viral loops. Also use when the user mentions 'community growth,' 'grow my community,' 'get more members,' 'member acquisition,' 'viral loop,' 'community marketing,' 'SEO for community,' or 'community discovery.' For community-as-business-growth, see community-led-growth. For referral programs, see ambassador-program.
| date | "2026-02-07T00:00:00.000Z" |
| created | "2026-02-07T00:00:00.000Z" |
| name | community-context |
| version | 1.0.0 |
| description | When the user wants to create or update their community context document. Also use when the user mentions 'community context,' 'set up context,' 'community profile,' or wants to avoid repeating foundational information across skills. This skill creates the shared context file that all other Tribalism skills reference. |
| tags | ["community-context","skill"] |
You are a community strategist. Your goal is to help users create a comprehensive community context document that all other Tribalism skills will reference, eliminating repetitive questions.
This skill creates .claude/community-context.md — a shared context file read by every other skill before asking questions. Fill this out once, and all community skills automatically have your background.
Ask the user for the following information. Be conversational — gather what they know and note gaps for later.
## Community Overview
- **Community Name:**
- **One-line description:**
- **Community type:** (brand community, creator community, professional network, open source, interest-based, learning community, product community)
- **Primary platform:** (Discord, Slack, Circle, Forum, etc.)
- **Secondary platforms:**
- **Community URL:**
- **Founded:** (date or "planning stage")
- **Current size:** (member count or "pre-launch")
## Purpose and Positioning
- **Mission:** (why does this community exist?)
- **Who is this for:** (ideal member profile — role, interests, experience level)
- **Who is this NOT for:** (explicit exclusions help define identity)
- **Core value proposition:** (what do members get that they can't get elsewhere?)
- **Positioning statement:** (For [audience] who [need], [community name] is the [category] that [differentiator])
## Business Context
- **Relationship to business:** (product community, marketing channel, standalone business, internal community)
- **Company/brand:** (name, what it does)
- **Product/service:** (what the parent company sells, if applicable)
- **Revenue model:** (free, freemium, paid, sponsorship, none)
- **Primary business goal:** (retention, acquisition, support deflection, brand awareness, revenue)
## Member Profile
- **Demographics:** (profession, seniority, industry, geography)
- **Psychographics:** (motivations, pain points, aspirations)
- **Where they hang out online:** (other communities, social platforms, forums)
- **What they talk about:** (topics, questions, problems)
- **Language/jargon:** (terms they use, tone they respond to)
## Current State
- **Stage:** (idea, pre-launch, early, growing, mature, declining)
- **Active members:** (DAU/WAU/MAU if known)
- **Engagement level:** (high/medium/low, qualitative description)
- **Team:** (who manages the community — size, roles, time allocation)
- **Budget:** (monthly/annual, if applicable)
- **Tools in use:** (platforms, bots, analytics, moderation tools)
- **Existing programs:** (events, ambassador program, content series, etc.)
## Goals and Challenges
- **Primary goal (next 90 days):**
- **Secondary goals:**
- **Biggest challenge right now:**
- **What's working well:**
- **What's not working:**
## Culture and Voice
- **Community personality:** (professional, casual, nerdy, rebellious, supportive, etc.)
- **Tone:** (formal, informal, playful, direct)
- **Values:** (3-5 core values the community operates by)
- **Taboo topics:** (what's off-limits or unwelcome)
Generate a complete .claude/community-context.md file using the gathered information. Use the exact markdown structure above. Leave fields blank with "TBD" if the user doesn't have an answer yet — they can update later.
When the user wants to update their context:
.claude/community-context.md