Merge remote-tracking branch 'origin/main'

Author: arsuhf

higgsfield-websites/SKILL.md

@@ -116,9 +116,22 @@ are rejected — if that happens, try a close variant.
    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.
+
 | Type | Flow |
 |---|---|
-| `--type website` | **`references/website-flow.md`** — phased pipeline: intake → concept → reference boards → asset system → build-to-boards → motion → cover + metadata → mechanical gate → deploy |
+| `--type website` | **`references/website-flow.md`** — phased pipeline (animated website by default): intake → concept → reference boards → asset system → build-to-boards → motion → cover + metadata → mechanical gate → deploy |
 | `--type app` | **`references/app-flow.md`** — the Quanta toolkit, the six code layouts, fnf SDK + auth + D1 contract, launch cover + metadata, publish gate |
 
 Both flows share the same platform mechanics (SSR Worker, `app.manifest.json`
@@ -162,6 +175,25 @@ 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

higgsfield-websites/references/app-cover.md

@@ -84,7 +84,12 @@ same-origin. Downscale: hero ≤2k, cutouts ~800px, icons ~256px.
 
 **Cinema tier adds:**
 
-7. **Hero video — cinema tier REQUIRES the scroll-scrub, not the loop.** A
+7. **Hero video — cinema tier REQUIRES the scroll-scrub, not the loop.**
+   (The DEFAULT website is the **animated website** — the full-site seam-locked
+   chain in `references/scroll-scrub.md` — whose MP4 chain replaces this single
+   hero scrub; see the note after this list. This §7 single-hero recipe is the
+   hero mechanic only when the user explicitly asked for a non-animated-website
+   treatment.) A
    static image + CSS effect is the floor; an autoplay ambient loop is barely
    above it (it moves, but the user's scroll does nothing — passive motion
    doesn't register as craft). The cinema-tier Tier-1 carrier is the
@@ -112,7 +117,7 @@ same-origin. Downscale: hero ≤2k, cutouts ~800px, icons ~256px.
      (dense collage heroes) or video generation failed per the failure rules;
      say so in the report. A mid-page band may still use a loop freely.
 
-For **A4 — Seam-locked scroll scrub**, read
+For the **animated website (A4 — Seam-locked scroll scrub, the default)**, read
 `references/scroll-scrub.md` and let its entry still, exact deployed-segment
 posters, and chained MP4s replace the ordinary single hero scrub above. Those
 posters also satisfy hero/content imagery for their chapters. Continue the
@@ -179,8 +184,11 @@ brand property they now own.
 - **Submit early, never idle.** All kit jobs go in right after the boards are
   chosen; poll between build steps. A build that waits on renders is
   mis-sequenced.
-- **Coherence check:** when the kit lands, view the assets together (read the
-  images). Any piece whose grade/palette fights the boards gets re-generated
+- **Coherence check — ONE batched vision pass, maximum.** When the kit lands,
+  view the assets TOGETHER in one pass — never one look per asset, never
+  re-inspecting something already viewed. The storyboard and the scroll-scrub
+  film are EXEMPT: you authored their prompts and the user reviews the
+  storyboard. Any piece whose grade/palette fights the boards gets re-generated
   with the hexes named harder. A mixed-grade asset kit reads cheaper than no
   assets. **Off-grade video budget: ONE re-roll.** If the re-roll drifts
   scene/composition (video models often do), keep the better take and

higgsfield-websites/references/asset-system.md

@@ -1,10 +1,13 @@
 # review-rubric — Phase 5 mechanical gate
 
 §A runs BEFORE deploy and is a completion gate, not a suggestion. Most items
-are verified by grep/code inspection; when the brief selects A4, item 9e also
-requires its interactive runtime checks in local preview before the final
-deploy. There is no post-deploy visual/screenshot review — this mechanical
-gate is the only verification.
+are verified by grep/code inspection. **Item 9f is the hard machine gate for the
+animated-website default: a website that ships without the scroll-scrub component
++ scene media (and without an explicit `non-animated` choice in the brief) FAILS, no matter
+how polished the rest is** — this is the single most common miss, so run 9f every
+time. For the animated website, item 9e adds its interactive runtime checks in
+local preview before the final deploy. There is no post-deploy visual/screenshot
+review — this mechanical gate is the only verification.
 
 ## §A. Mechanical gate (pre-deploy, code-level)
 
@@ -72,11 +75,14 @@ Check each item; fix every hit before deploying.
    build's six identity axes (palette family, type pairing, hero
    architecture, Tier-1 technique, CTA garments, corner language) and this
    build differs on ≥4; the rationed garments (drawing underline, hover
-   flood-fill, framed block) appear at most once page-wide combined; the
-   Tier-1 technique carries a `wow-catalog.md` ID and is interactive (not a
-   passive loop) on cinema/spectacle.
-9e. **A4 seam-locked scroll scrub (conditional)** — when the brief selects
-   A4, verify every media segment has a first-frame poster extracted from the
+   flood-fill, framed block) appear at most once page-wide combined. On the
+   `non-animated` path the Tier-1 technique carries a `wow-catalog.md` ID and is
+   interactive (not a passive loop); on the default `animated-website` path the
+   Tier-1 technique IS the scroll-scrub animated website (enforced by 9f) — a
+   generic wow-catalog ID does NOT satisfy the default path.
+9e. **Animated website — A4 seam-locked scroll scrub (every website by default;
+   skip only if the user explicitly opted out)** — verify every media segment
+   has a first-frame poster extracted from the
    exact deployed clip; chapter copy is server-rendered in semantic document
    flow (not hidden until a viewport callback); `prefers-reduced-motion`
    performs no video fetch and shows the complete static story; desktop and
@@ -89,6 +95,30 @@ Check each item; fix every hit before deploying.
    media. Inspect each seam immediately before/after in both scroll directions
    and test source swapping, a fast mobile flick, and unmount/remount in local
    preview before final deploy.
+9f. **Animation mode gate (machine-verifiable — HARD, every website).** This is
+   the completion gate for the animated-website default; a site that passes every
+   other check but this one is NOT done. Steps:
+   1. `grep -n "^Animation mode:" app/design-brief.md` — there MUST be exactly
+      one such line. Zero matches → FAIL (the brief never declared the state).
+   2. If the value is **`animated-website`**, ALL of these must hold, or FAIL:
+      - the scroll-scrub component exists —
+        `ls app/src/components/scroll-scrub/scroll-scrub.tsx` succeeds — and is
+        actually imported/rendered by a route (grep for its import);
+      - real film shipped — at least ONE clip (`single-shot` ships exactly
+        one; a `multi-leg` journey ships one per leg) under
+        `app/public/assets/**/*.mp4` (the seam-locked chain), each with a
+        first-frame poster (item 9e);
+      - the brief carries the journey block (Journey scenes + Camera
+        architecture A/B) written in Phase 0.
+      A website on this path with no scroll-scrub component or no scene MP4s is
+      the failure mode this gate exists to catch — do NOT deploy it; go build the
+      camera journey.
+   3. If the value is **`non-animated`**, the line MUST record the user's choice
+      (an intake pick or a verbatim request). No scroll-scrub artifacts are
+      required; instead confirm the site clears the `wow-maker.md` craft floor and
+      any chosen `wow-catalog.md` technique is actually built (9d). A
+      `non-animated` with no recorded user choice → FAIL (treat as
+      `animated-website` and go back to step 2).
 10. **Section plan honored** — the built page matches `app/design-brief.md`'s
     section plan (families, order, no consecutive family repeats). If the plan
     changed during the build, the brief was updated to match.