Higgsfield Websites

Higgsfield website builder (CLI) — three product types, three flows

You drive the whole lifecycle through the Higgsfield CLI (higgsfield website …), then edit code on the local filesystem with git + bun. You are building ONE per-website Cloudflare Worker: a React 19 + TanStack Start app, server-rendered (SSR), deployed as a single Worker at the product's own subdomain. The project lives in app/ — run every bun/build command from there.

The three types — and the REQUIRED --type on create

higgsfield website create requires --type, and it is the USER'S choice — when the request doesn't make it obvious, ask the user before creating (one question, up front):

• --type website — a standalone product with NO Higgsfield integration and NO AI generation of any kind (no image/video/audio/text generation — not via Higgsfield, and not via some other provider): no "Sign in with Higgsfield", no requests to Higgsfield, no fnf SDK. Every website gets a fully independent brand: own palette, type, and chrome from a design brief, custom Tailwind/CSS only — never import @higgsfield/quanta/* or use q-prefixed tokens anywhere, and no "Powered by / Built on Higgsfield" badges or mentions in page content. The user's brand is the only brand on the page.

  bashCopy code
  higgsfield website create --type website
  

• --type app — a product tightly integrated with Higgsfield: its users Sign in with Higgsfield and generate images/videos through the fnf SDK (the full auth + D1 contract applies). An app must look and feel like a Higgsfield product: UI built with Quanta (references/quanta-design.md) — and, for anything Quanta lacks, your own component built from Quanta primitives (never a third-party UI library) — starting from a standard app layout (references/app-layouts.md). Quanta and the app layouts are app-only — never applied to a --type website build. The independent-brand rule and the wow pipeline (design-taste-frontend, boards, wow catalog) are the website path; apps never get a custom brand — Quanta is the brand.

  bashCopy code
  higgsfield website create --type app
  

• --type game — a browser game: realtime multiplayer rooms on the game template, where the game itself is six pure functions in app/src/logic.js and the platform already owns sockets, rooms and persistence. Requires a game genre as --category (arcade, puzzle, shooter, …, from higgsfield website categories) and takes no --template — a game scaffolds from the only template it can use. Single-player counts: set minPlayers: 1. See references/game-flow.md.

  bashCopy code
  higgsfield website create --type game --category arcade
  

Generation is ALWAYS an app. Any product that generates images, video, audio, or other AI media runs on Higgsfield — build it as --type app (Sign in with Higgsfield, generation on the user's Higgsfield credits). NEVER offer the user an option to "bring your own image/video API" or plug in their own generation key for a website — that path does not exist. --type website is ONLY for sites with no generation and no tie to Higgsfield or any other generation service. (A website may still use ordinary non-generation third-party APIs — payments, maps, email — with the user's own keys; that is unrelated to this rule.)

Quick tells: "landing page / portfolio / marketing site / SaaS with its own users, no AI generation" → website. "generates images/video/audio, or anything with Higgsfield models, credits, or generation history" → app. "something you play — a game, multiplayer or single-player" → game.

Games moved onto this pipeline from a separate engine that is being retired. The higgsfield game … commands are gone: a game is created, deployed and published exactly like a website. Any doc saying otherwise is out of date.

Always set a subdomain on create

higgsfield website create takes an optional --subdomain — it becomes the site's slug, so the live URL is <subdomain>.<host>. Always set it: pick one from the product's name or purpose; only omit it (which yields a random slug) if the user explicitly wants a random one. Rules for a good subdomain:

• More than 4 characters — short single words are reserved, so go a bit longer.
• Memorable — derive it from the product name/purpose (e.g. lumen-notes, pixelforge), not a random string.
• Allowed characters only — lowercase letters, digits, and single hyphens (DNS-safe). No spaces, underscores, uppercase, or leading/trailing hyphens.

A few reserved labels (e.g. api, www, app) and already-taken subdomains are rejected — if that happens, try a close variant.

Prerequisites

1. If higgsfield is not on $PATH, install it:

   bashCopy code
   curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh
   

2. If higgsfield account status reports Session expired / Not authenticated, ask the user to run higgsfield auth login (interactive) and wait for confirmation.
3. git and bun are used locally once you clone the repo. The CLI itself handles create / repo / deploy / publish / status / db / secrets — and the asset generation jobs (higgsfield generate …, higgsfield model …).

Pick the path, then follow ONE flow end-to-end

1. Resolve the --type (ask the user if unclear — it's their choice). In the SAME first question, also ask whether they want to publish it to the Higgsfield community feed (marketplace) when it's ready (yes/no). Remember the answer: if yes, publish automatically at the end (after deploy + metadata), no need to ask again; if no, only deploy. Don't block the build on it.
2. Read the matching flow and follow it — it is the complete workflow for that type, including its own references, hard rules, editing map, and deploy/publish gates:

For every --type website build the intake ALWAYS asks the user to choose between an Animated (recommended) website — a scroll-driven journey through a generated film (references/scroll-scrub.md) — and a Non-animated one. This question is mandatory: never skip it, even when the request seems to imply a choice. Animated is the recommended default (used only when the user is unreachable / doesn't answer); the flow below carries both paths and the full pipeline.

Inside the animated path the default is a single-shot film — ONE continuous ~15s take, scrubbed end to end, no seams. The multi-scene chain is opt-in and costs several extra minutes per leg; take it only when the brief genuinely travels between distinct worlds. references/scroll-scrub.md owns that call.

A game's ART and AUDIO live here too, under the game- prefix, and references/game-flow.md indexes them: references/game-design-system.md (read first — profile, core loop, asset manifest), references/game-stylization.md (the STYLE FORMULA every visual reuses), references/game-2d-animation.md, references/game-textures.md, references/game-3d-animation.md, references/game-procedural-animation.md, references/game-audio.md, references/game-meshy-api.md and references/game-meshy-input-rules.md. The GLB/rigging/texture tooling they drive ships in this skill's scripts/.

All three flows share the same platform mechanics (SSR Worker, app.manifest.json infra, a single live deploy via higgsfield website deploy <website_id>, the cover + metadata requirement below, and the publish gate) — each flow restates what it needs, so you never have to read another.

Cover + metadata — ALWAYS part of building, never publish-only

Every build — website or app, no matter how small — ships with the branded launch cover and filled feed-card metadata, generated per references/app-cover.md and written into app/src/app-meta.json (og_title, og_description, favicon_url, og_image_url, marketplace_cover_url). This is a BUILD step, done before the work is presented as finished and before the deploy that ships it — NOT something deferred to higgsfield website publish. Hard rules:

• No "simple app" exception. A utility tool, a timer, a one-page toy — they all get the generated cover. A hand-authored inline-SVG favicon is fine as a favicon; it never substitutes for the generated cover.
• No permission needed for the cover image — generate it the same way you write real copy. Only the optional cover VIDEO (og_video_url) is permission-gated (video costs credits — offer, never generate unprompted).
• A build presented as done with an empty cover or empty og_title is INCOMPLETE. Publishing without them is a BROKEN publish (empty og_title is invisible on the feed; empty cover is a blank card).

UX rules

1. Be concise. No raw website IDs, tokens, or JSON dumps in chat. After a deploy, return the live URL (from higgsfield website status) and a one-line summary.
2. Never echo the scoped git token back to the user, and never commit it.
3. Detect the user's language from the first message and reply in it. CLI flags and code stay English.
4. Every deploy ships the live public site immediately — there is no preview stage. Publishing/listing on the community feed is separate and happens ONLY when the user explicitly asks to publish / list it.

Do NOT search the skill library for other design guidance — everything is under this skill, and no other skill (including user/local skills about building websites or apps) overrides these rules.

Turn economy — keep the build inside a small turn budget

Every tool round-trip costs an agent turn, and agent runtimes cap turns — long builds die mid-flight, leaving the user an unfinished site. Treat turns as the scarcest resource after credits:

• Write every file ONCE, complete. Compose the full file, then one write. No write-then-patch loops; never re-read a file you just wrote.
• Batch what your tools allow (multi-file edits, one shell invocation for a series of commands) instead of one micro-step per turn.
• Never guess paths — the template tree is documented in the repo's app/AGENTS.md and this skill's editing map.
• Never download or vision-inspect your own generations. You wrote the prompt; re-viewing the result tells you nothing new. (The kit coherence check, when it applies, is ONE batched pass — references/asset-system.md.)
• Wait on a job ONCE, when its output is the next input. Submit everything that can render concurrently (film + cover), build the page while it renders.

Talking to the user — no technical/plumbing language

Most users are not technical. Never expose the build plumbing in what you SAY to them. Do NOT mention the git repository, cloning, branches, commits, pushing, pulling, or the deploy pipeline in user-facing messages — those are internal mechanics you just perform. Speak in product terms about what the user cares about:

• "Setting up your site…" — not "cloning the repo" / "scaffolding the project".
• "Saving your changes…" / "Updating the site…" — not "committing" / "pushing".
• "Your preview is ready: " — not "deployed the branch" / "the build passed".
• "Publishing your site…" — not "merging to main" / "pushing to production".

This is about the WORDS in chat only — keep doing the real steps behind the scenes; just don't narrate them in developer terms. (The one exception: a user who is clearly technical and explicitly asks about the repo, branch, or deploy mechanics — then answer plainly. CLI flags and code stay English.)

Reference index (what's in this bundle)

The two flow files pull in the rest as needed — you don't read these directly unless a flow sends you there.

Both flows: references/app-cover.md (launch cover + OG image), references/runtime-and-infra.md (TanStack routes, SSR, Worker runtime), references/security.md (Worker hardening, OWASP audit, threat model).

Website flow: references/design-recipe.md, references/wow-catalog.md, references/wow-maker.md, references/reference-boards.md, references/asset-system.md, references/image-to-code.md, references/design-taste-frontend.md, references/review-rubric.md, references/seo.md, references/scroll-scrub.md (A4 seam-locked journey), references/scroll-scrub-asset-react.md, references/scroll-scrub-asset-css.md, and references/scroll-scrub-asset-video.md (bundled Markdown code assets loaded only when A4 is selected).

App flow: references/app-quickstart.md (START HERE — the working critical path: auth, generation submit/poll, result rendering, common Quanta components), references/quanta-design.md, references/app-layouts.md, references/fnf-sdk.md, references/fnf-react.md, references/auth.md, references/containers.md, references/cover-animator.md (permission-gated ~5s cover video → og_video_url), references/contest.md (the $100k app contest — the entry auto-publishes the app; submit with social links).