This page is designed for Claude to read and follow. It contains step-by-step instructions for guiding a user through the complete AlpacApps infrastructure setup.
One step at a time: Present ONE sub-step, wait for the user to confirm they've done it, then move to the next sub-step. Do NOT give multiple instructions in one message. For example, don't say "install Git, create a GitHub account, and install the GitHub CLI" — instead say "First, let's check if Git is installed. Open your terminal and run git --version. What do you see?" Then wait.
Checkpoint rule: Do not move to Step N+1 until every item in Step N is explicitly confirmed by the user. If the user says they've already completed something, still confirm it — ask them to verify (run a command, paste a screenshot, or state the result). "I already did that" requires a quick proof before proceeding.
Start in Code: Have the user switch to Claude Code or Codex Code mode immediately and select a new, empty folder. The agent creates the GitHub repository from the template and clones it automatically; do not make the user manually clone first unless GitHub CLI automation is unavailable.
Screenshot verification: At each step that requires the user to interact with a website or application (GitHub, Supabase, Google Cloud, Cloudflare, etc.), ask them to paste a screenshot so you can verify they're on the right page and guide them to the correct buttons and fields.
Adapting to the user: Adapt commands and instructions to their OS (Mac, Windows, Linux). If they've already completed a full step (e.g., "I already have a Supabase project"), confirm the key details you'll need (project ref, password, etc.) and move on — but still follow step order.
Before any setup, ask the user one question:
What kind of project? Two profiles are available:
Record their profile choice. You'll need it for the Claude Code setup wizard later. Service selection happens at the end — don't discuss it now.
Ask what OS they're using. This affects install commands throughout.
Before GitHub, Git, or any account setup, install and test a screenshot tool. Ask the user to paste one test screenshot into the Code-mode conversation.
On Mac, always install Xcode Command Line Tools first — this provides Git, compilers, and other developer essentials that Claude Code needs.
Ask the user to open Terminal and run:
xcode-select --install
If already installed, the terminal will say so and they can move on. If not installed:
The download is ~1–2 GB and can take several minutes. Wait for it to complete before moving on.
git --version. They should see a version number (e.g., git version 2.39.5).After Xcode CLI Tools are confirmed, run the prerequisite installer. This installs or upgrades: git, GitHub CLI, Node.js, Supabase CLI, Wrangler, psql, Bitwarden CLI, TypeScript.
bash <(curl -fsSL https://alpacaplayhouse.com/scripts/install-prereqs.sh)
If the user already has Homebrew and prefers granular control, they can also use brew bundle from the project's Brewfile after cloning.
If the user is NOT on Mac, they need to install these manually:
sudo apt install git (Linux)winget install --id GitHub.cli (Windows) or see Linux install docsnpm install -g supabase (installed by wizard if missing)npm install -g wrangler (installed by wizard if missing)npm install -g @bitwarden/cli — the standard secrets vault; sign in once with bw logingit --version && node --version successfully.Ask if they already have a GitHub account. If not, direct them to github.com/signup.
Then authenticate the GitHub CLI:
gh auth login
The CLI will ask a series of questions. Tell the user to:
GitHub.com)HTTPS)Login with a web browsergh auth status shows "Logged in".Preferred: install Cursor, sign in, open an empty folder, and select Grok 4.7 in Agent. Grok chat and apps are available separately. Claude Code and Codex remain alternatives.
Minimal spending: follow the OpenCode walkthrough. The tool is free; connected model usage is billed separately. Run opencode, connect your provider with /connect, and select a low-cost model with /models. Save keys in Bitwarden and set a provider spending limit.
AGENTS.md. Check image support before relying on screenshots.Direct the user to the template repository:
github.com/rsonnad/alpacapps-infra
my-salon-app)In their new repository:
The site will be live at https://USERNAME.github.io/REPO-NAME/ within 1–2 minutes.
Return to the Code-mode session that began in the empty folder. It should use authenticated GitHub CLI to create the repository from the template and clone it locally; the user should not need to construct a clone command.
ls (Mac/Linux) or dir (Windows).Keep using the agent that created the project, and open the cloned project folder if it did not switch automatically.
opencode in the project folder with your chosen provider and model.The project ref is the random string in the Supabase URL. It looks like this:
https://supabase.com/dashboard/project/abcdefghijklm
The bolded part is the project ref. Alternatively:
Record these two values — you'll paste them into Claude Code in Step 6:
abcdefghijklm)Cloudflare manages DNS, R2, D1, Pages, Workers, and related infrastructure. For initial setup, the user explicitly authorizes a temporary, maximally broad API token so the agent can configure everything without narrowing its permissions.
Record these values — you'll paste them into Claude Code in the next step:
.org/.us or a .com, check availability and current price, register it through Cloudflare Registrar when possible, and pause only for required purchase confirmation. Configure https://DOMAIN as the public placeholder and https://in.DOMAIN as the authenticated intranet.Open Claude Code in your project folder and let it handle all the technical setup.
/setup-alpacapps-infraIf on the Pro plan ($20/mo) or lower, paste this prompt instead:
Set up my AlpacApps project. I chose the [PROFILE] profile and want these services: [LIST].
My Supabase project ref is: [REF]
My database password is: [PASSWORD]
My Cloudflare email is: [EMAIL]
My Cloudflare temporary full-access API token is: [CF_TOKEN]
Follow the setup wizard in .claude/skills/setup-alpacapps-infra/SKILL.md to configure everything.
Handle all terminal work — CLI installs, database setup, edge functions, git pushes.
For the initial Cloudflare configuration, use my temporary full-access token as authorized. Do not narrow or replace it with a least-privilege token; I will delete temporary Cloudflare token(s) manually once setup is verified.
Ask me when you need credentials for optional services (API keys, etc.).
Replace the bracketed values with:
[PROFILE] — "Property Management" or "General AI Enablement"[LIST] — the services they selected in Step 1[REF] — Supabase project ref from Step 4[PASSWORD] — database password from Step 4[EMAIL] — Cloudflare account email from Step 5[CF_TOKEN] — temporary full-access API token from Step 5Claude Code will automatically:
After setup, Claude Code is how you build everything. Just describe what you want:
Claude Code handles the code, commits, and deploys.
gstack adds powerful skills to Claude Code: headless browser for QA testing, code review, ship workflow, engineering retrospectives, and more. Sub-second commands with zero token overhead.
In your Claude Code session, run:
curl -fsSL https://raw.githubusercontent.com/garrytan/gstack/main/install.sh | bash
Verify it installed:
ls ~/.claude/skills/gstack/SKILL.md
If the file exists, gstack is installed and Claude Code will automatically detect the skills.
/browse — Headless browser for QA testing and site dogfooding (~100ms per command)/review — Pre-landing code review with production risk detection/ship — Ship workflow: merge base, test, review, bump, push, create PR/qa — Systematic QA testing with auto-fix (Quick/Standard/Exhaustive tiers)/retro — Engineering retrospectives with commit analysis and trend tracking/plan-ceo-review — CEO/founder-mode plan review/plan-eng-review — Engineering manager plan reviewUpdate later: Run /gstack-upgrade inside Claude Code, or re-run the install script.
Source: github.com/garrytan/gstack (MIT license)
Your core stack is running. Now walk through these optional services and ask which ones they want to add. Claude Code will configure each one — just provide the API keys when asked.
For each service the user selects, walk them through the vendor signup below, then have Claude Code configure it.
Install Grok Bot, the persistent agentic harness, sign in, and create a project Bot. Check your plan for access before purchasing; Premium and above include Grok Bot with shared usage; Plus does not include it.
Your Project — Grok Bot Webhook. Store account logins, recovery codes, and provider API keys in the same project collection. Never paste secret values into this repository or chat.GROKBOT_WEBHOOK_URL and GROKBOT_WEBHOOK_KEY (raw key only). Run the test below in that environment. Do not put secrets in browser JavaScript, shell history, or logs.curl --silent --show-error --output /dev/null --write-out '%{http_code}\n' \
--request POST "$GROKBOT_WEBHOOK_URL" \
--header "Authorization: Bearer $GROKBOT_WEBHOOK_KEY" \
--header 'Content-Type: application/json' \
--data '{"event":"setup.test","environment":"staging"}'
These Grok Bot routine webhooks use Bearer authentication; separate Grok automations webhooks use HMAC signatures.
For failures, check the routine is active and the saved URL/key are current. If Webhook fields are absent, update the desktop app and consult support; use a schedule meanwhile. If your event provider cannot send a custom Bearer header, use a server-side adapter that verifies the provider’s signature before forwarding a minimal payload. Keep the Bot key in that adapter’s secret store.
Official webhook routine instructions • Grok Bot installation guide
When the agent asks for credentials for optional services, direct the user to these vendor pages. For each service, the user needs to create an account and get an API key.
https://USERNAME.github.io and, if configured, https://YOUR_DOMAINhttps://PROJECT_REF.supabase.co/auth/v1/callbackUses the temporary full-access Cloudflare API token you provided in Step 5 — no additional credentials needed.
<project>-media (images, uploads) and <project>-backups (DB exports, config snapshots)The setup wizard creates two D1 databases using the temporary full-access API token from Step 5:
<project>-sessions — Claude session logging and search<project>-devcontrol — Task tracking, build logs, deployment historyBoth are free tier (5M reads/day, 100K writes/day, 5 GB storage).
Other ways to get started: