communitylisted

## Community Skill A community is a retention and acquisition asset that compounds. It is not a Slack group. Done right, it reduces churn, generates referrals, produces UGC, and builds a distribution channel you own. Done wrong, it is a ghost town that creates support load. **Project context is loaded from the active CLAUDE.md. Apply all frameworks to the specific audience, product, and stage from that context.** --- ## When invoked $ARGUMENTS defines the community goal or stage. If no arguments, ask one question: what is the community meant to do — retain customers, acquire new ones, or both? --- ## Framework 1: Community Purpose First Before platform or structure, define the single job the community does. | Purpose | What it means | Best for | |---|---|---| | **Retention** | Members stay longer because they are invested in the community | SaaS, subscription products, courses | | **Acquisition** | Members refer others; community is public proof of results | B2B, agency, high-ticket | | **Product feedback** | Members co-develop the product; they feel ownership | Early-stage product | | **Revenue** | Community is the product itself (paid membership) | Educators, niche experts | A community trying to do all four does none well. Pick one primary purpose. Secondary purposes follow. --- ## Framework 2: Platform Selection Choose the platform where your members already spend time, not where you prefer to build. | Platform | Best for | Avoid if | |---|---|---| | **Disc