Sma1lboy/rove

HyperFrames Design

Brand, pacing, style, and composition direction. Use after the technical contract from /hyperframes/core is in place.

For motion patterns, scene blueprints, transitions, and CSS marker effects, use hyperframes-motion — this skill is intentionally non-animation.

Read these two FIRST for any non-trivial composition — they override web instincts:

• references/house-style.md — "interpret the prompt, generate real content," the lazy-default list, and the background/foreground layer recipe. This is what turns a literal restyle into a concept.
• references/video-composition.md — video-medium density, scale, foreground metadata (the "produced, not generated" detailing: data bars, registration marks, monospace readouts, 8-10 elements/scene).

Skipping these is the single biggest cause of generic, web-page-looking output. They are not optional rows in the routing table below — for anything beyond a one-line edit, open both before you choose colors or write HTML.

Workflow

1. If a project has a design spec, read it first and treat its frontmatter tokens as brand truth (colors, fonts, spacing, tone, constraints). Which file to read (precedence frame.md → design.md → DESIGN.md) and how to parse it (frontmatter = normative, prose = context) are defined once in references/design-spec.md — resolve and load per that doc.
2. If no design spec exists and the user asks for visual direction, choose a route:
   • Ready-made frame-preset (optional) → frame-presets/ (adopt a FRAME.md as frame.md; see references/design-spec.md)
   • Named style or mood → references/visual-styles.md
   • Fast defaults → references/house-style.md
3. For multi-scene work, plan beats and rhythm before writing HTML → references/beat-direction.md. For scene transitions, jump to hyperframes-motion/transitions/.
4. For motion-heavy work, read references/motion-principles.md (high-level guardrails), then go to hyperframes-motion for atomic rules.

Routing

Topic	Read
Adopt a ready-made frame-preset as frame.md (optional)	frame-presets/ · references/design-spec.md
Default palettes, motion, typography, lazy defaults to question	references/house-style.md
Named style presets, mood-to-style routing	references/visual-styles.md
Palette-specific color tokens	palettes/*.md
Composition patterns — PiP, text-behind-subject, title card, slide show	references/composition-patterns.md
Stats / infographic presentation	references/data-in-motion.md
Structured expansion for open-ended prompts	references/prompt-expansion.md
Video-medium density, scale, color, frame composition	references/video-composition.md
Per-beat direction, rhythm planning, transition timing	references/beat-direction.md
Post-authoring spec verification (colors, type, corners, spacing, depth)	references/design-adherence.md
High-level motion guardrails and GSAP-quality rules	references/motion-principles.md
Font selection, pairings, rendered-video type guardrails	references/typography.md

Scripts

• scripts/contrast-report.mjs — inspect contrast warnings from rendered frames.
• scripts/package-loader.mjs — support script for bundled creative tooling.

Run from the repo root with explicit paths.

Animation analysis (animation-map.mjs) lives in hyperframes-motion/scripts/.

Boundaries

• Do not override /hyperframes/core technical rules.
• Do not require a design system for a minimal technical composition.
• Do not add extra scenes, captions, or transitions unless the request calls for them or you first propose the expansion.
• Keep recipe references task-specific; do not read every reference for simple edits.