inner-circle-director

Structure tiered access, VIP mechanics, recognition systems, and premium community experiences, then output a membership framework. Use when Codex needs to design belonging and access around a persona

SKILL.md

GitHub

Inner Circle Director

Use this skill when you need a tiered access model, VIP mechanics, or recognition structure around a creator or founder community.

Default product shape: a compact macOS MenuBarExtra utility with a source-aware popover for tier setup, access design, and framework export and an optional settings/history window.

Quick Start

  1. Confirm the subject, target audience, and source window.
  2. Gather only public or user-authorized material into a working set.
  3. Produce a membership-framework with the default sections below.
  4. If the user wants a richer product concept, keep it menu bar first and native to SwiftUI.

Accepted Inputs

  • current audience size, existing memberships, and moderation capacity
  • planned perks such as early access, Q and As, events, or drops
  • pricing context, if any, plus non-paid recognition paths
  • notes about community norms, fairness concerns, and operational limits

Output Artifact

Primary artifact: membership-framework

Default sections:

  • Tier structure with purpose and entry logic
  • Perks, access rules, and recognition signals
  • Operational limits and moderation implications
  • Fairness notes, non-paid pathways, and downgrade paths
  • Pilot framework and review checkpoints

Workflow

Gather Sources

  • Map the existing audience structure before inventing new tiers.
  • Separate meaningful access from cosmetic status markers.
  • Note operational limits so premium promises stay realistic.

Distill Signal

  • Score each proposed tier by clarity, fairness, and maintenance cost.
  • Reject perks that rely on arbitrary favoritism or unhealthy status pressure.
  • Look for at least one valued non-paid participation pathway.

Build The Artifact

  • Export a membership framework with tiers, perks, review cadence, and guardrails.
  • Show where a perk should remain invitation-free, paid, or merit-based.
  • End with downgrade and sunset rules so the structure can evolve safely.

Mac Product Shape

  • Prefer MenuBarExtra with these primary actions:
    • Set Tiers
    • Design Access
    • Review Perks
    • Export Framework
  • Keep the popover between 320 pt and 380 pt wide with grouped sections, clear source status, and a strong export action.
  • Use a lightweight settings or history window only for source rules, saved exports, or weighting controls.

Safety Boundaries

  • Work only from public or user-authorized material.
  • Do not assist with stalking, covert profiling, rumor laundering, harassment, or minors-focused manipulation.
  • Do not recommend exploitative spend pressure, arbitrary social ranking, or access models that punish ordinary fans for not paying.

Example Prompts

  • Use $inner-circle-director to design a tiered community model for this artist with VIP access, non-paid recognition paths, and clear fairness rules.
  • Use $inner-circle-director to structure founder-community tiers around product drops and AMAs without turning the whole audience into a status ladder.

Resources

  • references/product-spec.md: product surface, SwiftUI layout, artifact template, icon direction, and first-run behavior.