Configure Vibe

Vibe Marketplace and Plugins

7. Update vibe marketplace, permissions, and MCP servers:

   • Run: vibe update
   • This command downloads the latest vibe release and:
     • Updates the marketplace at ~/.vibe/marketplace
     • Syncs permissions to ~/.claude/settings.json
     • Syncs MCP server configurations
     • Updates the vibe CLI itself

8. If only permissions/MCP sync is needed (no download):

   • Run: vibe sync
   • This syncs from the local marketplace without downloading

9. Check installation status:

   • Run: vibe status
   • This shows:
     • Marketplace installation status
     • Installed plugins
     • Permission and MCP server counts

10. Diagnose and fix issues:

    • Run: vibe doctor
    • This checks:
      • Prerequisites (gh, jq, yq, claude, python3)
      • Marketplace installation and registration
      • Settings and permissions
      • Outdated cached plugins (like renamed skills)
      • Python3 availability (required for logfood-querier and other tools)
    • It will automatically fix common issues and provide remediation steps

User Profile Setup

11. Check for existing vibe profile:

    • Check if profile exists: cat ~/.vibe/profile 2>/dev/null
    • If profile exists, show a summary (name, accounts, last generated date)
    • If profile does not exist, inform the user:

      "No vibe profile found. The vibe profile stores your accounts, use cases, team members, and Slack channels. This helps other vibe skills provide personalized context."

12. Offer to build profile:

    • Ask the user: "Would you like to build your vibe profile now?"
    • If yes, spawn the vibe-profile agent to discover and build the profile
    • The agent will:
      • Discover user identity from git config and environment
      • Query Salesforce for assigned accounts and use cases
      • Find relevant Slack channels (external and internal)
      • Look up team members (AEs, DSAs, specialists)
      • Write the profile to ~/.vibe/profile
    • If no, inform the user they can build it later by asking Claude to "build my vibe profile"

Completion

13. Summarize status:

    • List what was configured
    • List any issues encountered
    • Remind user to restart Claude Code if permissions or plugins were updated

14. Provide next steps:

    • If first-time setup: Restart Claude Code and test with a simple command
    • If update: Verify new features work as expected
    • Provide link to vibe documentation if available