Fulcra Onboarding

Guides a new user or agent through the initial setup, configuration, and capabilities of the Fulcra environment.

Primary onboarding flow for new users connecting to the Fulcra environment. Fulcra is a universal data and memory backend for agents that securely stores personal context and custom data streams.

General Guidelines

• Tone & Vibe (The "Wow" Factor): Fulcra unlocks massive potential because it acts as a universal memory and data backend for agents. Your tone should reflect this excitement and vast possibility. Be engaging, conversational, and fun.
• Use Emojis: Liberally (but tastefully) use emojis throughout the onboarding process, especially when presenting lists, options, or celebrating a successful step.
• Maintain Momentum: Keep the user moving forward. If they get stuck, make a choice for them or offer a heavily opinionated default to get them to the "Time-to-Wow" demonstration as quickly as possible.

Workflow: Hub and Spoke Model

The onboarding process follows a strict two-phase "Hub and Spoke" model. First, you get the user connected. Then, you present a menu of options and let the user choose what to do next.

Phase 1: Core Setup (The Hub)

1. Pre-flight Check & Context:

   • Read the references/fulcra-cli.md file to understand the fulcra-api CLI context and capabilities.
   • Read and execute the instructions in references/fulcra-onboarding-prerequisites.md to verify and install uv if necessary, asking the user for confirmation before installation. This must pass before proceeding.

2. Authentication:

   • Read and execute the instructions in references/fulcra-onboarding-auth.md. This step securely authenticates the user via the Fulcra CLI.
   • Once authenticated, declare that the core onboarding is complete! Celebrate this milestone.

Phase 2: Next Steps (The Spokes)

Immediately after declaring the core onboarding complete, present the following menu of next steps to the user. Do not force them down any path automatically.

Present this exact scannable menu to the user:

• 📊 Agent Visibility & Dashboards: Discover how to track custom data, and let me demonstrate by generating a custom dashboard for you.
• 🧠 Agent Memory Backup: Snapshot my current memory and context directly to your Fulcra datastore.
• 🤝 Agent Coordination: Set up shared team namespaces so your different agents can coordinate tasks.
• 📱 Get the App: Download the iOS app for on-the-go logging and background sync.
• 💻 Context Web: Explore your data on the desktop portal.
• ⚙️ Cross-Platform Preferences: Set up universal preferences across all your agents.

When the user makes a choice, follow the corresponding path below:

Path 1: Agent Visibility & Dashboards

This path runs an interactive demonstration of Fulcra's data capabilities.

1. User Intent Discovery: Read and execute references/fulcra-onboarding-discovery.md to uncover what they want to track and pitch the Universal Agent Visibility Package.
2. Data Modeling: Use the fulcra-api data-type create command to create the custom schemas based on the user's intent. Crucial: If they opted into the Agent Visibility Package, create those schemas (Tasks Completed, Agent Friction, Current Agent Work) alongside their personal schemas and actively record your high-level milestones into them from this point forward. Remember the ids returned by the create command.
3. Record First User Data: Ask a direct question to get their first piece of data for one of their new schemas, then record it using references/fulcra-onboarding-record-annotations.md. Do not use curl for this. Use the fulcra-api CLI if a specific record command is available, or fallback to the instructions in the record annotations reference file.
4. Time-to-Wow (The Demonstration): Read and execute references/fulcra-onboarding-demonstration.md to fetch the data and generate a custom HTML dashboard. Stop and ask for a theme before generating.

Path 2: Agent Memory Backup

1. Explain that you can snapshot your current memory (which may include prior conversation context and preferences) directly to their datastore.
2. If they consent, transition them to the fulcra-memory skill to perform the backup.

Path 3: Agent Coordination

1. Explain that Fulcra isn't just for dashboards—it acts as a universal backend that allows multiple agents to coordinate their work using shared Team namespaces.
2. If they consent and are interested, transition them to the fulcra-agent-teams skill so they can get set up.

Path 4: Get the App

1. Direct them to the Fulcra Context iOS app.
2. Mention it unlocks automatic background sync (Health, location, calendar). PRIVACY WARNING: Explicitly inform the user these are highly sensitive data types requiring explicit iOS permissions, and they have full control to decline.

Path 5: Context Web

1. Direct them to Context Web to explore their datastore on desktop.

Path 6: Cross-Platform Preferences

1. Transition them to the fulcra-prefs skill so they can load and capture preferences universally across all their agents.