Demo authoring skillpack

Author a guided, narrated, recorded demo tour for an Adom bridge or dock bar dashboard (KiCad, Fusion, the next ones): real content fetched live, ab's demo panel remote honoured instantly, captions and TTS narration, windows brought forward once and sized into slots, every beat verified before motion, motion that stays on the content, first-run box hardening, and a whole- desktop recording with audio that reaches the user. START HERE for any demo, tour or walkthrough a bridge runs on a user's desktop; routes to ten demo-* sub-skills. Trigger words: build a demo, make a demo tour, guided tour for my bridge, dashboard demo, play the demo, demo authoring, record the demo, demo remote, demo captions, demo narration, demo motion, verify the demo, demo on another machine, port the kicad tour, fusion demo tour, demo skillpack.

Captions and narration for a bridge demo: ab caption sizes and positions that do not collide with the panel, a reason on every caption, narration lines generated once with adom-tts and played by the bridge, the mute law, sync with the beat, and the system-mute pitfall that produces a silent recording. Read before adding a caption or an audio line to a tour. Trigger words: demo captions, caption size, medium caption, small caption, caption position, caption overlaps the panel, narration audio, adom-tts narration, demo mp3, mute unmute audio, audio sync, audio starts with the window, silent recording, system muted.

Pick and prepare what a bridge demo shows: a real, recognisable design fetched from the wiki at tour time, beats that build from one part to the whole assembly, and captions that state facts pulled from the design. Read before choosing what a demo opens. Trigger words: what should the demo show, demo content, sample board for the demo, lame board, sexy board, tour beats, beat order, demo captions text, fetch the design at tour time, real design in the demo, demo sample project.

What breaks on a first-run or colleague's box that never breaks on yours: a cold app with no plugin armed, a brand-new library item the app cannot see until it restarts, an opener that misreads plugin-not-running as a stale cache and restarts the app mid-beat, hidden UI panes, user-owned app instances, minimized remote-desktop windows. Read before running a demo on a box that is not your test box. Trigger words: first run demo, cold start, fresh machine, colleague's box, plugin not running, plugin arming, cache predated, kicad_restarted_retry, restart kicad mid tour, hidden pane, user-owned kicad, demo fails on another machine.

Map the KiCad tour's pattern onto the Fusion 360 bridge (and onto any dashboard demo): the beat equivalents, what the Fusion API does better (camera, named views), what stays identical (remote, captions, verification, recording), and the prompt to hand a bridge's build thread. Read when building a demo for a bridge other than KiCad. Trigger words: fusion demo tour, fusion equivalent of the kicad tour, port the demo to fusion, demo for another dashboard, demo for my bridge, beats for fusion, sketch body assembly drawing render.

Motion in every demo window so the recording looks alive without content leaving the screen: zoom extents first, bounded wheel zooms and pans, isometric then orbit in 3D, menu or API driven camera moves instead of guessed drags, and a canvas check after each gesture that recenters when the view empties. Read before adding zoom, pan or rotate to a tour. Trigger words: demo motion, zoom pan rotate, looks alive, zoom extents, zoom to fit, isometric, orbit the board, content off screen, dumb zooming, over-rotated, camera moves, 3d viewer rotate, canvas blank after pan, recenter.

Turn a demo recording into the videos people watch: mix narration at true offsets, cut a full version and a part B version, and avoid the six ffmpeg traps that each cost a round on the KiCad demo (a pup WebM declaring 1000 fps, no duration header, apad plus shortest running forever, splicing audio from an already mixed cut, dead air before the first line, a cut that starts before the click). Ships a reference postprod.py. Read before touching ffmpeg on a demo recording. Trigger words: post production, mix the narration, cut the video, part b video, tour only cut, ffmpeg webm, 1000 fps, runaway encode, dead air, double audio, overlapping audio, concat segments, adelay amix, video version query.

Record a bridge demo as a whole-desktop video with system audio and get it to the user: ab's native recorder (2.1.35+: desktop_record_start records one monitor plus the system audio mix to MP4, no browser), the pup screen-share recorder as fallback, the routing pitfall while ab still forwards desktop_record_* to pup, a 20 second survival test, the system-mute check, watching the recorder during the tour, pulling the clip, ffmpeg trimming and sizing, the 30 MB chat limit, and attaching the full file to a wiki issue for a tappable link. Read before recording a tour. Trigger words: record the demo, record a video of the demo, desktop recording with audio, desktop_record_start, native recorder, pup_screen_record_start, recording died, pull the recording, transcode, ffmpeg, video too big to send, 30 MB limit, attach video to wiki, record_window_start.

Wire ab's demo panel (play, pause, next, back, mute, X) so every press is instant, acknowledged, honoured in order and mirrored by the dashboard: loopback callbacks, ack captions, a FIFO control queue, cutting the beat in flight, exit teardown, and how to ralph-test the wiring with synthetic presses. Read before touching a tour's transport. Trigger words: demo panel, demo remote, prev next play pause mute, eventCallbackUrl, press callback, ack caption, instant press, cut the beat, demo control queue, X close the tour, stop event, press injection, synthetic press, dashboard play button, dashboard control verb.

The look-before-you-send review for a demo video or a demo screenshot: tile frames at every segment boundary and actually read them for the things a viewer notices at once (a stray cursor over the app, black letterbox areas, a zoom that shows a label instead of the part, missing 3D bodies, doubled or missing audio, dead air). Written after four such defects reached John on one day. Read before sending any video, frame or hero image. Trigger words: review the video, check the frames, stray cursor in the video, black area, contact sheet, look at the screenshot, did you look at it, before you send, video quality check, hero showcase check.

Run and test a bridge demo exactly the way a user starts it, from the Hydrogen dock bar to the dashboard's Play the demo button, driven by screenshots and clicks through ab, with the dashboard and the bridge kept in sync (pill, mute, toasts, closing). Read before demonstrating or recording a tour, or when a dashboard-started tour behaves differently from a CLI-started one. Trigger words: true demo the user runs, start from the dock bar, click the kicad card, play the demo button, dashboard started tour, dashboard pill, demo toast, closing the demo tour, caller identity from the dashboard, drive hydrogen by screenshot.

Measure every demo beat before showing motion and never assume: front, title, painted, stable, placed, gestures, and how to record them on the job so a dashboard and a human can read them; plus the ralph-test method for tours (screenshot, analyse, fix, re-run) and what 'verified' has to mean before you claim success. Read before calling a beat done. Trigger words: verify the beat, is the right window showing, done loading, canvas painted, stable capture, verified front title painted, tour record, per beat record, progress projection, ralph test the demo, are you analyzing these screens, claim success, evidence frame.

Window choreography for a bridge demo: bring each new window forward exactly once then yield, measure 'in front' correctly (skip minimized windows, shell popups and your own overlays), size editor windows to 80 percent of the work area in offset slots, save and restore bounds (also before closing a window, to protect the app's sticky geometry), and leave the app's main window alone. Read before moving or raising any window in a tour. Trigger words: foreground the window, bring to front once, yield to the user, window in front measurement, z-order, 80 percent window, window slots, top-left top-right, save restore window bounds, sticky geometry, do not maximize, main window size, hidden pane, library tree pane.