higgsfield-websiteslisted

Build, edit, and deploy full-stack websites via the Higgsfield CLI (`higgsfield website …`). Each site is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). TWO product types, picked via `--type` on create: `website` (standalone, NO Higgsfield integration, independent brand, custom CSS — the image-grounded pipeline in references/website-flow.md) vs `app` (Sign in with Higgsfield + fnf SDK, Quanta + app layouts per references/app-flow.md). This file routes to the right flow; each flow carries its own workflow, references, hard rules, and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / tool / portfolio", "deploy this site", "edit my site", "publish", "ship to production". NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
jurislm/jurislm-tools · ★ 0 · Web & Frontend · score 62

Install: claude install-skill jurislm/jurislm-tools

# Higgsfield website builder (CLI) — two product types, two 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 two 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/video