Headless

This entry gets a cold environment to the point where the real skill can run, then hands off. It has three phases:

1. Install (deterministic). The skill and its companions land under .agents/skills/.
2. Bootstrap (deterministic, scripted). The installed script verifies your environment (the Wix CLI) and handles login, so the run starts from a known-good, authenticated state. You just run it and relay its events.
3. Hand off (agentic). Open wix-headless/SKILL.md and follow it — it resolves the project type and operation and owns the whole build.

Three starting points come through here, all handled the same way — install, run the bootstrap, then hand off:

• new — a prompt with no project (empty CWD)
• connect — an existing frontend/design not yet on Wix (a project on disk without wix.config.json, or a brought-in zip/URL)
• iterate — a project already connected to Wix (.wix/ or wix.config.json present)

The bootstrap only verifies the CLI and logs you in, so it’s fine to run in every case (an existing session just reports logged_in). After it, wix-headless/SKILL.md resolves what to do and owns the build.

Phase 0 — Node (the one manual prerequisite)

This flow requires Node ≥ 24.18. Check it:

If that errors (Node not installed) or prints a version below 24.18, install or upgrade Node and re-check — do not try to work around it:

• macOS: brew install node (or nvm install 24 && nvm use 24)
• Linux: nvm install 24 && nvm use 24 (or your distro’s Node 24+ package)
• Windows: winget install OpenJS.NodeJS.LTS (or download from nodejs.org)

Phase 1 — Install the skills

CI=1 forces plain non-interactive CLI output — keep it on every Wix CLI command. Repeat --skill per skill; a comma-separated list is not parsed:

The skills land in .agents/skills/.

Phase 2 — Run the bootstrap (deterministic)

Run the skill’s bootstrap script — an ordinary foreground command that exits on its own within seconds. It verifies the Wix CLI and handles login, emitting one JSON event per line on stdout. Run it and relay its events to the user.

The script is inspectable: it only checks the Wix CLI via npx and drives wix login (a device-code flow) — no other network calls, and the only files it writes are the login’s own output and pid under the OS temp dir.

Relay these events

The script emits one JSON object per line:

On awaiting_user, run the script again once the user says they’ve logged in: it reports logged_in and you continue. Re-running while they’re still in the browser is harmless — it returns the same code rather than issuing a new one.

Phase 3 — Hand off

Open .agents/skills/wix-headless/SKILL.md and follow it. That skill owns the rest of the run — it resolves the project type (managed / self-managed / stripe) and, for managed, the operation (create / connect), then runs Discovery → Setup → Seed → the SDK handoff, and for managed create/connect it also scaffolds, builds, and releases.

• Don’t scaffold, install apps, or release by hand here — the skill does all of that (SETUP.md, references/managed/CREATE.md, etc.). This entry stops at logged in.
• You’re already authenticated from Phase 2, so the skill’s managed auth step (references/managed/AUTHENTICATION.md §1 whoami) will pass without prompting again.