* 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.
8.6 KiB
dataviz-countup — Data-Viz / Count-Up
intent: Make numbers and charts the hero — a count-up ring/number, a trend chart, a tilted stat/card grid — and traverse the data instruments with a camera that pushes THROUGH them (or scrolls across them) to land on one hero metric, so the data itself carries the argument.
roles served
- Problem (from
problem-dataviz-pushthrough/ #9 Problem_1): quantifies the pain with real-looking instruments — a count-up ring → a trend chart → a stat grid — the camera pushing THROUGH each object into the next to dramatize a worsening / large-scale problem ("X% of people struggle with…"). - Product_Intro (from
product-intro-dataviz-scroll-reveal/ #19 Product_Intro_06): a confident "look at the result / the data" open — hard-cut from a hook word into a perspective-tilted grid of data-viz cards, then a hands-off camera scroll lands one glowing hero metric while a kinetic tagline assembles word-by-word. - Hook (from
hook-counter-burst): a cold-open hook on ONE dramatic statistic — the frame opens dark and empty, 3–5 thematic icons puncture in clustered at center, then the headline number EXPLODES upward in size as the icons fling outward to their marks (the count-up and the spread are one beat), closed by a slow camera lean-in. Kinetic from frame 1.
duration: ~4–12s (Hook ~4s · Product_Intro ~6s · Problem ~11–12s)
shot structure Data-viz field on [bg color] (dark or light, soft corner glows); [gradient A→B] brand stroke on charts/rings; clean sans-serif white/dark text; a continuous camera move runs underneath that traverses 2–3 data instruments and resolves on a hero metric. One instrument per beat; the camera carries the cut.
-
Scene 1 (0.0–Xs): the first data instrument establishes centered — a
[stat]reads as the hero. A bold center number COUNTS UP[start]→[end]while its transform scale grows to the static final type size, with[stat label]below; its paired graphic (a circular progress RING sweeping to[pct]with a[gradient]stroke, or a bar/fill) animates in on the SAME ease so number + graphic land as one beat. Supporting[avatar/object]elements pop in with spring overshoot into a scattered glowing orbit; a[headline]fades up. A very slow continuous camera zoom-in runs throughout. -
Scene 2 (Xs–Ys): the camera traverses to the next instrument and that instrument animates — a
[gradient]trend line / area chart DRAWS left→right on grid lines (Problem), or off-center cards SCROLL away as the layout glides (Product_Intro). The arriving[stat-2]number counts up / the chart resolves. -
Scene 3 / Scene N (…–end): the camera lands the
[hero metric card](big number + label + delta + rising chart) in dead-center; a soft[accent]glow blooms behind it; the move reaches its peak then eases to a settled, slightly wider composition with the hero centered and supporting cards flanking it. HOLD on the final frame. -
Variant — Problem (push-THROUGH, count-up → trend → grid): Scene 1 is a centered circular progress ring + count-up center number with scattered glowing
[avatar/object]orbit. Scene 2 is a fast camera PUSH-IN straight through the center of the ring (ring, number, orbiting elements scale up and fly out of frame) into a rounded[card]holding[stat-2 header]over a[gradient]line chart with grid lines + translucent area fill that draws left→right; camera pushes through then settles. Scene 3: camera PANS to a second[card]whose number counts up, holding a grid of the[avatar/object]elements — a subset dim/blur while the rest receive[accent]circular checkmark badges that SPRING-POP; camera settles to the end. The traversal is z-depth push-through between instruments. -
Variant — Product_Intro (scroll-to-hero + word-by-word tagline): a brief opener — Scene 0 (~0.0–0.85s): a full-frame
[hero-color orb]with a bold white[hook phrase]over it; static shimmer, then HARD CUT. Scene 1 cuts to a slightly perspective-TILTED grid of[data-viz / product cards](charts, heatmaps, stat cards with deltas + source footers) with[tagline word 1]centered; the grid begins SCROLLING (e.g. toward upper-left) with its tilt held. Scene 2: the grid keeps scrolling so the[hero metric card]glides into dead-center as off-center cards slide away;[tagline word 1]translates out and[word 2]rises in from a frame edge. Scene 3: hero card settles centered,[accent]glow blooms behind it, camera PUSHES IN slightly;[word 2]holds near it. Scene 4:[word 2]slides out, the final[tagline word]drops in from the opposite edge above the still-glowing hero, push-in peaks. Scene 5: overlay type clears, camera eases BACK OUT to a settled wider tilted composition — hero centered with glow, supporting cards flanking. The traversal is a hands-off camera SCROLL across a tilted card plane (no cursor, no clicks) + a one-word-at-a-time kinetic headline + push-in-then-out bookend.
motion vocabulary count-up number with transform-scale growth on the value; circular progress-ring sweep; growth bar / progress fill; gradient trend-line + area-fill left→right draw; spring-overshoot pop-in of scattered glowing avatar/object elements; perspective-tilted card grid; directional grid scroll (cards glide in/out of center); hero-card centering; soft accent glow bloom behind the hero; slow continuous zoom-in; fast camera push-IN / push-THROUGH the center of an instrument; lateral/vertical camera pan between cards; gentle push-in that peaks then eases back out to a wider settle; selective dim/blur of a subset + spring-pop checkmark badges; full-frame hook orb → hard cut; kinetic tagline assembled word-by-word (each word drops/rises from a frame edge, prior word slides out).
rule mapping (motion verb → rules/<id>.md)
- count-up number whose transform scale grows with the value →
counting-dynamic-scale(primary text rule) - circular progress-ring sweep (the ring fill) →
stat-bars-and-fills(ring form) — its draw mechanics delegate to →svg-path-draw - growth bars / progress fill paired beside a number →
stat-bars-and-fills(primary data rule) - gradient trend-line / area-chart left→right draw →
svg-path-draw(a path/line draws itself) - spring-overshoot pop-in of the avatar/object elements →
spring-pop-entrance(elastic overshoot); the scattered-ring layout of glowing avatars/objects →avatar-cloud-network; if they keep drifting/orbiting →orbit-3d-entry - spring-pop
[accent]checkmark badges →spring-pop-entrance - perspective-tilted card grid (tilt held static while content moves) →
3d-page-scroll - directional scroll across the tilted card plane (cards glide in/out of center) →
3d-page-scroll(scroll) +viewport-change(lateral/vertical pan form) - hero metric card centering (scroll/pan lands the target dead-center) →
coordinate-target-zoom(target lands at viewport center) /viewport-change - hard-cut from the hook orb into the grid →
scale-swap-transition - kinetic tagline assembled word-by-word →
kinetic-beat-slam(one onset grid, distinct per-word entrances) - slow continuous zoom-in + push-THROUGH the instruments + lateral/vertical pan between cards + push-in-then-out bookend →
multi-phase-camera(see camera modifier) - soft accent glow BLOOM behind the hero card →
ambient-glow-bloom(un-triggered soft glow/bloom behind the static hero element — distinct frompress-release-spring's press-triggered glow andasr-keyword-glow's word-timed envelope) - selective dim/blur of a SUBSET of grid items (focus-falloff on the non-highlighted cards) →
depth-of-field-blur(selective per-element blur/dim to spotlight the highlighted cards — the same focus-falloff rule used inconstellation-hub)
camera modifier: The camera is the through-line that traverses the data instruments — one camera wrapper sequenced by multi-phase-camera, with each stop targeted via coordinate-target-zoom onto the focal instrument/card.
- Problem — push-THROUGH: a slow continuous zoom-in (drift overlay) plus a fast PUSH-IN straight through the center of one instrument into the next (
multi-phase-camera, Steady-push pattern), then a lateral/vertical PAN to the final card. Z-depth push-through is the signature (distinguishes it from a flat pan-tour). - Product_Intro — scroll-to-hero + bookend push: a hands-off directional SCROLL across the tilted card plane (
3d-page-scrollscroll /viewport-changepan) that lands the hero card center, then a gentle push-in that PEAKS and eases BACK OUT to a wider settle (multi-phase-camera, Bookend-pull pattern). No cursor, no clicks — the camera does the navigating.