Publish

Publish a studio

A studio's site runs on the studio's own Cloudflare account; homie.rocks only lists it.

Cloudflare (checked only when you publish)

1. In the studio folder: npx wrangler whoami.
2. Not signed in: run npx wrangler login. Tell the person in one line that Cloudflare opened in their browser and they approve once (a free account works, no payment method). Wait, then whoami again. Never ask for, paste or store an API key. Where no browser can open on this computer (a remote or cloud session), npx wrangler login --device prints a code the person approves on any device.
3. Several accounts: ask the person which one, and put its id in studio.json (cloudflare.accountId).
4. Cloudflare's own tools, for Cloudflare questions beyond the studio's deploy (a Worker's logs, a limit, what a Wrangler flag does, building on Cloudflare yourself):
   • Current facts come from Cloudflare's docs, not memory: its docs MCP server (https://docs.mcp.cloudflare.com/mcp, no sign-in) or any developers.cloudflare.com page with /index.md added for Markdown.
   • Cloudflare's plugin brings its own skills (wrangler, workers-best-practices, durable-objects and more) and its API MCP server. Offer it when the person wants that help, and they approve the install: in Claude Code /plugin marketplace add cloudflare/skills, then /plugin install cloudflare@cloudflare (it is also in Claude's plugin directory as cloudflare@claude-plugins-official); in Codex codex plugin marketplace add cloudflare/skills, then codex plugin add cloudflare@cloudflare.
   • The studio's own Worker, database, storage and secrets change only through npm run deploy and homie-studio, which record what they create in studio.json and never touch what they did not create. Never create, change or delete them with Cloudflare's MCP (its execute, a bindings or connector tool) or a bare wrangler command. The Homie mod (Claude Code) and Homie's hooks (Codex) hold such a change inside a studio (a delete, a secret, a hand rollout, a write to the live database) until the person says Proceed.

Deploy

npm run deploy
npx --no-install homie-studio check <id> --url <the live site it printed>

Before the first deploy, tell the person what it creates and what it costs: npx --no-install homie-studio deploy --plan prints it and changes nothing (one Worker, one D1 database, two SQLite-backed Durable Objects; free on the Workers Free plan; no R2).

deploy builds every game, creates the Worker and D1 database named in studio.json, applies migrations, deploys, and reads the live site once (the site then claims itself in the homie.rocks directory; nothing is stored by hand). It never creates R2. It refuses to use a Worker, database or bucket of the same name that this studio did not create; then rename it in studio.json and wrangler.jsonc (an older studio's is site/wrangler.jsonc). Never delete, rename or redeploy anything the studio did not create. When it answers with a needs step (a new account verifies its email address; an account with no workers.dev address picks one), say that step to the person and wait. The deploy itself is held for the person's Proceed, with where it goes and what changed since the last one: by the Homie mod in Claude Code, and by Homie's hooks in Codex and Grok Build (studio-setup says how a hold is answered there). Where nothing holds it (Codex or Grok Build before the hooks are trusted: the setup status says "Homie's holds: off"), say what the deploy would do in a sentence and wait for the person's yes.

Storage for songs and videos (npx --no-install homie-studio storage add, an R2 bucket) is separate and optional: Cloudflare asks for a payment method before R2 works, so only when the person wants it, after saying so (R2 has no egress fees; storage is free up to 10 GB-month, then US$0.015 per GB-month).

Songs and videos

Published entries of music/manifest.json and videos/manifest.json become pages at /music/<slug>/ and /videos/<slug>/ with every deploy (the music and video skills write them and redeploy). Without storage the site serves each file itself, up to 25 MiB a file. Once the studio has storage, big media lives in its R2 by default: every deploy moves each public file over 1 MiB, or left out of git, into R2 (uploaded, read back, checked by SHA-256) before the site stops carrying it, and serves it at the same address; the file stays in the studio folder. npx --no-install homie-studio media move --dry-run says what would move; media list shows what the site will show, where each file is served from, and why anything is left out. A studio with songs or videos and no games can still deploy.

An existing studio (made before @homie-rocks/studio 0.18.0) moving its media: upgrade (it lists the big media and moves nothing), npm install, media move --dry-run, media move, then npm run deploy, then curl one moved file with a byte range: a 206 with the file's full size in content-range, at the address it always had. Never delete the local files.

The site

Every deploy builds the studio's site from the studio (node_modules/@homie-rocks/studio/site/SITE.md has all of it): Home, Games, Music, Videos, Rooms and Posts, each only when the studio has something in it (a section with nothing has no tab and answers 404), and a landing for every game (the game skill's "Its landing page" makes one epic). Every page ends with "Made with Homie"; restyle it, keep it.

• A news post ("give my studio a news post", "announce the new game"): write posts/<YYYY-MM-DD>-<slug>.md (posts/README.md): frontmatter title:, summary: (one line: the cards and the feeds), image: (a /path on the site, like a game's cover), and game:, song: or video: to link one of the studio's own; then the body in markdown. Say something real: what is new, why it is fun, how to play, what is next. Posts are at /posts/, on Home, in /posts/feed.xml (Atom) and /posts/feed.json (JSON Feed), and in the directory's copy of the studio.
• The look: site/theme.json (colours, fonts, corner radius, a logo in site/public/) and site/theme.css for anything more. studio.json "tagline" is the studio's line; "site": { "featured": "<game id>" } picks Home's game.
• Anything of the studio's own wins: a whole page in site/pages/<path>/index.html (an About page, or a hand-made landing at site/pages/<id>/index.html), a piece of every page in site/partials/ (footer, header, home, game, game-<id>, post, head), files in site/public/. site/README.md in the studio lists them.
• Search engines and AI agents: every page carries schema.org JSON-LD (a full VideoGame on each landing, the studio's Organization on Home), and the site makes /robots.txt, /sitemap.xml, /llms.txt and /llms-full.txt from what is public (SITE.md, "Search engines and AI agents"). The studio's links elsewhere go in studio.json "site": { "schema": { "sameAs": [...] } }; a hand-made page takes <!-- homie:schema --> in its <head>. Ratings, reviews and prices are never added by hand.
• The play page shares its room: the room is in the address, and a small button at the edge gives Invite, Big screen and the room code. Nothing to set up.
• Before and after a deploy, look: npx --no-install homie-studio look --url <site> (the local dev address, then the live one) shoots every page on a computer and a phone and names what is wrong.

List in the directory

Going online never lists a studio. Listing is this separate step, public, and the person's to ask for: do it when they asked to be listed or said yes to your offer, never as part of a deploy.

Licences first: publish refuses to list a studio while a public game ships an asset with no licence record, a licence that forbids a web game, or a credit it owes but does not show (npx --no-install homie-studio assets check <id> names each one and its fix; the models skill has the rules). Fix them, deploy, then publish.

Call the Homie MCP tool studio_publish with the live site (or run npx --no-install homie-studio publish). It answers with each listed game's Play link, and with anything it did not list and why. The directory is in beta: at most 12 games per studio are listed, names and blurbs are checked (plain text, no links), and its owner can unlist a listing. Anyone can report a listing; only the directory's owner acts on reports, never an AI.

The beta also caps how many times a studio may publish in a day. publish (and studio_publish) says how many are left when the directory gives the number, and before it sends, how many this computer has sent today; the local tool's before: true says that without publishing. A refusal for the cap is not a broken studio: say when it ends and stop, never retry in a loop. A deploy that closes or opens a game's source asks the directory to read an already-listed studio again by itself (that uses one of the day's publishes); it never lists an unlisted one.