higgsfield-websites

Agent skill from higgsfield-ai/skills.

higgsfield-ai ↓ 17k

Claude Code

View source ↗

What it does

--type website — a standalone product with NO Higgsfield integration
--type app — a product tightly integrated with Higgsfield: its users
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,
Allowed characters only — lowercase letters, digits, and single hyphens
No "simple app" exception. A utility tool, a timer, a one-page toy —
No permission needed for the cover image — generate it the same way you

Requirements & configuration

higgsfield website create requires --type, and it is the USER'S choice —
metadata), no need to ask again; if no, only deploy. Don't block the build
restates what it needs, so you never have to read the other one.
2. Never echo the scoped git token back to the user, and never commit it.

Configuration: PATH

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

Source

Repository: https://github.com/higgsfield-ai/skills

higgsfield-websites FAQ

What does the higgsfield-websites skill do?

| 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). --type website — a standalone product with NO Higgsfield integration --type app — a product tightly integrated with Higgsfield: its users

What does higgsfield-websites require?

higgsfield website create requires --type, and it is the USER'S choice — metadata), no need to ask again; if no, only deploy. Don't block the build restates what it needs, so you never have to read the other one. 2. Never echo the scoped git token back to the user, and never commit it. Configuration keys: PATH.

How do I install higgsfield-websites?

Run: npx -y skills add https://github.com/higgsfield-ai/skills --skill higgsfield-websites --agent claude-code — the source lives at github.com/higgsfield-ai/skills.

Maintain higgsfield-websites?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![higgsfield-websites on getagentictools](https://getagentictools.com/badge/skills/higgsfield-ai-skills-higgsfield-websites.svg)](https://getagentictools.com/skills/higgsfield-ai-skills-higgsfield-websites?ref=badge)

npx agentictools info skills/higgsfield-ai-skills-higgsfield-websites

The second line is the CLI lookup for this page — handy in READMEs and docs.