higgsfield-websites

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
version: 0.12.0
name: higgsfield-websites
description: |
  Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references/website-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references/app-flow.md), `game` (realtime multiplayer rooms — references/game-flow.md). Routes to the right flow; each carries its own rules and deploy/publish gates.
  Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / portfolio", "make me a game", "deploy this site", "publish". Also owns GAME ART: "make a spritesheet", "tileable texture", "animate a 3D character", game music/SFX — see the game-* references.
  NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
argument-hint: "[what to build or edit] [--type website|app|game]"
allowed-tools: Bash
---

# 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.
  ```bash
  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.
  ```bash
  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`.
  ```bash
  higgsfield website create --type game --category arcade
  ```

**Generation is ALWAYS an app.** Any product that generates imag