mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-17 23:47:33 +00:00
Make the example library load-bearing in 4 places: 1. SKILL.md — new 'Step -1: Study the Example Library' BEFORE Step 0. Mandatory: read examples/README.md + at least 3 scene HTMLs before planning. Names which scenes are 'the bars' (04-composed-ui scene 01 kanban + scene 02 chat). Non-negotiable rule: if you'd reach for a product screenshot of an interface as a primary visual, STOP and build that UI from divs using the matching example scene. 2. step-3-storyboard.md — Technique-pick checklist after the pacing table. Every beat must name 2-4 techniques AND cite the matching example scene path. Beats with <2 cited techniques must be redesigned. Forbidden: 'show the kanban' as a beat with no scene citation. 3. step-5-build.md — Copy-closest mandate added to the build section. Concrete map from beat type to example scene path. Do not write any beat from scratch; there is always a closer example. 4. beat-builder-guide.md — Example scene moved to the #1 mandatory read for every beat. Sub-agents copy the cited scene's index.html to compositions/beat-N-name.html and mutate, not write from scratch. Specific call-out: if the beat has narration, also study examples/04-composed-ui/scene-02-chat-with-typing — the canonical narration-sync pattern (every meaningful phrase = one visual event). This is the lever HANDOFF Recommendation 2 named: agents pattern-match to what they study, not to skill prose. With 18 production-grade scenes in the library and the workflow now requiring agents to copy them as starting points, the screenshot+Ken-Burns default has somewhere better to go.