Files
skills/public/showcase-walkthrough.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

624 lines
35 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>showcase-walkthrough</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/showcase-walkthrough.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/showcase-walkthrough">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/showcase-walkthrough.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>showcase-walkthrough</h1><p class="lede">App Walkthrough showcase — step-by-step guided tour with animated cursor, Hotspot pulses, Tooltip explanations, scroll transitions, and ZoomReveal on key moments across multiple screens. Journey-driven from video-profile.yaml. Produces a 30–90s 16:9 MP4 via the AppWalkthrough composition.</p><h1>Showcase: App Walkthrough</h1>
<p>Specialist skill for the <strong>App Walkthrough</strong> showcase. Activated by the <code>remotion-pro</code> orchestrator when the user selects showcase <code>8</code> (<code>walkthrough</code>, <code>tutorial</code>, <code>passo-a-passo</code>, <code>step-by-step</code>, <code>tour</code>). Receives a context object with <code>video_profile</code>, <code>brand_voice</code>, <code>remotion</code>, and <code>briefing</code>.</p>
<hr>
<h2>Overview</h2>
<p>The App Walkthrough showcase is the most comprehensive video format — a full guided tour through an entire user journey. An animated cursor navigates the UI step-by-step, <code>Hotspot</code> pulses highlight targets before each click, <code>Tooltip</code> cards explain each action, <code>ScreenScroll</code> transitions move within pages, and <code>ZoomReveal</code> emphasizes key outcomes. Multiple screens are woven into one continuous, smooth flow.</p>
<p><strong>Best for:</strong> product onboarding videos, sales demos, tutorial content, user guides, help center videos, investor walkthroughs, support documentation.</p>
<p><strong>Composition ID:</strong> <code>AppWalkthrough</code> <strong>Aspect ratio:</strong> 16:9 (1920×1080) <strong>FPS:</strong> 30 <strong>Duration range:</strong> 30–90 seconds (900–2700 frames)</p>
<hr>
<h2>Components Used</h2>
<p>| Component | File | Purpose in video | |---|---|---| | <code>BrowserFrame</code> | <code>components/BrowserFrame.tsx</code> | Wraps each screen in browser chrome with URL bar | | <code>MobileFrame</code> | <code>components/MobileFrame.tsx</code> | Wraps screens in iPhone/Android shell (if device=mobile) | | <code>AnimatedCursor</code> | <code>components/AnimatedCursor.tsx</code> | Moves cursor from previous position to next target with spring easing | | <code>ScreenScroll</code> | <code>components/ScreenScroll.tsx</code> | Scrolls within a tall screenshot between actions | | <code>ScreenshotOverlay</code> | <code>components/ScreenshotOverlay.tsx</code> | Crossfades between different app screens on navigation | | <code>ZoomReveal</code> | <code>components/ZoomReveal.tsx</code> | Zooms into result or key UI state after important actions | | <code>AnimatedText</code> | <code>components/AnimatedText.tsx</code> | Hook title, step labels, and CTA text | | <code>BackgroundGradient</code> | <code>components/BackgroundGradient.tsx</code> | Branded background gradient | | <code>ProgressBar</code> | <code>components/ProgressBar.tsx</code> | Accent-colored progress bar at bottom | | <code>BrandWatermark</code> | <code>components/BrandWatermark.tsx</code> | Handle overlay at watermark position |</p>
<h3>Hotspot (inline component)</h3>
<p><code>Hotspot</code> is rendered as an inline animated div inside the <code>step</code> scene — a pulsing ring that appears at <code>cursor_target</code> coordinates 0.5s before the cursor arrives. Implementation:</p>
<pre><code class="lang-typescript">// Pulsing ring at target position
// Uses interpolate(frame, [0, 15, 30], [0, 1, 0]) for scale pulse
// Color: brand.colors.accent at 60% opacity
// Size: 40×40px, border-radius: 50%, position: absolute</code></pre>
<h3>Tooltip (inline component)</h3>
<p><code>Tooltip</code> is an animated floating label rendered inside the <code>step</code> scene, appearing after the cursor click. Implementation:</p>
<pre><code class="lang-typescript">// Glassmorphic card (blur: 8px, opacity: 0.85) positioned near cursor_target
// Offsets: if target.y &gt; 540 → tooltip above (y - 80), else below (y + 60)
// Contains: action icon + tooltip text (max 60 chars)
// Entry animation: fade-in + slide-up over 12 frames
// Duration: stays visible for remainder of step scene</code></pre>
<hr>
<h2>Scene Flow Template</h2>
<p>Default sequence for a medium-pacing, 3-screen journey with 2 actions per screen:</p>
<pre><code>Scene 1 — Hook (0s–3s, frames 0–89)
AnimatedText: &quot;Here&#x27;s how [product] works&quot;
Subtext: journey name or product tagline, animation: fade-in delay 15
Scene 2 — Screen 1 Intro (3s–5s, frames 90–149)
BrowserFrame/MobileFrame slides in from bottom
ScreenshotOverlay: first screenshot fades in
AnimatedText: step label appears (e.g., &quot;Step 1: Sign Up&quot;)
Scene 3 — Step 1a (5s–9s, frames 150–269)
AnimatedCursor moves from center → target element
Hotspot pulses at target for 15 frames
Click effect fires (ripple)
Tooltip appears: action description
ScreenshotOverlay crossfades to next state
Scene 4 — Step 1b (scroll) (9s–12s, frames 270–359) [if page is scrollable]
ScreenScroll: page scrolls down to next interaction target
Pause at key content for 20 frames
Scene 5 — Transition (12s–14s, frames 360–419)
ScreenshotOverlay crossfades to Screen 2
Step counter increments: &quot;Step 2: [label]&quot;
Scene 6 — Step 2a (14s–18s, frames 420–539)
AnimatedCursor: moves from top-left → target element
Hotspot pulses → click → ripple
Tooltip: action description
ScreenshotOverlay: next state loads
Scene 7 — Zoom Reveal (18s–21s, frames 540–629) [1 zoom per journey]
ZoomReveal on most important result (confirmation screen, success state, key metric)
highlightBox: true, highlightColor: brand.colors.accent
Tooltip: outcome description (&quot;Your dashboard is ready!&quot;)
Scene 8 — Screen 3 (21s–27s, frames 630–809) [if 3rd screen exists]
[Repeat cursor + hotspot + click + tooltip pattern]
Scene 9 — CTA (27s–31s, frames 810–929)
Device frame fades out
AnimatedText: CTA headline bounces in
Accent pill: product URL / &quot;Start free trial&quot;
BrandWatermark visible</code></pre>
<p><strong>Pacing multipliers per step type:</strong></p>
<ul><li><code>fast</code>: cursor travel = 1.5s, tooltip = 1s, scroll = 2s</li><li><code>medium</code>: cursor travel = 2s, tooltip = 1.5s, scroll = 3s (default)</li><li><code>slow</code>: cursor travel = 3s, tooltip = 2.5s, scroll = 4s</li></ul>
<hr>
<h2>Storyboard Generation Rules</h2>
<h3>Step 1 — Parse the briefing</h3>
<pre><code>product_name → explicit in briefing OR brand-voice.yaml → brand.name
journey_name → explicit in briefing OR first journey in video-profile.yaml
device → &quot;mobile&quot; / &quot;phone&quot; → MobileFrame
→ &quot;browser&quot; / &quot;desktop&quot; / default → BrowserFrame
pacing → explicit in briefing → video-profile.yaml → style.pacing → &quot;medium&quot;
cta_text → explicit in briefing → brand-voice.yaml → cta.default
zoom_on → explicit &quot;zoom on [screen/element]&quot; → auto-select (see Step 4)</code></pre>
<h3>Step 2 — Load journey</h3>
<pre><code>IF briefing specifies journey name:
Find in video-profile.yaml journeys[] (case-insensitive, fuzzy match)
IF not found: list available journeys, ask user to select
ELSE IF video-profile.yaml has one journey:
Use it automatically
ELSE IF video-profile.yaml has multiple journeys:
Ask: &quot;Which journey should the walkthrough follow? [list names]&quot;
ELSE (no journeys defined):
Ask user to define steps inline (screen path + action + tooltip)</code></pre>
<h3>Step 3 — Build WalkthroughStep list</h3>
<p>For each <code>screen</code> in the selected journey:</p>
<pre><code class="lang-typescript">// Map each screen to a WalkthroughStep
{
screenName: screen.name,
screenshot: screen.screenshot,
actions: screen.actions.map(action =&gt; mapActionToWalkthroughAction(action))
}</code></pre>
<p><strong>Action string → WalkthroughAction mapping:</strong></p>
<p>| Action string pattern | type | target heuristic | tooltip | |---|---|---|---| | <code>clica [target]</code> / <code>click [target]</code> | <code>click</code> | element center heuristic | <code>&quot;Click [target]&quot;</code> | | <code>clica em [target]</code> | <code>click</code> | element center heuristic | <code>&quot;Click on [target]&quot;</code> | | <code>scroll até [section]</code> / <code>scroll to</code> | <code>scroll</code> | { x: 960, y: 540 } | <code>&quot;Scroll to [section]&quot;</code> | | <code>digita [text]</code> / <code>type [text]</code> | <code>type</code> | input field heuristic | <code>&quot;Type your [field]&quot;</code> | | <code>preenche [field]</code> / <code>fill [field]</code> | <code>type</code> | input field heuristic | <code>&quot;Fill in [field]&quot;</code> | | <code>navega para [page]</code> / <code>navigate to</code> | <code>click</code> | nav link heuristic | <code>&quot;Go to [page]&quot;</code> | | <code>hover em [element]</code> / <code>hover [element]</code> | <code>hover</code> | element center heuristic | <code>&quot;Hover over [element]&quot;</code> | | <code>submit</code> / <code>confirma</code> / <code>save</code> | <code>click</code> | submit button heuristic | <code>&quot;Confirm and continue&quot;</code> |</p>
<p><strong>Target coordinate heuristics (1920×1080, browser frame, content area ~1760×900 offset 80,120):</strong></p>
<pre><code>&quot;Sign Up&quot; / &quot;Get Started&quot; / &quot;CTA button&quot; → { x: 960, y: 500 }
&quot;Login&quot; / &quot;Sign In&quot; → { x: 960, y: 420 }
&quot;Email field&quot; → { x: 760, y: 380 }
&quot;Password field&quot; → { x: 760, y: 460 }
&quot;Submit&quot; / &quot;Continue&quot; / &quot;Next&quot; → { x: 960, y: 600 }
&quot;Navigation menu item&quot; (generic) → { x: 300, y: 160 }
&quot;Search bar&quot; → { x: 760, y: 180 }
&quot;Profile / Avatar&quot; → { x: 1750, y: 160 }
&quot;Settings&quot; → { x: 1700, y: 160 }
&quot;Dashboard / Home card&quot; → { x: 480, y: 520 }
&quot;Sidebar item&quot; → { x: 160, y: 400 }
&quot;Modal close&quot; → { x: 1400, y: 300 }
&quot;Dropdown option&quot; → { x: 760, y: 480 }
Fallback (unknown) → { x: 960, y: 540 }</code></pre>
<h3>Step 4 — Select zoom target</h3>
<p>The walkthrough should have exactly <strong>one</strong> <code>ZoomReveal</code> scene. Placement rule:</p>
<pre><code>IF briefing specifies &quot;zoom on [screen/element]&quot;:
Use that screen, estimate element coordinates
ELSE:
Auto-select the screen with the most significant outcome:
Priority 1: screen labeled &quot;Dashboard&quot;, &quot;Success&quot;, &quot;Result&quot;, &quot;Confirmation&quot;
Priority 2: last screen in the journey (final state)
Priority 3: screen with action &quot;zoom em&quot; / &quot;zoom on&quot;
ZoomReveal target: { x: 600, y: 300, width: 720, height: 400 } (center of content area)
zoomLevel: 2.0
highlightBox: true
highlightColor: brand.colors.accent</code></pre>
<h3>Step 5 — Calculate total duration</h3>
<pre><code>hook_duration = 3s
screen_intro_duration = 2s (for first screen only)
per_cursor_travel_s = pacing_cursor[pacing] (1.5 / 2.0 / 3.0)
per_hotspot_s = 0.5 (always)
per_click_effect_s = 0.3 (always)
per_tooltip_s = pacing_tooltip[pacing] (1.0 / 1.5 / 2.5)
per_scroll_action_s = pacing_scroll[pacing] (2.0 / 3.0 / 4.0)
per_type_action_s = max(1.5, text.length × 0.08)
transition_s = 1.5 (between screens)
zoom_reveal_s = 3s (one per video)
cta_duration = 4s
per_step_s = cursor_travel + hotspot + click_effect + tooltip (per action)
+ scroll (if action.type === &#x27;scroll&#x27;)
+ type_time (if action.type === &#x27;type&#x27;)
screen_section_s = screen_intro (screen 1 only) + sum(per_step_s for all actions)
total_s = hook + sum(screen_section_s) + transitions × (screens - 1) + zoom + cta
IF total_s &lt; 30: extend tooltip durations by 1.5×, add intro text for each screen
IF total_s &gt; 90: reduce tooltip durations to minimum, merge same-screen actions</code></pre>
<h3>Step 6 — Output storyboard YAML</h3>
<pre><code class="lang-yaml"># storyboard.yaml — App Walkthrough
showcase: AppWalkthrough
product: &quot;[product_name]&quot;
journey: &quot;[journey_name]&quot;
device: &quot;[browser|mobile]&quot;
pacing: &quot;[fast|medium|slow]&quot;
total_duration_s: [calculated]
step_count: [total action count across all screens]
scenes:
- id: hook
type: hook
duration_s: 3
text: &quot;Here&#x27;s how [product_name] works&quot;
subtext: &quot;[journey_name or tagline]&quot;
animation: scale-in
- id: screen-1-intro
type: step
duration_s: 2
step:
screenName: &quot;[screen.name]&quot;
screenshot: &quot;[screen.screenshot]&quot;
actions: []
text: &quot;Step 1: [screen.name]&quot;
animation: slide-up
- id: step-1-1
type: step
duration_s: [calculated]
step:
screenName: &quot;[screen.name]&quot;
screenshot: &quot;[screen.screenshot]&quot;
actions:
- type: &quot;[click|scroll|hover|type]&quot;
target: { x: [N], y: [N] }
tooltip: &quot;[tooltip text]&quot;
duration: [frames]
# next_screenshot for crossfade after click
next_screenshot: &quot;[next state screenshot if available]&quot;
- id: transition-1-2
type: transition
duration_s: 1.5
text: &quot;Step 2: [next screen name]&quot;
animation: crossfade
- id: step-2-1
type: step
duration_s: [calculated]
step:
screenName: &quot;[screen 2 name]&quot;
screenshot: &quot;[screen 2 screenshot]&quot;
actions:
- type: click
target: { x: [N], y: [N] }
tooltip: &quot;[tooltip text]&quot;
duration: [frames]
- id: zoom-reveal
type: step
duration_s: 3
step:
screenName: &quot;[result screen name]&quot;
screenshot: &quot;[result screenshot]&quot;
actions: []
zoom:
target: { x: 600, y: 300, width: 720, height: 400 }
zoomLevel: 2.0
highlightBox: true
text: &quot;[outcome description]&quot;
- id: cta
type: cta
duration_s: 4
text: &quot;[cta headline]&quot;
subtext: &quot;[product URL or &#x27;Start free trial&#x27;]&quot;
animation: bounce</code></pre>
<hr>
<h2>Composition Mapping</h2>
<p>Convert storyboard to Remotion props for the <code>AppWalkthrough</code> composition:</p>
<h3>Frame calculation</h3>
<pre><code>scene.duration_s × 30 = scene.durationFrames
startFrame[N] = sum of durationFrames[0..N-1]</code></pre>
<h3>Props object structure</h3>
<pre><code class="lang-typescript">// AppWalkthroughProps (from types.ts)
{
brand: {
name: &quot;[product_name]&quot;,
handle: brand_voice.brand.handle,
colors: {
primary: design_tokens.primary_color,
secondary: design_tokens.secondary_color,
background: &quot;#0F0F1A&quot;,
text: &quot;#FFFFFF&quot;,
accent: design_tokens.accent_color,
},
watermark_position: &quot;bottom-right&quot;,
},
deviceType: &quot;[browser|mobile]&quot;,
deviceConfig: {
browser: &quot;chrome&quot;,
device: &quot;iphone15&quot;,
darkMode: true,
},
showProgressBar: true,
showWatermark: true,
scenes: [
// hook
{
type: &quot;hook&quot;,
startFrame: 0,
durationFrames: 90,
text: &quot;Here&#x27;s how [product] works&quot;,
subtext: &quot;[journey name or tagline]&quot;,
animation: &quot;scale-in&quot;,
},
// step scenes (one per action, or grouped by screen)
{
type: &quot;step&quot;,
startFrame: [N],
durationFrames: [N],
text: &quot;Step [N]: [screen name]&quot;,
step: {
screenName: &quot;[screen name]&quot;,
screenshot: &quot;[path/to/screenshot.png]&quot;,
actions: [
{
type: &quot;click&quot;,
target: { x: 960, y: 500 },
tooltip: &quot;Click &#x27;Get Started&#x27; to begin&quot;,
duration: 60, // frames for this action
},
],
},
},
// transition
{
type: &quot;transition&quot;,
startFrame: [N],
durationFrames: 45,
text: &quot;Step [N]: [next screen name]&quot;,
animation: &quot;wipe&quot;,
},
// zoom (one per video)
{
type: &quot;step&quot;,
startFrame: [N],
durationFrames: 90,
text: &quot;[outcome description]&quot;,
step: {
screenName: &quot;[result screen]&quot;,
screenshot: &quot;[result screenshot path]&quot;,
actions: [], // no cursor for zoom scene
},
},
// cta
{
type: &quot;cta&quot;,
startFrame: [N],
durationFrames: 120,
text: &quot;[cta headline]&quot;,
subtext: &quot;[URL or trial text]&quot;,
animation: &quot;bounce&quot;,
},
],
}</code></pre>
<h3>Cursor path interpolation between steps</h3>
<p>When building <code>AnimatedCursorProps.path</code> for each action, the cursor&#x27;s starting position is the previous action&#x27;s <code>target</code>. For the first action, start from screen center <code>{ x: 960, y: 540 }</code>.</p>
<pre><code>path[0] = previous_target (or {x: 960, y: 540} for first action)
path[1] = current action.target with action: &quot;move&quot; (intermediate point if needed)
path[2] = current action.target with action: &quot;click&quot; / &quot;hover&quot;</code></pre>
<p>Add intermediate path points for long diagonal travel (distance &gt; 400px):</p>
<pre><code>midpoint = { x: (start.x + end.x) / 2, y: start.y, action: &quot;move&quot;, delay: 5 }</code></pre>
<hr>
<h2>Config Reading</h2>
<h3>From video-profile.yaml</h3>
<p>| Field | Used for | |---|---| | <code>design_tokens.primary_color</code> | <code>brand.colors.primary</code>, BrowserFrame bar | | <code>design_tokens.accent_color</code> | Hotspot color, ProgressBar, CTA pill, ZoomReveal highlight | | <code>design_tokens.heading_font</code> | step label font-family | | <code>assets.screenshots_dir</code> | prepended to all screenshot paths | | <code>assets.logo_path</code> | hook scene overlay if present | | <code>device_frames[]</code> | validate device choice | | <code>journeys[*]</code> | source of all screens, screenshots, actions | | <code>style.pacing</code> | cursor/tooltip/scroll duration multipliers | | <code>style.theme</code> | background and frame color strategy |</p>
<h3>From brand-voice.yaml</h3>
<p>| Field | Used for | |---|---| | <code>brand.name</code> | product_name fallback, hook text | | <code>brand.handle</code> | <code>brand.handle</code> in watermark | | <code>brand.tagline</code> | hook subtext fallback | | <code>cta.default</code> | CTA text fallback | | <code>automation.autonomy</code> | output bundle level (manual/semi/auto) |</p>
<h3>Briefing overrides (highest priority)</h3>
<p>Any explicit value in the user&#x27;s briefing (journey name, device, pacing, CTA text, zoom target, specific step tooltip text) takes precedence over both YAML files.</p>
<hr>
<h2>Render Command</h2>
<p>After generating the composition props, return to the orchestrator with:</p>
<pre><code class="lang-yaml">composition_id: AppWalkthrough
props: { ...AppWalkthroughProps JSON... }</code></pre>
<p>The orchestrator renders using the discovered Remotion CLI:</p>
<pre><code class="lang-bash">cd &quot;${REMOTION_PROJECT}&quot; &amp;&amp; npx remotion render src/index.ts AppWalkthrough &quot;${OUTPUT_DIR}/video.mp4&quot; \
--props=&#x27;{&quot;brand&quot;:{...},&quot;scenes&quot;:[...],&quot;deviceType&quot;:&quot;browser&quot;}&#x27; \
--fps=30</code></pre>
<p>For multi-platform (auto autonomy), the orchestrator also runs a 9:16 variant for social:</p>
<pre><code class="lang-bash">npx remotion render src/index.ts AppWalkthrough &quot;${OUTPUT_DIR}/video-9x16.mp4&quot; \
--width=1080 --height=1920 --props=&#x27;...&#x27; --fps=30</code></pre>
<hr>
<h2>Briefing Collection UI</h2>
<p>When the orchestrator routes here, display this briefing prompt:</p>
<pre><code>APP WALKTHROUGH SHOWCASE
─────────────────────────────────────────────────────────
I&#x27;ll create a step-by-step guided tour of your product
with cursor navigation, hotspot pulses, and tooltip labels.
Product name:
&gt; [e.g. &quot;&quot; or leave blank to use brand-voice.yaml]
Journey to walk through (from video-profile.yaml):
[list available journey names]
&gt; [select by name or number, or type &quot;custom&quot; to define steps]
Device frame: [browser / mobile] (default: browser)
&gt;
CTA text (optional):
&gt; [e.g. &quot;Start free at .app&quot;]
Pacing: [fast / medium / slow] (default: medium)
&gt;
Zoom focus (optional — which screen to zoom into):
&gt; [e.g. &quot;dashboard&quot; or &quot;confirmation screen&quot; or leave blank for auto]
─────────────────────────────────────────────────────────</code></pre>
<p>If user selects &quot;custom&quot;, collect steps inline:</p>
<pre><code>CUSTOM STEPS — Define your walkthrough
Step 1:
Screenshot path: &gt; [e.g. assets/screenshots/home.png]
Screen name: &gt; [e.g. &quot;Landing Page&quot;]
Actions (one per line, blank to finish):
&gt; [e.g. &quot;click Sign Up&quot; or &quot;scroll to pricing&quot;]
&gt; [e.g. &quot;click Get Started&quot;]
&gt;
Add another screen? [y/n] &gt;</code></pre>
<p>Repeat until user types <code>n</code>. Minimum 2 screens required for a walkthrough (otherwise recommend <code>showcase-product-demo</code> instead).</p>
<hr>
<h2>Error Handling</h2>
<p>| Error condition | Response | |---|---| | Journey not found in video-profile.yaml | List available journeys, offer to define inline | | Journey has only 1 screen | Warn: &quot;Walkthroughs work best with 2+ screens. Use Product Demo for single-screen videos?&quot; | | Screenshot file missing | Warn with path, use gray placeholder, list all missing paths at end | | No actions defined for a screen | Add a default &quot;scroll to bottom&quot; action for that screen | | Total duration &lt; 25s | Extend tooltip durations, add step-label intro for each screen | | Total duration &gt; 95s | Ask user which screens to cut, or merge actions into fewer steps | | More than 8 screens | Warn &quot;8+ screens may make the video too long&quot;, suggest splitting into 2 videos | | Cursor coordinates out of frame | Clamp to (80–1840, 120–1020) content area bounds | | device not in video-profile.yaml device_frames | Warn, proceed with requested device |</p>
<hr>
<h2>Output</h2>
<p>Return to orchestrator:</p>
<pre><code class="lang-yaml">status: ready
composition_id: AppWalkthrough
storyboard_path: &quot;[OUTPUT_DIR]/storyboard.md&quot;
props: { ...AppWalkthroughProps JSON... }
estimated_duration_s: [N]
screen_count: [N]
step_count: [total actions]
zoom_screen: &quot;[name of zoomed screen]&quot;</code></pre>
<p>The orchestrator handles the render call, thumbnail, captions, and output bundle.</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/showcase-walkthrough.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>