Files
hyperframes/skills/hyperframes-animation/rules/counting-dynamic-scale.md
T
WaterrrForever b9be0b2625 feat(skills,studio,media-use): the intent layer, review loop, and user memory — BRIEF.md, companion mode, recipes; /website-to-video folds into /product-launch-video (#2133)
* feat(studio,cli): per-frame board comments, self-refreshing storyboard, status-aware preview landing

Per-frame comment boxes on the storyboard board batch into
.hyperframes/frame-comments.json (a resubmit wins per frame; unconsumed
comments on other frames are kept). Submitted-but-unconsumed comments
stay visible — a toolbar banner plus a per-tile echo — until the agent
consumes the file; the banner also says what to do next (reply anything
in the agent chat).

The board keeps itself current: GET /projects/:id/signature exposes the
watcher-cached project signature, the storyboard payload carries the
signature it was derived from, and the view polls at 2s (hidden tabs
skipped, re-checked on visibility), refetching in place with no loading
flash. Posters bake the signature into their URL so tiles fill in as
sketches land and a poster that failed mid-write retries on the next
version; the empty state upgrades itself when STORYBOARD.md appears,
and its handoff prompt now points the agent at the review loop and uses
the parser's real status vocabulary (outline, not planned).

preview lands the browser on the storyboard view while the board is the
review surface — any frame built, or pure planning (srcs declared, none
on disk yet) — and on the timeline once the video is assembled.

* feat(skills): the review loop — plan, sketch, build as one shared process

hyperframes-core/references/review-loop.md is the single source for the
three-pass collaborative review: the plan proposed on a live board
(§ 1), wireframe sketches marked built with one layout question (§ 2 —
real words on plain blocks, run no CLI; a confirmed board is itself a
valid deliverable when the user asked for a storyboard, not a video),
the build dressing confirmed layouts (§ 3, worker or inline), and the
final look (§ 4). Autonomous runs skip every gate and keep one question
before render.

The three narrative workflows' Steps 3/4/6 collapse to references plus
their sketch stand-ins (captured-asset blocks for product-launch-video,
plain code panels for pr-to-video); the confirmed-sketch handoff stays
in each frame-worker prompt. general-video plans on a board for
multi-scene narrative pieces in collaborative mode — its sketch pass is
layout-before-animation with the user watching. The router treats
"I want a storyboard" as a process request rather than a route, and
closes exploratory intake by recommending a route plus how the run will
review.

The supporting contracts land next door: the comments channel (silent
submit, one reply picks it up, check the file before the words) in
brief-contract § 1; the sidecar schema and the built status rung in
storyboard-format; the mode question asked first and alone in the three
workflows' Step 0.

* feat(media-use): user memory — remembered preferences and frozen recipes

Two tiers of memory on media-use's existing two-tier storage split.

Preferences (lightweight): confirmed brief answers — destination, aspect,
language, mode, voice, style preset — recorded to the project's
.media/preferences.json (committed, the team inherits it) and promoted
to the personal ~/.media/preferences.json once the same value is
confirmed in two different projects (a sightings ledger accumulates the
cross-project evidence user-side, since project files can't see each
other). prefs.mjs get/record; merge reads project-over-user; a changed
value restarts its provenance.

Recipes (heavyweight): one approved run frozen as a named, versioned
bundle — frame.md, the storyboard skeleton (structure kept: durations,
transitions, srcs, Video direction; statuses reset to outline; content
blanked to per-frame fill-ins naming the beat's role), and the confirmed
brief values. Named folders, not content hashes: re-freezing bumps
version and archives <name>@v<N>; a freeze is already confirmed, so it
promotes to the user tier immediately. recipe.mjs freeze/list/use, plus
resolve --type recipe --entity <name> delegating like grade/lut.

16 new node --test cases; the media-use lib suite is 168/168.

* feat(skills): wire user memory into the brief and the review loop

brief-contract § 2 gains Remembered defaults: read the merged
preferences before Round 2 and let a remembered value become the
recommended option with a receipt naming its source project. Memory
changes the default, never the question — every ask-marked field still
gets asked, and what the request says this time beats what was picked
last time. Record only what the user actually confirmed (a defaulted
voice nobody chose is not an answer; a "go" that accepts the
recommended defaults is). The first record announces itself once;
after that the receipts carry the reminder. In autonomous mode a
remembered value becomes the decided value, receipt included.

The three narrative workflows read the remembered defaults before
Round 2, record the confirmed answers at the Step 0 gate, record the
chosen preset at the Step 2 gate (pr-to-video excepted — its preset is
fixed), and fall back to the remembered voice when the request names
none. general-video's discovery reads the same defaults.

Recipes wire in at both ends: Step 0 checks for a matching recipe
before the mode question — one question, plural-aware, and adopting
one fills the brief, skips the design step, and drafts the storyboard
from the frozen skeleton while every review gate still runs. The
review loop's final look (§ 4) offers the freeze once after approval,
and the confirmation teaches the recall phrase — the name is something
the system reminds the user of, never something they must remember.
The router recognizes a named recipe or "like last time" as a route.

* docs(skills): the sketch pass names check, not the deprecated validate

* feat(skills): intent-layer references — process, route briefs, capability menu, BRIEF.md format

* feat(media-use): brief skeleton as the recipe's fourth artifact; flow/storyboard preference keys

* feat(skills): the intent layer conducts every brief — workflows execute BRIEF.md

* feat(skills): retire the mode preference key; sync catalog surfaces for intent layer

* refactor(skills): dedupe router vs intent-layer guidance — one owner per rule

* feat(skills): the design ask — own spec, pick by eye from showcases, or defer

* docs(skills): the design ask says the honest line on capture routes

* feat(skills): product-launch-video absorbs website-to-video as the tour angle

* refactor(skills): keep product-launch-video pristine — a tour is brief intent, not a pipeline branch

* feat(skills): production loop + genre lenses; general-video goes freeform (route yours, laws hold)

* refactor(skills): /hyperframes is the front door - route tables and scope lists leave the workflows

* docs(skills): review-loop pass across skill catalog

* fix(cli): pass project dir to openStudioBrowser in background-server path

* feat(skills): add pitch-round reference - verbalized sampling concept gate

* feat(skills): wire pitch round into intent layer - completeness triage + route eligibility

* feat(skills): editorial capability recommendations, handoff disciplines, menu-probe split

* feat(skills): pitches carry their machinery; source-only-formed requests pitch the telling

* feat(skills): companion goes director - ceiling treatment plus blueprint/rule citation discipline

* fix(scripts): sandbox npx-leak guard - private npm global prefix keeps npx on the branch CLI

* chore(skills): resync manifest hash after formatter pass reflowed general-video tables

* fix(skills): recipe freeze reads workflow from BRIEF.md; style_preset records require workflow scope

Two holes found by a live companion-run freeze: the agent-supplied --workflow
contradicted the run's actual workflow (recipe.json said faceless-explainer,
brief-skeleton said general-video), and the style_preset lookup missed because
the preference had been recorded under the bare key.

- freezeRecipe resolves the workflow from BRIEF.md frontmatter; the flag is a
  fallback for briefless projects and a contradicting flag is ignored (noted).
- recordPreference refuses a bare style_preset — the scoped key is the only
  writable shape; freeze tolerates legacy bare records via read fallback.
- review-loop § 4 / media-use SKILL / brief-format wording follow the machinery.
2026-07-15 21:19:14 +08:00

9.7 KiB
Raw Blame History

name, description, metadata
name description metadata
counting-dynamic-scale Counter animation where the value counts up while transform scale grows to its final size, creating escalating visual weight without per-frame text reflow.
tags
counter, counting, scale, transform, number, dynamic, emphasis

Counting with Dynamic Scale

A number counts from A → B while its transform scale grows to the final size. The effect preserves escalating visual weight without tweening font-size or forcing text layout on every frame.

How It Works

A single paused timeline drives two synchronized tweens:

  1. The numeric value (rendered as DOM text via onUpdate)
  2. The counter transform (scale: START_SCALEscale: 1)

As the number gets bigger, the text grows in place — visually communicating “this is impressive” while keeping the final font size static in CSS.

Easing

Pick by drama desired (the choice is discrete; coefficient is implicit):

GSAP ease Effect
power1.out Mild — slight deceleration
power2.out Default — ease-out, fast start slow end
power3.out Strong — dramatic deceleration recommended
expo.out Very dramatic — almost stops at the end

power3.out matches the polynomial 1 - (1-x)^k family at k ≈ 2.5 — number rushes up then slows dramatically at the peak.

HTML

<div
  class="scene"
  data-composition-id="counter-scene"
  data-start="0"
  data-duration="3"
  data-track-index="0"
>
  <div class="counter-wrap">
    <span class="counter" id="counter">0</span><span class="counter-suffix">{suffix}</span>
  </div>
  <div class="counter-label">{label}</div>
</div>

CSS

.scene {
  position: relative;
  width: 100%;
  height: 100%;
  display: grid;
  place-items: center;
  background: {bgColor};
}

.counter-wrap {
  display: flex;
  align-items: baseline;
  justify-content: center;
  gap: 8px;
  /* Fixed-width container prevents layout shift as digit count changes */
  width: {counterContainerWidth};
  text-align: center;
}

.counter {
  font-family: {font};
  font-weight: 900;
  color: {textColor};
  /* MANDATORY — tabular-nums keeps digits the same width */
  font-variant-numeric: tabular-nums;
  /* Final size is static. GSAP animates transform scale, not font-size. */
  display: inline-block;
  font-size: {endSize};
  transform-origin: center center;
  letter-spacing: -2px;
  line-height: 1;
}

.counter-suffix {
  font-family: {font};
  font-weight: 800;
  color: {accentColor};
  font-size: {suffixSize};
  opacity: 0;
  transform: translateY(20px);
}

.counter-label {
  margin-top: 24px;
  font-family: {font};
  font-size: {labelSize};
  color: {mutedTextColor};
  text-align: center;
}

GSAP Timeline

<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
<script>
  window.__timelines = window.__timelines || {};
  const tl = gsap.timeline({ paused: true });

  const counter = document.getElementById("counter");
  const state = { value: 0 };
  const START_SCALE = START_SIZE / END_SIZE;

  // Count value. onUpdate changes text only.
  tl.to(
    state,
    {
      value: TARGET_VALUE,
      duration: COUNT_DUR,
      ease: COUNT_EASE,
      onUpdate: () => {
        counter.textContent = Math.round(state.value).toLocaleString();
      },
    },
    0,
  );

  // Visual growth uses a compositor transform and shares the count timing.
  tl.fromTo(
    counter,
    { scale: START_SCALE },
    { scale: 1, duration: COUNT_DUR, ease: COUNT_EASE },
    0,
  );

  // Suffix slides in after count completes
  tl.to(
    ".counter-suffix",
    {
      opacity: 1,
      y: 0,
      duration: SUFFIX_DUR,
      ease: `back.out(${SUFFIX_BOUNCE_FACTOR})`,
    },
    COUNT_DUR,
  );

  // Label fades in early
  tl.from(
    ".counter-label",
    {
      opacity: 0,
      y: 12,
      duration: LABEL_DUR,
      ease: "power2.out",
    },
    LABEL_AT,
  );

  window.__timelines["counter-scene"] = tl;
</script>

How to Choose Values

  • TARGET_VALUE — the number the counter lands on

    • Effects: 23 digits reads best at hero size; 4+ digits requires wider container
    • Constraints: must fit horizontally at END_SIZE inside the container
  • START_SIZE / END_SIZE — design inputs used once to calculate START_SCALE

    • Range: START_SIZE ≈ 4060 % of END_SIZE
    • Effects: smaller START_SIZE = more dramatic growth; larger = subtler
    • Constraints: set CSS font-size to END_SIZE; never tween either value. END_SIZE × digit count must fit the container width without clipping
  • COUNT_DUR — count + scale tween duration

    • Range: 1.22.5 s
    • Effects: shorter = aggressive; longer = settled, gives reading time
    • Constraints: must allow the eye to read the digits scrolling past; below ~0.8 s reads as a flash
  • COUNT_EASE — shared ease for the value and transform scale

    • Discrete choice: power2.out, power3.out, expo.out (see table above)
    • Constraint: avoid back.out / elastic.out — overshoot reads as unstable data
  • SUFFIX_DUR — duration of the suffix slide-in

    • Range: 0.30.6 s
    • Effects: shorter = snap; longer = floats
    • Constraints: must fire after the count lands (started at COUNT_DUR), not during
  • SUFFIX_BOUNCE_FACTOR — back.out coefficient on the suffix entry

    • Range: 1.42.0
    • Effects: 1.4 = small overshoot; 2.0 = bouncy
  • LABEL_AT / LABEL_DUR — when and how long the label fades in

    • Range: LABEL_AT < COUNT_DUR / 2 (label arrives before count peaks); LABEL_DUR 0.40.7 s

Variations

Direct innerText tween (no proxy object)

The GSAP inspector reads innerText directly, so a number-only counter can skip the state proxy:

tl.to(
  counter,
  { innerText: TARGET_VALUE, duration: COUNT_DUR, ease: COUNT_EASE, snap: { innerText: 1 } },
  0,
);

snap: { innerText: 1 } keeps it integer. Keep the proxy-object onUpdate form above when you need locale formatting (toLocaleString) or suffix logic. In either form, the synchronized scale remains a separate transform tween at timeline position 0.

3D depth entry

Combine with translateZ for parallax-style depth on entry:

tl.from(
  ".counter",
  {
    z: -300,
    duration: 0.6,
    ease: "power2.out",
    // requires parent or .counter itself to have perspective set
  },
  0,
);

CSS prerequisite:

.counter-wrap {
  perspective: 1000px;
}
.counter {
  transform-style: preserve-3d;
}

Multi-stat coordinated reveal

For 3 stats counting in parallel, share the SAME ease and duration so they finish together — visually a chord, not arpeggio. Each stat usually also needs a paired graphic (bar / ring / stars) — don't stop at the number; see stat-bars-and-fills.md:

["#stat1", "#stat2", "#stat3"].forEach((sel, i) => {
  const obj = { v: 0 };
  tl.to(
    obj,
    {
      v: TARGETS[i],
      duration: COUNT_DUR,
      ease: COUNT_EASE,
      onUpdate: () => (document.querySelector(sel).textContent = Math.round(obj.v)),
    },
    0,
  ); // same start position — chord
});

Key Principles

  • Synchronized value + scale at one timeline position so the two tweens share an ease and stay coordinated
  • font-variant-numeric: tabular-nums is mandatory — without it digit-count transitions (e.g. 9 → 10 → 100) cause visible jitter as glyph widths change
  • Fixed-width container as belt-and-suspenders — even with tabular-nums, glyph shape changes can shift baselines
  • Grow in place, don't bounce — the number should feel weighty, not springy. power3.out ends at exact value; back.out overshoots and feels cartoonish
  • Start small enough to grow noticeably (~50 % of final size); end large enough to feel decisive but not clip viewport
  • Never set fontSize in onUpdate — final type size is static CSS; only the transform changes per frame
  • Suffix animates AFTER the count, not during — gives the number its own beat
  • Label is BIG TEXT, not a page-style tiny caption — for VIDEO, a small paragraph-style caption below a hero-size number reads as visual noise. Use display-size, uppercase, tracked label so the layout is "two-line big-text"; the label is part of the headline, not a footer.

Critical Constraints

  • tabular-nums mandatory — required CSS for layout stability
  • Timeline must be paused: gsap.timeline({ paused: true }). Never tl.play()
  • Registry key = data-composition-id: window.__timelines["counter-scene"] must match scene root
  • onUpdate mutates DOM: HF runtime seeks the timeline frame-by-frame, so onUpdate runs on every seek call. Keep onUpdate work O(1) — set text only, with no style writes or DOM creation
  • Math.round not Math.floor — half-way through the final integer should display the final value briefly, not the previous one
  • Avoid back.out / elastic.out for the counter itself — overshoot makes the number look unstable (it's data, not decoration)

Combinations

  • stat-bars-and-fills.mdthe paired graphic beside the number (growth bars / progress ring / star wipe). A stat scene is usually BOTH rules: the count-up here + a fill there. Give the fill the same ease and duration so number and graphic land as one beat.
  • svg-path-draw.md — icons drawing in around the number
  • center-outward-expansion.md — related icons exploding outward synced to count peak

Pairs with HF skills

  • /hyperframes-animation — timeline + onUpdate API
  • /hyperframes-core — composition wiring, data-* attributes
  • /hyperframes-clihyperframes lint to verify scene