メニュー
Builds and nurtures user community — welcome flows, discussions, feedback loops, events, and retention. Use when you need users to engage on your page, stick around, refer others, or when launching in Discord, forums, or product communities.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.
Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.
Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."
Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.
Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.
Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.
| name | community-engagement |
| description | Builds and nurtures user community — welcome flows, discussions, feedback loops, events, and retention. Use when you need users to engage on your page, stick around, refer others, or when launching in Discord, forums, or product communities. |
Traffic without engagement is a leaky bucket. Developers join products when they see real people having real conversations — not an empty forum and a bot saying "welcome." This skill turns sign-ups into active members who come back, invite peers, and give feedback.
Chains from [[growth-strategy]] (ICP, channels) and [[social-distribution]] (drive people in). Feeds [[content-marketing]] with user stories and [[growth-strategy]] with qualitative insights.
Skip when the product has no community surface yet — define one first or use [[social-distribution]] for audience-only channels.
Pick one primary home (don't split early):
| Surface | Best when |
|---|---|
| In-app feed / profiles | Product IS the network (e.g. developer-connection) |
| Discord | Real-time chat, events, support |
| Slack | B2B teams, private beta |
| GitHub Discussions | Open-source, technical Q&A |
| Forum (Discourse) | Long-form threads, searchable archive |
Document:
Write short, clear rules:
Tone: Welcoming, peer-to-peer, moderator light-touch. Developers hate corporate-speak in community spaces.
Pin rules in the primary channel. Add #introductions, #help, #showcase (or equivalents).
New member journey:
Sign up → Welcome message (email + in-app)
→ Profile prompt ("Add stack, goal, location")
→ Suggested first action ("Introduce yourself" / "Find 1 connection")
→ Day 1 nudge if inactive
→ Day 7 check-in with tip or event invite
Draft copy for each touchpoint. First action within 24h is the activation metric.
For developer-connection products specifically:
Plan recurring activities:
| Activity | Frequency | Goal |
|---|---|---|
| Introduction thread | Weekly | Lower barrier to first post |
| AMA / office hours | Bi-weekly | Expert draw + live engagement |
| Showcase Friday | Weekly | User-generated content |
| Challenge ("Connect with 3 devs this week") | Monthly | Activation |
| Feedback thread | Monthly | Product input + feeling heard |
Calendar 4 weeks ahead. Assign facilitator (you or power user).
Before driving traffic:
Empty communities die on first visit. Seed authentically — real team intros, not fake personas.
Don't spam. Add value first:
Track which communities convert — double down on two, drop the rest.
Weekly community digest for product team:
Use [[decision-docs]] if community feedback drives product decisions.
Community work is done when: