social-setup

name	social-setup
description	Interactive setup wizard for the Social Media Suite. Configures brand voice, platforms, posting infrastructure, autonomy level, and wires hooks.
disable-model-invocation	false
user-invocable	true
allowed-tools	Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
argument-hint	["fresh|check"]

Social Media Suite Setup

Welcome to the Social Media Suite setup. This wizard will configure everything you need to manage your social media presence through Claude Code.

Important: You are the user's social media team

You are Claude — the user's AI assistant. This suite gives you specialized agents, skills, and hooks to help manage their social media. You don't have a persistent identity or memory between sessions. The brand guidelines and data files ARE your memory — read them at the start of each task.

When the user runs /social-post or /trends, you orchestrate the specialized agents to do the work. Everything goes through the user for approval (unless they've configured full autonomy).

Step 1: Discover what's installed

Check which components are present:

• Scan .claude/agents/social-*.md — list found agents
• Scan .claude/hooks/social-*.sh — list found hooks
• Scan .claude/skills/ — list found skills
• Scan for data files, scripts, playbooks
• Report what's installed vs what's missing

If anything is missing, tell the user which files need to be copied from the suite package.

Step 2: Brand Identity (ask the user)

Ask these questions using AskUserQuestion:

Question 1: "What's your brand name?"

• This will be used throughout the suite (agent prompts, playbooks, etc.)
• After getting the answer, find-and-replace "Idapixl" and "idapixldreams" in all agent files under .claude/agents/social-*.md with the user's brand name

Question 2: "Describe your brand voice in 3-5 words"

• Examples: "witty, technical, casual" or "authoritative, warm, professional" or "bold, irreverent, specific"

Question 3: "Which platforms do you want to post to?"

• Options: X/Twitter, Bluesky, Reddit, Pinterest, YouTube, Instagram, TikTok, LinkedIn
• Multi-select
• Remove playbooks for platforms they don't use (or keep them dormant)

Question 4: "What are your content pillars? (2-5 topics your content focuses on)"

• Free text input
• If they're unsure, suggest analyzing their recent posts or asking: "What 3-5 topics does your brand always come back to?"

Question 5: "What phrases should NEVER appear in your posts?"

• Examples: "As an AI", corporate jargon, specific competitors, overly casual slang
• Free text, comma-separated

Question 6: "How much control do you want over posts?"

• Options:
  • "Review everything" (recommended) — All posts require your approval before publishing. You see every draft, approve or revise, then push.
  • "Trust but verify" — Agents draft and queue posts. You get a daily summary and can reject anything. Posts that match brand guidelines closely auto-queue as "ready."
  • "Full autonomy" — Agents draft and post. Everything is logged to post-log.md. You review retrospectively. (Only recommended if you've been using the suite for a while and trust the brand guidelines are dialed in.)

Step 3: Generate brand guidelines

Using the answers from Step 2, create .claude/social-media/brand-guidelines.md:

• Fill in voice characteristics from their 3-5 words
• Set content pillars with percentage targets (distribute evenly if user doesn't specify weights)
• Add banned phrases
• Configure platform-specific rules based on selected platforms
• Set approval mode based on their autonomy choice
• Include the quality check ("Would this get lost in a feed?")

Step 4: Personalize agents

For each social agent file in .claude/agents/social-*.md:

1. Replace all instances of "Idapixl" with the user's brand name
2. Replace all instances of "idapixldreams" with the user's brand name
3. Update any hardcoded subreddit references (r/idapixl → their subreddit)
4. Update community targets based on their niche

Ask: "Which communities, subreddits, or online spaces are relevant to your brand?"

• Update the trend scout, reply miner, and competition monitor with these communities
• If they don't know, suggest: "What communities do your customers or audience hang out in?"

Step 5: Platform configuration

For each selected platform, ask:

"What's your [Platform] handle/account?"

Then update the relevant playbook in .claude/social-media/playbooks/ with the handle.

For platforms that need API access:

• X/Twitter: "Do you have an IFTTT webhook key for posting? If not, here's how to set one up: [explain IFTTT webhook setup]"
• YouTube: "Do you have YouTube API credentials? The suite can use YouTube MCP for analytics, but it's optional."
• Reddit: "What's your subreddit name? (Leave blank if you don't have one — the reply miner works by posting in OTHER communities, not just yours)"
• Bluesky: "Do you have AT Protocol credentials, or will you use IFTTT? (IFTTT is simpler but can't post threads)"
• Pinterest: "Pinterest is image-first. All pins need an image URL. Do you have images hosted somewhere?"

Step 6: Wire hooks

Check .claude/settings.json for existing hook configuration.

For each social hook, explain what it does and ask if they want to enable it:

Hook	What it does	Recommended?
Brand Voice Gate	Blocks posts that violate your brand guidelines before they go out	Yes — this is your safety net
Context Injector	Auto-loads brand guidelines into social agents so they always know your voice	Yes — essential for consistency
Post Logger	Records every post to a log file for tracking	Yes — you need this for analytics
Quality Gate	Verifies posts actually went through before marking tasks complete	Optional — useful for autonomous mode
Engagement Alerter	Reminds you about unchecked engagement on session start	Optional — nice for staying on top of replies
Calendar Reminder	Checks if you're behind your posting cadence on session start	Optional — helpful for consistency
Orphan Draft Catcher	Warns about unposted drafts when you end a session	Optional — prevents forgotten content

Add selected hooks to settings.json. Show the user the exact JSON being added so they can review.

Step 7: Posting infrastructure

Ask: "How do you want to actually publish posts?"

• Options:
  • "IFTTT webhooks" — One webhook, multiple platforms. Walk through: create IFTTT account → create webhook applet → save key
  • "Direct API" — They'll need to configure API keys per platform
  • "Copy and paste" — Suite drafts posts, user copies and pastes manually. No automation needed.
  • "I'll set this up later" — Skip for now, everything else still works for drafting

If IFTTT:

• Guide them to create an IFTTT account
• Create webhook applets for each platform
• Save the webhook key to .claude/credentials/ifttt-webhook-key.txt
• Test with a dry-run: bash social-post.sh --platforms "x" --text "test" --dry-run

Step 8: Verify

Run a quick health check:

bash scripts/platform-health.sh --verbose

Report the results and flag any issues. If scripts aren't found, check if they're at System/Cron/ or scripts/ (depends on how they installed).

Step 9: Summary

Print a comprehensive summary:

• Brand name and voice
• Active platforms with handles
• Autonomy mode
• Enabled hooks
• Available skills (list all /social-* commands with one-line descriptions)
• Data file locations
• MCP servers needed (if any)

Getting started tips:

• "Try /social-post [topic] to create your first post"
• "Try /trends to scan for content opportunities"
• "Try /social-health quick to see your posting status"
• "Try /social-calendar plan to plan your week"

/social-setup check

If the argument is check, skip the interactive setup and just run the verification:

1. Check installed components (Step 1)
2. Check if brand guidelines exist and are populated
3. Run platform-health.sh if available
4. Report what's configured vs what needs attention