Skip to main content

1. Integrate with openclix-init

openclix-init:
  • Detects platform (Expo/RN/Flutter/iOS/Android)
  • Copies local-source templates into your repo
  • Wires minimal initialization/event/lifecycle touchpoints
  • Reuses existing dependencies where possible
  • Runs platform-appropriate build/analyze verification

2. Generate config with openclix-design-campaigns

openclix-design-campaigns:
  • Creates a structured campaign planning profile
  • Designs lifecycle campaigns (onboarding/habit/re-engagement/milestone/feature discovery)
  • Produces schema-valid config (openclix/config/v1)
Expected output:
  • .clix/campaigns/app-profile.json
  • .clix/campaigns/openclix-config.json

3. Measure impact with openclix-analytics

openclix-analytics:
  • Detects provider: Firebase > PostHog > Mixpanel > Amplitude
  • Wires OpenClix event forwarding with openclix_* properties
  • Produces pre/post impact artifacts for retention + engagement
Expected output:
  • .clix/analytics/impact-metrics.json
  • .clix/analytics/impact-report.md

4. Draft campaign operations with openclix-update-campaigns

openclix-update-campaigns:
  • Reads impact + campaign metrics and evaluates per-campaign actions.
  • Produces openclix-config.next.json without mutating active config.
  • Keeps apply behind explicit confirmation.
Expected output:
  • .clix/campaigns/update-recommendations.json
  • .clix/campaigns/openclix-config.next.json

5. Run agent retention operations with retention_ops_automation.sh

Use the helper script when you want OpenClaw, Claude Code, and/or Codex prompts generated from the latest OpenClix artifacts.
bash scripts/retention_ops_automation.sh \
  --root <target-project-root> \
  --agent all \
  --delivery-mode auto \
  --dry-run
Expected output:
  • .clix/automation/run-summary.json
  • .clix/automation/prompts/openclaw.md
  • .clix/automation/prompts/claude-code.md
  • .clix/automation/prompts/codex.md
Next: Agent-based mobile app retention automation guide