BRIEFING INTERACTIVE — SKILL FILE
For Building Recording Visuals for Screen-Recorded Briefings
WHAT THIS SKILL BUILDS
A dark-themed, scrolling HTML page that the practice owner opens in Chrome, screen-records, and narrates over. The recording becomes the briefing video. The page is the visual layer — everything the viewer sees. The voiceover is the audio layer — everything the viewer hears. Together they form a 10–20 minute briefing.
This is NOT:
- A landing page (that's the timer-based briefing wrapper — separate template)
- An interactive thought leadership article (those use light/dark alternation and are read, not recorded)
- A micro-tool (those take user input and produce output)
- A framework explainer (the article already does that)
This IS:
- A behind-the-scenes client walkthrough
- A visual narrative the presenter scrolls and hovers through while talking
- A case study told as a story, with interactive elements that reveal detail on hover
Golden examples:
- The Proof Gap Briefing (
proof-gap-briefing.html) - The Silent List Briefing (
silent-list-briefing-interactive.html)
THE CORE DISTINCTION: BEHIND THE SCENES, NOT FRAMEWORK
The most important thing about this format: the briefing is not the article restated with hover effects.
The article teaches the framework. The briefing shows what happened when the framework was applied to a real client.
| Article | Briefing |
|---|---|
| "There are five wound types" | "Her 8 no-shows were embarrassed. Her 4 quiet proposals had sticker shock." |
| "Matched follow-up outperforms generic" | "Here's what she'd been sending. Here's what we rewrote together." |
| "Recovery rates range from 15–25%" | "19 out of 41 responded. 5 became clients. $62,000." |
| "The system gap has three layers" | "She ran it once. It worked. Then I asked: what happens next quarter?" |
The test: If you removed the article from existence, would the briefing still make sense as a standalone story? It should. If someone watches the briefing first and reads the article second, the article should feel like the methodology behind the story they just watched — not a repeat.
Content that belongs in the briefing:
- Specific client details (practice type, revenue, team size, what they thought the problem was)
- What you actually did together (the discovery process, the aha moments, what surprised them)
- Direct quotes from the client
- Specific numbers from their engagement (not industry averages)
- What you saw that they couldn't see from inside
- Where the work stopped and why
Content that does NOT belong in the briefing:
- Framework definitions (the article covers this)
- Industry statistics or research
- Abstract categorization (wound types as a taxonomy vs. wound types as they appeared in this practice)
- Generic advice or recommendations
- The same comparison tables or visualizations from the article
INTERACTION MODEL
All interactions are hover-driven or scroll-triggered. There are zero buttons, zero toggles, zero "Reveal Next" controls. The presenter controls pacing by scrolling and hovering.
Why No Buttons
This page is a recording visual. The presenter scrolls through it while narrating. Buttons create awkward pauses on video ("now I'm going to click this button..."). Hover effects are invisible to the viewer — they just see content appear as the presenter moves through the page. Scroll reveals create natural pacing as elements cascade in.
Two Interaction Types
1. Scroll Reveal (IntersectionObserver) Elements fade in and slide up when they enter the viewport. Used for all content. Staggered delays on list items create a cascade effect.
// Standard reveal
const observer = new IntersectionObserver((entries) => {
entries.forEach(entry => {
if (entry.isIntersecting) {
entry.target.classList.add('visible');
observer.unobserve(entry.target);
}
});
}, { threshold: 0.15, rootMargin: '0px 0px -40px 0px' });
document.querySelectorAll('.reveal').forEach(el => observer.observe(el));
// Stagger reveal (for list items with data-delay attributes)
const staggerObs = new IntersectionObserver((entries) => {
entries.forEach(entry => {
if (entry.isIntersecting) {
entry.target.querySelectorAll('[data-delay]').forEach(child => {
setTimeout(() => child.classList.add('visible'), parseInt(child.dataset.delay));
});
staggerObs.unobserve(entry.target);
}
});
}, { threshold: 0.2 });
2. Hover Expand (CSS-only) Content is hidden with max-height: 0; opacity: 0; overflow: hidden. On :hover of the parent container, detail panels expand. The presenter hovers over each item while narrating what it means.
.item-detail {
max-height: 0; opacity: 0; overflow: hidden;
transition: max-height 0.4s ease, opacity 0.3s ease;
}
.item:hover .item-detail { max-height: 300px; opacity: 1; }
INTERACTION PATTERN LIBRARY
These are the reusable interactive components. Every briefing uses a subset of these. Match the pattern to what the narrative needs to show.
Pattern 1: Profile Cards
Shows: Who the client is. The practice snapshot. How: Grid of 5 cards (practice type, revenue, team/clients, current approach, the problem). Cards scroll-stagger in with delays. Last card is red (the problem card). Hover dims siblings and highlights the hovered card.
When to use: Always. Every briefing opens with a practice profile. This grounds the story in a real person, not an abstraction.
Pattern 2: Stagger List
Shows: Items that accumulate — categories, questions, discovery items. How: Rows with left gold border, scroll-stagger in at 60% opacity. Hover brings to full opacity with gold border and background tint. Optional: right-aligned numbers.
When to use: When the narrative involves counting, listing, or discovering items one at a time.
Pattern 3: Summary Numbers
Shows: A reveal moment — guess vs. reality, before/after, key metrics. How: Centered text elements with stagger delays. Numbers in Cormorant Garamond. Key number in gold. Coda line in italic stone.
When to use: After a counting sequence or at the end of a results sequence. The "hold for a beat" moment.
Pattern 4: Hover-Expand Items
Shows: Detail behind a summary line — what you found in each category, what the client skipped, what each layer means. How: Bordered rows with title visible. Hover expands hidden detail text below the title. Gold border + background tint on hover.
When to use: When each item in a list has a story behind it that the presenter will narrate while hovering.
Pattern 5: Side-by-Side Zones
Shows: Before/after, surface/real, standard/matched — two versions of the same thing. How: Two-column grid inside a bordered container. Left column (before/surface/standard) is always visible in muted style. Right column (after/real/matched) content is dimmed and offset; hover reveals it with gold tint.
When to use: When showing what the client had vs. what you built together. The contrast IS the value.
Pattern 6: Comparison Block
Shows: Two numbers that tell the whole story. How: Two-column grid with center border. Left number muted, right number gold. Hover highlights each side.
When to use: When two numbers in juxtaposition make the argument (ad spend vs. recovered revenue, time before vs. after).
Pattern 7: Layer Stack
Shows: A framework or progression — what was done, what's still needed, three phases. How: Stacked rows with left tag label and body. Hover expands description. Gold border + background on hover.
When to use: When showing the gap between what the client could do alone and what requires a system.
Pattern 8: Offer Cards
Shows: Two paths forward (tool + diagnostic, or two options). How: Two-column grid. Primary card has gold border and dim background. Hover reveals description text. Hover lifts card.
When to use: Always. Every briefing ends with two starting points.
Pattern 9: Inline Quote
Shows: The client's own words. How: Gold left border, dim gold background, Cormorant Garamond italic.
When to use: Direct client quotes that reveal their mindset — what they believed before the discovery, their reaction to a finding.
Pattern 10: Big Quote
Shows: The briefing's most quotable line. How: Centered, Cormorant Garamond italic, large, with gold for the key word. Bordered top and bottom.
When to use: Between sections as punctuation. 2–3 per briefing maximum.
Pattern 11: Transition Line
Shows: A bridge between sections. How: Centered, Cormorant Garamond italic, medium size, cream-dim with gold .
When to use: When the narrative shifts from one phase to the next and needs a single-line bridge.
NARRATIVE ARC
Every briefing follows this progression. The beats are consistent; the content changes per campaign.
Beat 1: The Practice
Profile cards. Client quote. What they thought the problem was. Set up the story. Viewer thinks: "I know someone like this" (or "that's me").
Beat 2: The Discovery
What you actually did together. The exercise, the count, the audit, the extraction. Stagger lists, hover-expand items. The real numbers emerging. Viewer thinks: "I've never done that."
Beat 3: The Findings
What you found that the client couldn't see. Hover-expand items showing your read vs. their read. Specific details from their practice — not abstract categories. Viewer thinks: "What would mine look like?"
Beat 4: The Rewrite / The Build
What you changed. Before/after side-by-side zones showing the actual work product. Specific to this client's contacts, proposals, services. Viewer thinks: "That's a completely different message."
Beat 5: The Results
What happened. Staggered result lines building to a hero number. Comparison block showing the ratio (spend vs. recovered, before vs. after). Hold the moment. Viewer thinks: "That's real money."
Beat 6: The Gap
What the client could do once vs. what requires a system. Layer stack with "Did / We Did / Still Open" framing. Transition to: the count shows the leak, the diagnostic finds the break. Viewer thinks: "I could count mine. But I can't build the system."
Beat 7: The Decision
Two offer cards. The free tool (start with the count / assessment / calculator). The diagnostic (start with the constraint). CTA. Viewer thinks: "I want to know my number."
DESIGN SPECIFICATIONS
Theme
Dark only. No light sections. This is a recording visual — dark backgrounds look better on video and create visual separation from the article (which uses light/dark alternation).
Typography
- Body:
font-size: 20px(larger than articles for video readability) - Headings: Cormorant Garamond, 400 weight
- Body: Inter, 300 weight
strongis 500 weight (not 600 or 700)- Line height: 1.8 for body text
- Detail text in hover-expand panels: 17px
Colors (CSS custom properties)
:root {
--gold: #b79d64;
--gold-light: #c4aa74;
--gold-dim: rgba(183, 157, 100, 0.08);
--gold-border: rgba(183, 157, 100, 0.25);
--charcoal: #141414;
--charcoal-light: #1e1e1e;
--charcoal-card: #1a1a1a;
--cream: #f5f4f0;
--cream-dim: rgba(245, 244, 240, 0.7);
--cream-muted: rgba(245, 244, 240, 0.55);
--stone: #8a8680;
--red: #c45a4a;
--red-dim: rgba(196, 90, 74, 0.12);
--red-border: rgba(196, 90, 74, 0.3);
}
Note: This format uses var() custom properties (unlike micro-tools which hardcode all hex values). This is acceptable because briefing interactives are single-page files with no JS-generated HTML that would break var() references.
Layout
- Sections:
padding: 140px 48px - Container (prose):
max-width: 860px - Container-wide (grids, zones):
max-width: 1100px - Section padding compresses at 968px and 768px breakpoints
Nav
<nav>
<div class="nav-inner">
<a class="logo" href="https://advisoryos.ai">
<img src="[Advisory OS icon URL]" alt="Advisory OS">
<span class="logo-text">Advisory OS</span>
</a>
<span class="nav-tag">Briefing</span>
</div>
</nav>
- Fixed, blurred background (
backdrop-filter: blur(12px)) - Subtle bottom border (not the heavy 3px gold border from micro-tools)
- "Briefing" tag in gold with border (not a section label)
Hero
- Full viewport height (
min-height: 100vh) - Centered text
- Subtle radial gold glow behind (
::beforepseudo-element) - Label: "An Advisory OS Briefing"
- h1 with gold
on the key word - Subtitle: Cormorant Garamond, stone color, describes the specific client story
Footer
Standard Advisory OS footer. Identical across all pages.
Animations
- Scroll reveal:
opacity 0→1, translateY 24px→0, 0.7s ease - Hover transitions:
0.3s–0.5s ease - Stagger delays: 200–400ms between items
fadeInUpkeyframe not needed — all animations use transition classes
BUILD SEQUENCE
- Write the narrative arc first. Map out all 7 beats with the specific client story. What's the practice profile? What discovery did you do? What did you find? What did you change? What happened? Where did they get stuck? No code yet.
- Map interactions to beats. For each beat, select which interaction pattern serves the narrative. Not every beat needs a fancy pattern — some just need reveal paragraphs and an inline quote.
- Build HTML structure. All sections, all containers, nav, hero, footer. No styling yet.
- Add CSS. Copy the design specifications from this skill. Adjust section-specific styles for whatever interaction patterns you're using.
- Add hover interactions. All CSS-only.
max-height+opacitytransitions.
- Add scroll reveals. IntersectionObserver instances for
.revealelements and stagger containers.
- Test the scroll-through. Open in Chrome, scroll through at narration pace. Does every element appear at the right moment? Do hover details expand smoothly? Is the pacing comfortable for a 10–20 minute walkthrough?
RECORDING WORKFLOW
- Open the HTML in Chrome (full screen, no bookmarks bar)
- Start screen recording + audio
- Scroll and hover through the page while narrating
- Nothing auto-advances — you control all pacing
- Hover over items while explaining what you found
- Pause (stop scrolling) on summary numbers and big quotes
- The recording becomes the briefing video embedded in the timer-based landing page
WHAT THIS SKILL DOES NOT COVER
- The landing page: The timer-based wrapper where the recorded video lives. That's a separate template (see
timer-based-briefing-golden-example.html). - The briefing script: The voiceover narrative with scroll/hover cues. That's written as part of the campaign distribution assets.
- The article: The thought leadership framework piece. Different format, different skill (
interactive-narrative-SKILL.md). - Micro-tools: Calculators, diagnostics, revelation tools. Different purpose, different skill files.
Skill file extracted from: The Proof Gap Briefing + The Silent List Briefing Created: February 20, 2026