WayCup Engine

GTM Engineer Onboarding (WSL)

3 min read

🚀 GTM Engineer Onboarding: Windows/WSL Edition

🏁 Phase 0: Terminal Configuration (Windows Terminal)

To avoid “Windows Syntax Hell,” you must configure Windows Terminal to launch into Linux by default.

Instructions:

  1. Open Windows Terminal.
  2. Press Ctrl + , to open Settings.
  3. Under Startup, set Default profile to Ubuntu.
  4. Under Profiles (Ubuntu) > Starting directory, uncheck “Use parent process directory” and set it to ~ or \\wsl$\Ubuntu\home\yourusername.
  5. Save and restart the terminal. You should now see a $ prompt instead of a PS > prompt.

Welcome to the WayCup Engine, Brenn. This guide will synchronize your Windows/WSL2 environment with the WayCup Thin-Client Infrastructure (TCI), allowing you to jump straight into Go-To-Market (GTM) Engineering.

🛠️ Phase 1: Environment Diagnostics

Before making any changes, we must verify that your WSL foundation is healthy.

Instructions:

Open your WSL (Ubuntu) terminal and run these commands one by one.

# 1. Verify 1Password CLI is installed and authenticated
op whoami
 
# 2. Verify Node is ready for the Gemini & HubSpot CLIs
node -v && npm -v
 
# 3. Verify Tailscale is active on the WayCup network
tailscale status | head -n 3
 
# 4. Verify you are in the Linux filesystem (Should NOT start with /mnt/c/)
pwd

✅ Testing & Verification

  • Expected Result: op whoami returns your WayCup email. Node is v20 or v22. Tailscale shows you on the WayCup tailnet. pwd returns /home/brennwc (or similar).
  • ❌ Remediation:
    • op command not found: Run sudo apt install 1password-cli and sign in.
    • Tailscale not running: Run sudo tailscaled --tun=userspace-networking --socks5-server=localhost:1055 & then tailscale up.
    • Wrong Directory: Run cd ~ to return to your Linux home. Never run TCI tools from /mnt/c/.

🔗 Phase 2: Dotfiles & Core Aliases

Because you maintain a fork of Kevin’s dotfiles, we do not want to run global sync scripts that overwrite your personal terminal UI. Instead, we use a shared “Gist” for core WayCup commands.

Instructions:

  1. Open your local aliases file:
nano ~/.bash_aliases
  1. Paste this line at the very bottom (Kevin will provide the actual Gist URL):
# WayCup Core Aliases (Cloud Synced)
source <(curl -s https://gist.githubusercontent.com/kevindockman/4f135243cf94c7fcd13925a5a31926a4/raw/waycup_core_aliases.sh)
  1. Save and reload:
source ~/.bashrc

✅ Testing & Verification

  • Expected Result: Run cdway. It should instantly transport you to the 01_internal/core/vault directory.
  • ❌ Remediation: If it fails, ensure curl is installed (sudo apt install curl) and verify the Gist URL with Kevin.

💻 Phase 3: Antigravity IDE via Windows

You will run the Windows Native version of Antigravity for optimal UI performance, but trigger it from inside WSL.

Instructions:

Add this alias to your ~/.bash_aliases (adjust the path if your Windows username differs):

# Map 'antigravity' in WSL to the Windows executable
alias antigravity='/mnt/c/Users/Brenn/AppData/Local/Programs/Antigravity/Antigravity.exe'

✅ Testing & Verification

  • Expected Result: Run antigravity . in your core/vault directory. The Windows UI should open seamlessly, editing the Linux files.
  • ❌ Remediation: Check the exact path to your Antigravity.exe in Windows Explorer and update the alias.

🤖 Phase 4: AI & GTM Tooling

Install the core CLI tools required for WayCup development.

Instructions:

# Install Gemini CLI globally
sudo npm install -g @google/gemini-cli
 
# Install HubSpot CLI globally
sudo npm install -g @hubspot/cli
 
# Index your local vault to power the AI Brain
cd ~/projects/01_internal/core/vault
gemini /obsidian:index

✅ Testing & Verification

  • Expected Result: The Gemini CLI should successfully index your markdown files.
  • ❌ Remediation: If Gemini fails to index, ensure your ~/.gemini/settings.json and .env are configured correctly per your original bootstrap guide.

Graph View