nexu-io/open-design / plugins/_official/scenarios/od-next-strategy
od-next-strategy
VerifiedBundled OD Next V2 strategy entrypoint for request-led planning and Build execution.
assets/task-profiles/hyperframes.md
View on GitHub# OD Next HyperFrames Task Profile v3.1.0
> Rollout: active
Task routing, clarification, Build, and the ship-on-write boundary follow the
general orchestration Skill; how HyperFrames is actually invoked is defined
by the engineering implementation. Use the profile fields and delivery requirements as design guidance in the
readable plan; do not serialize them into a machine contract.
## Applicability
Apply this profile only to the parts of the current request that call for this
kind of deliverable. The Core instruction order applies: explicit user scope
and format outrank these defaults. An independent media or document request
does not require this profile's HTML source, page structure, or export workflow.
Keep the normal HTML requirements when building the corresponding prototype,
deck, marketing layout, or HyperFrames composition. Do not add a wrapper merely
because this profile is loaded.
## Profile fields
Resolve platform and purpose, duration, frame shape and rate, script or
storyboard locks, scenes, supplied media, on-screen copy, voice, music,
captions, and required source and rendered outputs. Freeze palette, type,
composition, scene language, motion timing, transitions, safe areas, and
audio rules in the Design Spec.
Never silently omit a missing field: decide per the general orchestration
Skill whether to enter the clarification stage, or convert the gap into an
explicit assumption with its risk disclosed in prose.
Quality focus: narrative and pacing, visual unity, motivated motion, text
readability, asset fidelity, and audio-picture sync.
## Artifact contract
For a HyperFrames composition, the default deliverable is editable HyperFrames source — a timeline-driven
HTML source artifact — with a stable render entry. Final-cut files such as
MP4 are rendered by Open Design's product-side engineering capability after
the source is written and are outside the Agent's responsibility, unless the
task contract explicitly assigns a rendered media file to a Build Package; a
package that owns rendering declares the exact format, duration, frame
dimensions, and frame rate.
Writing the HyperFrames HTML source artifact to disk IS the delivery: no
playback, no frame extraction, no final-cut rendering outside a declared
render-owning package. Never describe a final-cut file as completed before
the declared production route has actually rendered it.
## Build Requirements
Global priority follows the Core System Prompt; this profile establishes no
ordering of its own. Where upstream instructions and contracts are silent,
carry forward brand guidelines, existing videos, and the series' visual
language. User-provided scripts and assets apply only within their specified
scope; this profile's defaults fill in only what has not been specified.
### Build a unified visual world
- Set a clear, consistent visual direction from the subject, audience,
channel, and references.
- Typography, color, composition, assets, camera work, and motion belong to
one visual language; centralize motion, type, color, and scene tokens so
dependent segments use the same system.
- Keep characters, products, environments, light, and brand elements
continuous across scenes unless the story explicitly changes them.
- When modifying an existing video, continue its existing style and pacing
first; never redo unrelated segments.
### Organize information in time
- Turn the script or plan into clear visual segments, each carrying one
distinct narrative job, organized into a readable temporal arc.
- Establish the subject, mood, or a reason to keep watching as early in the
opening as possible.
- Give key copy, subjects, and calls to action enough time on screen to
appear and be read.
- Pace by the weight of the content; never hold the same speed throughout or
sustain high-intensity change end to end.
- Never add, remove, or rewrite shot order, durations, copy, or transitions
the user has locked.
### Give every motion a reason
- Use motion to express entrance, exit, emphasis, transition, causality, or
spatial change.
- Keep motion direction, speed, and camera logic coherent.
- Transitions must connect what comes before and after, never serve as mere
visual stimulation.
- Limit how many elements move at once so the viewer always knows where to
look.
When task configuration provides the following values, execute them and
record them in the Design Spec:
- **Visual style** sets the visual language: motion graphics leads with
typography and graphic movement; live-action look leads with camera
language and depth of field; data visualization leads with evolving charts.
- **Motion intensity** sets shot and transition density: restrained leads
with cuts and fades; standard may use translation, scaling, and graphic
transitions; intense may use continuous camera moves and multi-layer
choreography — but still never unmotivated shake, rotation, or rapid zoom.
### Keep animated text readable
- Limit the amount of text per screen; establish a hierarchy of titles,
body, subtitles, and supporting information.
- Hold text long enough for its reading load and the declared audience:
short titles no less than 1.5 seconds; full-sentence copy estimated at
roughly 1 second per 4 Chinese characters, plus headroom.
- For vertical placements (Douyin, WeChat Channels), keep key text out of the
platform UI zones — roughly the top 15% and bottom 20% of the frame; for
horizontal, keep 5% padding on all four sides.
- Kinetic typography must reinforce meaning; never use sustained shake,
rotation, or rapid zoom that impairs reading.
### Coordinate picture and sound
- When the task includes voiceover, music, or sound effects, keep visual
changes aligned with the sound's rhythm and meaning, and keep voice,
captions, music, sound effects, and visual transitions aligned to the
frozen timing plan.
- Sync subtitles with the voiceover in both content and timing.
- Use sound effects to reinforce actions and transitions, never to mask the
voiceover or key information.
- With the sound off, the picture alone must still carry the main message.
### Avoid runaway motion
- Apply the core anti-cliché defaults strictly: no warm beige / cream color
washes as the default grade, and no floating-particle or glow overlays
used as filler between scenes.
- Avoid purposeless fast cutting, camera shake, continuous zooming, and
random transitions.
- Avoid unexplained jumps in subject, lighting, scale, or style between
scenes.
- Avoid over-enlarging low-resolution assets, and avoid visible distortion of
images, people, or products.
- Never pass off code-driven motion or static slides as the photorealistic
live-action video the user asked for; never substitute a static sequence
for requested motion.
- Never fabricate product capabilities, data, brand endorsements, or campaign
details the user has not provided or confirmed.
### Quality floor
Meet the following in one pass, while writing the source (the timeline and
shot definitions):
- All text sits inside the safe area, unoccluded, with colors chosen for
≥4.5:1 contrast against the background.
- Total timeline duration and aspect ratio match the configuration item by
item; subtitles align with the voiceover sentence by sentence in the
timeline definition.
- Locked scene order, durations, copy, transitions, and supplied media are
preserved item by item — nothing added, removed, or rewritten.
- Adjacent scenes stay continuous in subject, lighting, scale, and style
through asset selection and shot definitions; never use low-resolution
assets that would require excessive enlargement.
- Produce the declared source bundle and any assigned render outputs through
the stated production route; never describe a final-cut file as completed
before that route has actually rendered it.
## Build Packages
Simple mode builds the full timeline in one context. Complex mode may split
complete, independently renderable segments only after the script, timeline,
asset assignments, Design Spec, and integration boundaries are frozen. A
single shot stays within one package — never split a single shot.
Dependencies name shared intros, transitions, audio stems, or preceding
segment outputs explicitly.
## Discovery scope
Apply these requirements only to this output. Reuse the complete same-version Skill already in context; read it when absent. Companion deliverables follow their own Skills. Keep the requested output scope and ordinary prose plan; no machine contract is required.
Create editable timeline HTML with the existing media scaffold command. Read its generated index.html before editing, preserve registration, duration and asset references, and fit the preview viewport without changing composition coordinates. If the user requests an actual MP4 too, read the video Skill and render through the existing media interface; the source alone is not the MP4.
Scaffold stages its editable project under `.hyperframes-cache/<id>/`, which is hidden from the deliverable list. Before completion, publish the finished composition HTML to a user-visible project path such as `animation.html`; keep the timeline registration and resolve/copy its referenced assets so this visible entry works. The hidden working copy alone is not a delivered artifact. Do not copy dependency trees into the project.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |