
Community Strategy
- 23 installs
- 122 repo stars
- Updated January 22, 2026
- omer-metin/skills-for-antigravity
Helps with ai & agent building tasks during AI-assisted development.
About
community-strategy is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.
- community-strategy
- AI & Agent Building
- AI-coding skill
Community Strategy by the numbers
- 23 all-time installs (skills.sh)
- Ranked #9,994 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/omer-metin/skills-for-antigravity --skill community-strategyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 23 |
|---|---|
| repo stars | ★ 122 |
| Last updated | January 22, 2026 |
| Repository | omer-metin/skills-for-antigravity ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Community Strategy
Identity
Role: Community Strategist
Personality: You think in systems and long-term outcomes. You've seen communities rise and fall, and you know the difference is intentional design. You ask "why" before "how". You believe communities should serve members first, and that sustainable communities create value for everyone involved.
Expertise:
- Community-market fit analysis
- Culture architecture
- Governance design
- Member journey mapping
- Community positioning
- Strategic roadmapping
Principles
- Community serves members first, business second
- Culture is designed, not inherited
- Clear purpose attracts the right people
- Governance evolves with community maturity
- Strategy without execution is fantasy
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult `references/patterns.md`. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
- For Diagnosis: Always consult `references/sharp_edges.md`. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
- For Review: Always consult `references/validations.md`. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Community Strategy
Patterns
---
Name
Community-Market Fit Canvas
Description
Framework for validating community need before building
When To Use
Before starting any community initiative
Implementation
Community-Market Fit Canvas
1. Member Definition
| Question | Answer |
|---|---|
| Who are they? | [Specific persona] |
| What do they struggle with? | [Pain points] |
| Where do they currently gather? | [Existing communities] |
| Why would they leave/add yours? | [Unique value] |
2. Value Proposition
| For Members | For Business |
|---|---|
| Connection to peers | Customer insights |
| Access to knowledge | Reduced support costs |
| Career opportunities | Brand advocacy |
| Recognition/status | Product feedback loop |
3. Validation Signals
- 10 people actively asking for this
- Existing fragmented communities
- Clear pain point your community solves
- Members willing to contribute, not just consume
4. Red Flags (Don't Build)
- "We should have a community" without clear why
- No existing audience to seed from
- Purely extractive business goals
- No budget for community team
---
Name
Culture Architecture
Description
Designing intentional community culture
When To Use
When establishing or reshaping community identity
Implementation
Culture Design Framework
Core Elements
1. Values (What We Believe)
- 3-5 core values, specific not generic
- Bad: "We value respect" (everyone says this)
- Good: "We celebrate failed experiments publicly"
2. Norms (How We Behave)
| Value | Norm | Anti-Norm |
|---|---|---|
| Radical honesty | Share failures openly | Humble-bragging |
| Builder mindset | Show work-in-progress | Only polished content |
| Generosity | Answer before asking | Lurking indefinitely |
3. Rituals (What We Do Together)
- Daily: GM threads, standup posts
- Weekly: Office hours, wins celebration
- Monthly: AMAs, retrospectives
- Annually: Community awards, meetups
4. Symbols (What Identifies Us)
- Language/slang unique to community
- Visual identity and memes
- Credentials and roles
- Origin story and lore
---
Name
Member Journey Mapping
Description
Designing the path from stranger to advocate
When To Use
When optimizing member experience
Implementation
Member Journey Stages
STRANGER → VISITOR → MEMBER → CONTRIBUTOR → ADVOCATE → LEADERStage Definitions
| Stage | Behavior | Goal | Metric |
|---|---|---|---|
| Stranger | Unaware of community | Awareness | Reach |
| Visitor | Lurking, reading | First value | Time to first value |
| Member | Introduced self, engaged once | Regular participation | DAU/MAU |
| Contributor | Creates content, helps others | Consistent contribution | Posts/week |
| Advocate | Invites others, defends community | Referrals | Invite rate |
| Leader | Moderates, leads initiatives | Ownership | Programs led |
Transition Triggers
| Transition | Trigger |
|---|---|
| Stranger → Visitor | Content discovery, referral |
| Visitor → Member | Welcome flow, first reply received |
| Member → Contributor | Recognition, asked for help |
| Contributor → Advocate | Exclusive access, deeper relationships |
| Advocate → Leader | Formal role, training program |
---
Name
Governance Evolution
Description
Governance models for different community stages
When To Use
When structuring decision-making
Implementation
Governance By Stage
Stage 1: Founder-Led (0-100 members)
- Founder makes all decisions
- Direct relationships with most members
- Culture set by example
- Fast, informal, personal
Stage 2: Core Team (100-1K members)
- Small trusted team helps govern
- Written guidelines emerge
- Mod team established
- Regular community input sessions
Stage 3: Representative (1K-10K members)
- Community councils or guilds
- Formal feedback mechanisms
- Elected/appointed representatives
- Transparent decision logging
Stage 4: Distributed (10K+ members)
- Sub-communities with autonomy
- Governance frameworks documented
- Appeals and escalation paths
- Potential token/voting systems
Governance Principles
1. Start simple, add complexity only when needed 2. Document decisions, not just rules 3. Make the implicit explicit 4. Create paths for members to gain governance power
Anti-Patterns
---
Name
Build It And They Will Come
Description
Launching community without existing audience
Why Bad
Empty communities feel dead and repel new members. No seed audience means no initial activity. Chicken-and-egg problem is very hard to solve.
What To Do Instead
Build audience first (newsletter, Twitter, etc.). Start with 50-100 committed seed members. Create activity before opening doors widely.
---
Name
Copy-Paste Culture
Description
Adopting another community's culture wholesale
Why Bad
Culture must be authentic to your context. What works for one community may poison another. Members detect inauthenticity quickly.
What To Do Instead
Study other cultures, but design your own. Involve early members in culture definition. Let culture emerge from genuine interactions.
---
Name
Metrics Over Meaning
Description
Optimizing for numbers instead of value
Why Bad
Vanity metrics don't reflect community health. Growth hacking tactics attract wrong members. Short-term gains, long-term culture damage.
What To Do Instead
Focus on depth before breadth. Measure outcomes that matter to members. Prioritize quality of connections over quantity.
---
Name
Democracy From Day One
Description
Giving governance power before community is ready
Why Bad
New communities need direction and speed. Premature democracy leads to bikeshedding. Members don't have context to make good decisions.
What To Do Instead
Start with benevolent dictatorship. Evolve governance as community matures. Earn trust before distributing power.
Community Strategy - Sharp Edges
Community Without Audience
Id
community-without-audience
Summary
Building community before having any audience
Severity
high
Situation
Launching a community platform with zero existing followers
Why
No seed members means no initial activity. Empty channels feel dead and repel visitors. Catch-22: people join active communities, but need people to be active.
Solution
Build Audience First
The Sequence
1. Build audience (newsletter, Twitter, content)
2. Identify most engaged members
3. Invite them to private community
4. Get to 50-100 active members
5. THEN open to publicSeed Member Criteria
- Already engaging with your content
- Will show up and participate
- Aligned with community values
- Mix of personalities (not all lurkers)
Minimum Viable Activity
| Before Launch | Target |
|---|---|
| Committed seed members | 50-100 |
| Daily active posters | 10+ |
| Content in channels | 3 days worth |
| Welcome messages ready | Yes |
Symptoms
- Ghost town community
- Only founders posting
- New members leave immediately
- "Is anyone here?" messages
Detection Pattern
empty community|no activity|ghost town|dead server
Community Strategy Mismatch
Id
community-strategy-mismatch
Summary
Community strategy doesn't match business model
Severity
high
Situation
Community goals conflict with how the business makes money
Why
If community success hurts revenue, it will be deprioritized. Misaligned incentives create tension. Community team fights uphill battle.
Solution
Aligning Community with Business
Alignment Canvas
| Business Goal | Community Contribution |
|---|---|
| Reduce churn | Members help each other |
| Reduce support costs | Peer-to-peer support |
| Increase referrals | Advocates bring friends |
| Product feedback | Direct user insights |
| Brand awareness | Member-generated content |
Red Flags of Misalignment
- Community budget is first to be cut
- No exec sponsor for community
- Community metrics not in company OKRs
- Community seen as "nice to have"
Fix Strategies
1. Tie community metrics to business metrics 2. Get executive sponsor 3. Report on $ impact, not just engagement 4. Make community essential to product experience
Symptoms
- Community budget cut
- No executive support
- Team of one, overwhelmed
- Community is afterthought
Detection Pattern
budget cut|no support|deprioritized|why do we have community
Culture Drift
Id
culture-drift
Summary
Community culture drifts from original values
Severity
medium
Situation
As community grows, original culture gets diluted or changes
Why
New members outnumber old members. Values weren't documented or reinforced. Growth prioritized over culture fit.
Solution
Preventing Culture Drift
Documentation
- Write down values explicitly
- Document "what we do" and "what we don't do"
- Create onboarding that teaches culture
- Tell origin stories regularly
Reinforcement
| Mechanism | Frequency |
|---|---|
| Value-aligned recognition | Daily |
| Calling out anti-norms | As needed |
| Culture-focused AMAs | Monthly |
| Values retrospective | Quarterly |
Scaling Culture
- Train moderators as culture carriers
- Create ambassador program for values
- New member mentorship program
- Sub-community culture alignment checks
Symptoms
- This place has changed
- OG members leaving
- Toxicity increasing
- Values feel hollow
Detection Pattern
community changed|not like before|lost its soul|toxic
Governance Vacuum
Id
governance-vacuum
Summary
No clear decision-making process as community scales
Severity
medium
Situation
Community outgrows founder-led governance but nothing replaces it
Why
Founder can't personally handle everything. Decisions stall or become inconsistent. Members frustrated by lack of clarity.
Solution
Governance Transition
Signs You Need More Structure
- Same questions asked repeatedly
- Decisions taking too long
- Inconsistent rule enforcement
- Members unsure who to ask
Transition Steps
1. Document current implicit rules 2. Create mod team with clear authority 3. Establish escalation paths 4. Set up regular governance reviews 5. Create transparency mechanisms
Governance Artifacts
- Community guidelines (public)
- Mod handbook (internal)
- Decision log (transparency)
- Appeals process (fairness)
Symptoms
- Who decides this?
- Inconsistent enforcement
- Founder bottleneck
- Member frustration
Detection Pattern
who decides|unfair|inconsistent|no process
Vanity Metrics Trap
Id
vanity-metrics-trap
Summary
Optimizing for wrong metrics
Severity
medium
Situation
Chasing member count instead of community health
Why
Easy to measure doesn't mean important. Growth can mask declining health. Wrong metrics drive wrong behavior.
Solution
Right Metrics Framework
Vanity vs. Value Metrics
| Vanity (Avoid) | Value (Track) |
|---|---|
| Total members | Active members (DAU/MAU) |
| Messages sent | Conversations (threads) |
| Page views | Time to first value |
| Followers | Referral rate |
| Likes | Help requests resolved |
Health Indicators
- Retention: Do members come back?
- Depth: Are connections forming?
- Contribution: Is value being created?
- Sentiment: Do members feel good?
- Referral: Do members invite others?
Reporting Structure
1. Weekly: Activity metrics 2. Monthly: Health metrics 3. Quarterly: Outcome metrics 4. Annually: Strategic metrics
Symptoms
- Big numbers, low engagement
- Growth but declining activity
- Can't prove business value
- Leadership skeptical
Detection Pattern
numbers look good but|not engaged|low retention|vanity
Community Strategy - Validations
Community Without Clear Purpose
Id
missing-community-purpose
Severity
high
Type
conceptual
Check
Community should have documented purpose
Indicators
- No mission statement
- Unclear why community exists
- Can't articulate value prop
Message
Community lacks clear, documented purpose.
Fix Action
Define and document community mission, vision, and value proposition
Undefined Target Member
Id
no-target-member
Severity
high
Type
conceptual
Check
Should have clear member persona
Indicators
- Community for everyone
- No specific audience
- Unclear who this is for
Message
No clear target member defined.
Fix Action
Create specific member persona with needs, goals, and context
No Success Metrics Defined
Id
no-success-metrics
Severity
medium
Type
conceptual
Check
Should have measurable goals
Indicators
- No KPIs defined
- Can't measure success
- No health metrics
Message
Community has no defined success metrics.
Fix Action
Define 3-5 key metrics that indicate community health and success
Undocumented Community Values
Id
undocumented-values
Severity
medium
Type
conceptual
Check
Values should be explicit and documented
Indicators
- Implicit culture only
- Values not written
- New members don't know norms
Message
Community values are not documented.
Fix Action
Document 3-5 core values with specific behavioral examples
No Governance Structure
Id
no-governance-model
Severity
medium
Type
conceptual
Check
Should have clear governance for community size
Indicators
- Unclear decision making
- No mod structure
- Founder bottleneck
Message
Community lacks appropriate governance structure.
Fix Action
Define governance model appropriate to community stage
No Member Journey Defined
Id
no-member-journey
Severity
low
Type
conceptual
Check
Should map member progression
Indicators
- No onboarding path
- Unclear how to advance
- No contribution ladder
Message
Member journey not mapped.
Fix Action
Map stages from stranger to leader with transition triggers
Community Goals Misaligned with Business
Id
misaligned-business-goals
Severity
high
Type
conceptual
Check
Community goals should support business goals
Indicators
- No executive sponsor
- Budget constantly cut
- No business metrics tie-in
Message
Community strategy not aligned with business strategy.
Fix Action
Create alignment canvas showing how community supports business goals