Higgsfield website builder
Project ownership
A local repository request does not authorize creating a Higgsfield website or
moving the project into a cloud sandbox. Use this workflow for a requested
hosted product or a known Higgsfield site's edit; keep component-only work in
the user's existing codebase and toolchain.
You build ONE per-product Cloudflare Worker: a React 19 + TanStack Start app,
server-rendered, deployed as a single Worker at the product's own subdomain.
The project lives in app/ — every bun/build command runs from there.
The code is edited in the Higgsfield cloud sandbox with sandbox_exec, never on
a local machine. Read references/repo-and-sandbox.md before your first edit —
website_repo_access reserves a 15-minute editing lease. Commit and push progress
before the lease expires; checkout again if the sandbox was discarded.
THREE product types — the user picks, not you
create_website requires type, and it is the user's choice. When the
request does not make it obvious, ask once, up front, in the same message as the
publish question below.
type: "website" — a standalone product with NO Higgsfield integration and
no AI generation of any kind inside the product (not via Higgsfield, not
via another provider): no Sign in with Higgsfield, no fnf SDK. It gets a fully
independent brand — own palette, type, and chrome, custom Tailwind/CSS. Never
import @higgsfield/quanta/*, and never put a "Powered by Higgsfield" badge on
the page. The user's brand is the only brand there.
→ references/website-flow.md
type: "app" — a product tightly integrated with Higgsfield: its users Sign
in with Higgsfield and generate images/videos through the fnf SDK, on their own
Higgsfield credits. An app must look like a Higgsfield product: UI built with
Quanta, starting from the starter layout picked at create.
→ references/app-flow.md
type: "game" — a browser game 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 and takes
no template. Single-player counts — set minPlayers: 1.
→ references/game-flow.md
Each flow is complete for its type and pulls in the shared references below, so
you never have to read another flow.
Generation is ALWAYS an app. Any product that generates images, video, or
audio for its own users runs on Higgsfield — build it as type: "app". Never
offer the user a "bring your own image/video API key" path for a website; it does
not exist. (An ordinary non-generation third-party API — payments, maps, email —
with the user's own key is unrelated to this rule and fine in a website.)
Quick tells: "landing page / portfolio / marketing site / SaaS with its own
users, no AI generation" → website. "generates images, video, or audio, or ties
into Higgsfield models, credits, or history" → app. "playable, rounds, score,
players" → game.
The create call
Resolve all of this BEFORE calling create_website — type, category, and
template are fixed at create and are not editable afterwards.
category — required. Call list_website_categories for the valid slugs
and pass the closest one (other when nothing fits). A game takes a game genre
(arcade, puzzle, shooter, …).
subdomain — always set it. It becomes the slug, so the live URL is
<subdomain>.<host>. Derive it from the product's name or purpose
(lumen-notes, pixelforge), more than 4 characters, lowercase letters, digits
and single hyphens only. Omit it only when the user explicitly asks for a random
one. Reserved labels (api, www, app) and taken subdomains are rejected —
try a close variant.
template — REQUIRED for type: "app", optional for type: "website",
never for type: "game". App and website template names are not
interchangeable; a cross-kind name is rejected.
- App:
studio (full creative workspace), preset (pick-a-style-then-generate,
also the base for wizards), app-detail (a single tool's landing page). A
custom bare shell exists but is used ONLY when the user says "use custom
template" — never pick it yourself.
- Website:
scroll-scrub for an animated site (the scrub engine arrives
pre-built), omitted for a non-animated one.
The chosen app layout ships as REAL CODE already wired as the home page. You
adapt it in place — thread the product's real data through the shipped
layout. Never rebuild the screen or swap layouts. After cloning, read
app/src/layouts/AGENTS.md and app/src/components/AGENTS.md: the layout is the
UI shell with demo placeholders, and the deliverable is the user's actual product
with complete business logic. A template that merely renders is NOT done.
Order of work
- Resolve
type (ask if unclear). In that SAME first message, ask one more
yes/no: publish it to the Higgsfield community feed when it is ready? Remember
the answer — if yes, you publish at the end without asking again. Don't block
the build on it.
- Read the matching flow reference and follow it end to end. Each flow carries
its own intake, references, hard rules, and gates, so you never need to read
another one.
- Ship it: cover + metadata, deploy, then publish if they said yes.
The reference set
The flow you picked tells you when to open each of these. Do not read them all
up front.
Every build
| Reference |
What it owns |
repo-and-sandbox.md |
The sandbox_exec edit loop, repo access, deploy/status/publish, db and secrets. Read before the first edit. |
asset-system.md |
The generated asset kit — what to generate per tier, and the post-processing this surface does not have |
app-cover.md |
The branded 3:2 launch cover and OG images |
security.md |
Input validation, authz, secrets, safe queries |
seo.md |
Metadata, sitemaps, structured data, crawlability |
runtime-and-infra.md |
The Worker runtime, routing, D1/R2/KV wiring |
containers.md |
Heavy or long-running work off the Worker |
contest.md |
The app contest entry rules |
type: "website"
| Reference |
What it owns |
design-recipe.md, reference-boards.md |
Concept spine, palette, boards |
design-taste-frontend.md |
The craft bar — what separates a real design from a templated one |
wow-catalog.md, wow-maker.md |
The signature interaction, and how to build it |
image-to-code.md |
Turning an approved board into matching code |
scroll-scrub.md |
The animated-website scrub journey |
scroll-scrub-asset-video.md, -asset-react.md, -asset-css.md |
Its encode, React, and CSS halves |
review-rubric.md |
The gate before deploy |
type: "app"
| Reference |
What it owns |
app-quickstart.md |
The critical path: auth → SDK client → submit/poll → render |
app-layouts.md |
Picking and adapting the starter layout |
quanta-design.md |
The design system and its UX rules |
fnf-sdk.md, fnf-react.md |
Generation, media, profile, credits |
auth.md |
Sign in with Higgsfield, server-side re-checks |
cover-animator.md |
The optional animated cover |
type: "game"
| Reference |
What it owns |
game-design-system.md |
Game profile, core loop, asset manifest |
game-stylization.md |
The style formula every visual prompt reuses |
game-2d-animation.md, game-textures.md |
Spritesheets and tiles |
game-audio.md |
Music, SFX, voice |
Cover + metadata — part of building, never publish-only
Every build — website, app, or game, however small — ships with a branded launch
cover and filled feed-card metadata written into app/src/app-meta.json
(og_title, og_description, favicon_url, og_image_url,
marketplace_cover_url). See references/app-cover.md. This is a BUILD
step, done before you present the work as finished and before the deploy that
ships it — not something deferred to publish_website.
- No "simple app" exception. A utility, a timer, a one-page toy — all get the
generated cover. A hand-authored inline-SVG favicon is fine as a favicon; it
never substitutes for the cover.
- No permission needed for the cover image — generate it the same way you
write real copy. Only an optional cover VIDEO is permission-gated, because
video costs credits: offer it, never generate it unprompted.
- A build presented as done with an empty cover or empty
og_title is
INCOMPLETE, and publishing it is a broken publish — an empty og_title is
invisible on the feed and an empty cover is a blank card.
Deploy is the only thing that ships
deploy_website builds from the pushed branch and ships the live site. There
is no separate preview stage. Commit and push everything first, then deploy — and
deploy again after ANY later change. publish_website does not deploy; it only
lists the already-live build on the community feed.
Everything you need is under this skill. Do not go looking for other website or
design guidance, and no other skill overrides these rules.
What this client cannot do
Say so plainly when it comes up; never promise one of these and improvise.
- No image-to-3D. No mesh generation, rigging, or animation clips. Games
built here are 2D, and a "3D" hero is the layered-depth rig in
references/wow-catalog.md, not a model the user can spin.
- No background remover, AI upscaler, or uncrop. Generate at the size and
aspect you need, and get a transparent subject by prompting it on a flat
chroma ground and keying it out in
sandbox_exec. references/asset-system.md
has the commands.
Turn economy
Every tool round-trip costs a turn and clients cap them, so a long build can die
mid-flight and leave the user an unfinished site. Turns are the scarcest resource
after credits:
- Write every file ONCE, complete. Compose the whole file, then one write. No
write-then-patch loops, and never re-read a file you just wrote.
- Never guess paths. The tree is documented in the repo's
app/AGENTS.md and
in this skill's flows; searching a guessed directory is a wasted turn that ends
in "not found".
- Never download or vision-inspect your own generations. You wrote the prompt;
re-viewing the result tells you nothing new.
- Submit everything that can render concurrently (page assets and the cover)
with one
generate_image_batch, build the page while it renders, then collect
with one jobs_wait and one show_generation_by_ids.
- Tool errors cost double — the failed turn plus the retry. Array params take
real JSON arrays, never stringified ones.
Talking to the user
Most users are not technical. Never expose the plumbing in what you SAY. Do not
mention the git repository, cloning, branches, commits, pushing, or the deploy
pipeline in user-facing messages — perform them silently and speak in product
terms:
- "Setting up your site…" — not "cloning the repo".
- "Saving your changes…" — not "committing and pushing".
- "Your site is live: " — not "the build passed".
This is about the words in chat only; keep doing the real steps. The one
exception is a clearly technical user who explicitly asks about the repo or the
deploy mechanics — then answer plainly.
Repository credentials are handled by the service and never returned. Do not ask
for Git tokens or application secret values in chat.
1---2name: website-builder3description: >4 Build and publish a complete website, web app or browser game on5 Higgsfield, or edit/redeploy an existing Higgsfield-hosted site. Use when the6 requested deliverable is that hosted product or a change to it. Components,7 snippets and fixes for a user's existing local codebase remain repository8 work; mentioning React, a website or a UI element does not request a hosted9 build. Exclude copywriting, external-site review, standalone media and10 read-only site administration. After a valid activation, collect missing11 product type and scope.12metadata:13 source: https://skillmd.com/skills/jhamidun/website-builder14---1516# Higgsfield website builder1718## Project ownership1920A local repository request does not authorize creating a Higgsfield website or21moving the project into a cloud sandbox. Use this workflow for a requested22hosted product or a known Higgsfield site's edit; keep component-only work in23the user's existing codebase and toolchain.2425You build ONE per-product Cloudflare Worker: a **React 19 + TanStack Start** app,26**server-rendered**, deployed as a single Worker at the product's own subdomain.27The project lives in **`app/`** — every `bun`/build command runs from there.2829The code is edited in the Higgsfield cloud sandbox with `sandbox_exec`, never on30a local machine. Read `references/repo-and-sandbox.md` before your first edit —31website_repo_access reserves a 15-minute editing lease. Commit and push progress32before the lease expires; checkout again if the sandbox was discarded.3334## THREE product types — the user picks, not you3536`create_website` requires `type`, and it is the **user's** choice. When the37request does not make it obvious, ask once, up front, in the same message as the38publish question below.3940- **`type: "website"`** — a standalone product with NO Higgsfield integration and41 **no AI generation of any kind** inside the product (not via Higgsfield, not42 via another provider): no Sign in with Higgsfield, no fnf SDK. It gets a fully43 independent brand — own palette, type, and chrome, custom Tailwind/CSS. Never44 import `@higgsfield/quanta/*`, and never put a "Powered by Higgsfield" badge on45 the page. The user's brand is the only brand there.46 → **`references/website-flow.md`**47- **`type: "app"`** — a product tightly integrated with Higgsfield: its users Sign48 in with Higgsfield and generate images/videos through the fnf SDK, on their own49 Higgsfield credits. An app must look like a Higgsfield product: UI built with50 **Quanta**, starting from the starter layout picked at create.51 → **`references/app-flow.md`**52- **`type: "game"`** — a browser game on the game template, where the game itself53 is six pure functions in `app/src/logic.js` and the platform already owns54 sockets, rooms, and persistence. Requires a game genre as `category` and takes55 **no** template. Single-player counts — set `minPlayers: 1`.56 → **`references/game-flow.md`**5758Each flow is complete for its type and pulls in the shared references below, so59you never have to read another flow.6061**Generation is ALWAYS an app.** Any product that generates images, video, or62audio for its own users runs on Higgsfield — build it as `type: "app"`. Never63offer the user a "bring your own image/video API key" path for a website; it does64not exist. (An ordinary non-generation third-party API — payments, maps, email —65with the user's own key is unrelated to this rule and fine in a website.)6667Quick tells: "landing page / portfolio / marketing site / SaaS with its own68users, no AI generation" → website. "generates images, video, or audio, or ties69into Higgsfield models, credits, or history" → app. "playable, rounds, score,70players" → game.7172## The create call7374Resolve all of this BEFORE calling `create_website` — `type`, `category`, and75`template` are fixed at create and are not editable afterwards.7677- **`category`** — required. Call `list_website_categories` for the valid slugs78 and pass the closest one (`other` when nothing fits). A game takes a game genre79 (`arcade`, `puzzle`, `shooter`, …).80- **`subdomain`** — always set it. It becomes the slug, so the live URL is81 `<subdomain>.<host>`. Derive it from the product's name or purpose82 (`lumen-notes`, `pixelforge`), more than 4 characters, lowercase letters, digits83 and single hyphens only. Omit it only when the user explicitly asks for a random84 one. Reserved labels (`api`, `www`, `app`) and taken subdomains are rejected —85 try a close variant.86- **`template`** — REQUIRED for `type: "app"`, optional for `type: "website"`,87 never for `type: "game"`. App and website template names are not88 interchangeable; a cross-kind name is rejected.89 - App: `studio` (full creative workspace), `preset` (pick-a-style-then-generate,90 also the base for wizards), `app-detail` (a single tool's landing page). A91 `custom` bare shell exists but is used ONLY when the user says "use custom92 template" — never pick it yourself.93 - Website: `scroll-scrub` for an animated site (the scrub engine arrives94 pre-built), omitted for a non-animated one.9596The chosen app layout ships as REAL CODE already wired as the home page. You97**adapt it in place** — thread the product's real data through the shipped98layout. Never rebuild the screen or swap layouts. After cloning, read99`app/src/layouts/AGENTS.md` and `app/src/components/AGENTS.md`: the layout is the100UI shell with demo placeholders, and the deliverable is the user's actual product101with complete business logic. A template that merely renders is NOT done.102103## Order of work1041051. Resolve `type` (ask if unclear). In that SAME first message, ask one more106 yes/no: publish it to the Higgsfield community feed when it is ready? Remember107 the answer — if yes, you publish at the end without asking again. Don't block108 the build on it.1092. Read the matching flow reference and follow it end to end. Each flow carries110 its own intake, references, hard rules, and gates, so you never need to read111 another one.1123. Ship it: cover + metadata, deploy, then publish if they said yes.113114## The reference set115116The flow you picked tells you when to open each of these. Do not read them all117up front.118119**Every build**120121| Reference | What it owns |122|---|---|123| `repo-and-sandbox.md` | The `sandbox_exec` edit loop, repo access, deploy/status/publish, db and secrets. **Read before the first edit.** |124| `asset-system.md` | The generated asset kit — what to generate per tier, and the post-processing this surface does not have |125| `app-cover.md` | The branded 3:2 launch cover and OG images |126| `security.md` | Input validation, authz, secrets, safe queries |127| `seo.md` | Metadata, sitemaps, structured data, crawlability |128| `runtime-and-infra.md` | The Worker runtime, routing, D1/R2/KV wiring |129| `containers.md` | Heavy or long-running work off the Worker |130| `contest.md` | The app contest entry rules |131132**`type: "website"`**133134| Reference | What it owns |135|---|---|136| `design-recipe.md`, `reference-boards.md` | Concept spine, palette, boards |137| `design-taste-frontend.md` | The craft bar — what separates a real design from a templated one |138| `wow-catalog.md`, `wow-maker.md` | The signature interaction, and how to build it |139| `image-to-code.md` | Turning an approved board into matching code |140| `scroll-scrub.md` | The animated-website scrub journey |141| `scroll-scrub-asset-video.md`, `-asset-react.md`, `-asset-css.md` | Its encode, React, and CSS halves |142| `review-rubric.md` | The gate before deploy |143144**`type: "app"`**145146| Reference | What it owns |147|---|---|148| `app-quickstart.md` | The critical path: auth → SDK client → submit/poll → render |149| `app-layouts.md` | Picking and adapting the starter layout |150| `quanta-design.md` | The design system and its UX rules |151| `fnf-sdk.md`, `fnf-react.md` | Generation, media, profile, credits |152| `auth.md` | Sign in with Higgsfield, server-side re-checks |153| `cover-animator.md` | The optional animated cover |154155**`type: "game"`**156157| Reference | What it owns |158|---|---|159| `game-design-system.md` | Game profile, core loop, asset manifest |160| `game-stylization.md` | The style formula every visual prompt reuses |161| `game-2d-animation.md`, `game-textures.md` | Spritesheets and tiles |162| `game-audio.md` | Music, SFX, voice |163164## Cover + metadata — part of building, never publish-only165166Every build — website, app, or game, however small — ships with a branded launch167cover and filled feed-card metadata written into `app/src/app-meta.json`168(`og_title`, `og_description`, `favicon_url`, `og_image_url`,169`marketplace_cover_url`). See `references/app-cover.md`. This is a BUILD170step, done before you present the work as finished and before the deploy that171ships it — not something deferred to `publish_website`.172173- **No "simple app" exception.** A utility, a timer, a one-page toy — all get the174 generated cover. A hand-authored inline-SVG favicon is fine *as a favicon*; it175 never substitutes for the cover.176- **No permission needed** for the cover image — generate it the same way you177 write real copy. Only an optional cover VIDEO is permission-gated, because178 video costs credits: offer it, never generate it unprompted.179- A build presented as done with an empty cover or empty `og_title` is180 INCOMPLETE, and publishing it is a broken publish — an empty `og_title` is181 invisible on the feed and an empty cover is a blank card.182183## Deploy is the only thing that ships184185`deploy_website` builds from the **pushed** branch and ships the live site. There186is no separate preview stage. Commit and push everything first, then deploy — and187deploy again after ANY later change. `publish_website` does not deploy; it only188lists the already-live build on the community feed.189190Everything you need is under this skill. Do not go looking for other website or191design guidance, and no other skill overrides these rules.192193## What this client cannot do194195Say so plainly when it comes up; never promise one of these and improvise.196197- **No image-to-3D.** No mesh generation, rigging, or animation clips. Games198 built here are 2D, and a "3D" hero is the layered-depth rig in199 `references/wow-catalog.md`, not a model the user can spin.200- **No background remover, AI upscaler, or uncrop.** Generate at the size and201 aspect you need, and get a transparent subject by prompting it on a flat202 chroma ground and keying it out in `sandbox_exec`. `references/asset-system.md`203 has the commands.204205## Turn economy206207Every tool round-trip costs a turn and clients cap them, so a long build can die208mid-flight and leave the user an unfinished site. Turns are the scarcest resource209after credits:210211- **Write every file ONCE, complete.** Compose the whole file, then one write. No212 write-then-patch loops, and never re-read a file you just wrote.213- **Never guess paths.** The tree is documented in the repo's `app/AGENTS.md` and214 in this skill's flows; searching a guessed directory is a wasted turn that ends215 in "not found".216- **Never download or vision-inspect your own generations.** You wrote the prompt;217 re-viewing the result tells you nothing new.218- **Submit everything that can render concurrently** (page assets and the cover)219 with one `generate_image_batch`, build the page while it renders, then collect220 with one `jobs_wait` and one `show_generation_by_ids`.221- **Tool errors cost double** — the failed turn plus the retry. Array params take222 real JSON arrays, never stringified ones.223224## Talking to the user225226Most users are not technical. Never expose the plumbing in what you SAY. Do not227mention the git repository, cloning, branches, commits, pushing, or the deploy228pipeline in user-facing messages — perform them silently and speak in product229terms:230231- "Setting up your site…" — not "cloning the repo".232- "Saving your changes…" — not "committing and pushing".233- "Your site is live: <url>" — not "the build passed".234235This is about the words in chat only; keep doing the real steps. The one236exception is a clearly technical user who explicitly asks about the repo or the237deploy mechanics — then answer plainly.238239Repository credentials are handled by the service and never returned. Do not ask240for Git tokens or application secret values in chat.