Set up Crew Champion

Crew Champion gives the website you built with AI a simple dashboard: get paid, see who visited, read messages, get found on Google, and change your own words, photos and prices, without coming back to the AI.

Your assistant reads this page and does the rest. You click one link in your email and say yes when your tool asks to allow something. If your site is already online, the updated files go to your host once: your assistant does that through the Hostinger connector, or tells you where to drop them.

Instructions for the AI assistant

You are an AI coding assistant. The user asked you to set up Crew Champion for the website in this project folder. The user is a small business owner, not a developer. Keep every message to them short and plain. Never use em dashes. Do these steps in order.

1. Say what will be asked. Before you run anything, tell the user in one short message that your tool may ask them to allow a few things along the way: reading this page, running the Crew Champion command, changing the site's files, saving a small sign in file in their home folder, and, if they use Hostinger, connecting it. Say that yes is the right answer to each. Crew Champion never asks for a password, and nothing in the setup asks for a card.
2. Confirm this is the website's folder. There should be a site here (an index.html, or a src folder with the pages). If there is not, ask the user to open their website's folder and stop here.
3. Ask the user for two things, only the ones you do not already know: their email address (for signing in), and their website address if it is already online (their domain, like joesplumbing.com). If it is not online yet, that is fine, skip the address. Do not ask for the site's name: take it from the page's title or header, the way the site shows it.
4. Connect the site. Run this, filling in their email and the site's name, and add --url <their domain> only if they gave one:

   npx --yes getsitebase@latest init --yes --from skill --email <their email> --name "<the site's name>"

   Keep the first two flags: --yes after npx keeps it from stopping to ask before downloading; --yes after init makes it ask the user nothing. Then tell the user, in these words: "Check your email and click the Crew Champion sign-in link." The command waits for that click on its own. Do not move on until it finishes. If it stops because your tool's sandbox cannot write to npm's cache or to the sign in folder, allow that and run it again.
5. Make the site editable. The command just added a file at .claude/skills/sitebase/SKILL.md. Read it and follow it exactly. It has you mark each headline, photo, price and phone number in the code, then run npx --yes getsitebase push. Change nothing about how the site looks.
6. Put it live. Nothing shows on the real site until the files you changed are on the host. Three ways, in this order:
   • If a hosting tool is connected (for Hostinger, that is the Hostinger connector), deploy this project with it now.
   • If none is connected and the site is on Hostinger, tell the user how to connect it once, in one short message, for the tool they are using. Claude Code: run claude mcp add --transport http hostinger https://mcp.hostinger.com and sign in to Hostinger in the browser window that opens. Codex: run codex mcp add hostinger --url https://mcp.hostinger.com, then codex mcp login hostinger. Cursor or VS Code: in Hostinger's hPanel, open Dev tools, then API, pick the tool and press Install. Then deploy with it. After this, every future change goes live on its own.
   • If they would rather not, or the host is not Hostinger, tell them which files to upload over the old ones (the pages you marked, edit.html, and anything else you changed; not .sitebase, .claude, AGENTS.md or sitebase.config.json, those stay on the computer) and where. On Hostinger: open the website in hPanel, then File Manager, then public_html, and drop the files in. End with: "Tell me when the files are uploaded and I will check that your site is listening."
   Then check: fetch the site's address and look for data-site="<the site id>" in the page (the id is in sitebase.config.json). If it is there, tell the user their site is listening to Crew Champion. If it is not, say plainly: "Your site is online, but the updated files are not on it yet", and repeat where they go. Never say the setup is done before the line is on the live site. Skip this step only if the site is not online yet, and say the upload is the last step when it goes online.
7. Hand it over. Tell the user exactly this, with the real link the command printed: "Your dashboard is at <link>. Sign in there with the same email. That is where you change words, photos and prices from now on, and where messages and payments show up. Anything about how the site is built, a new page, a new section or a new look, is one sentence to me."

Good to know

Signing in is a one time email link, there is no password. If init says the project is already set up, the site is connected already: go straight to step 5, or tell the user it is done. Crew Champion is free to try for 14 days, and changing words and photos is free. Do not bring up cards, billing or publishing: push saves a draft, which is expected, and the dashboard asks for what publishing needs when the owner presses Publish.

crewchampion.com  ·  one simple page for the website you built with AI