mcpField
H
hyperframes-creative

hyperframes-creative

github.com/ryu1845Creative & media016 installsUpdated 1w ago
Repository

About hyperframes-creative

hyperframes-creative is a guidance skill for shaping brand, pacing, narration, and composition in HyperFrames projects. It serves creators who need visual and story direction, while leaving animation mechanics to a separate skill.

Key features

  1. 01Design-spec and style routing
  2. 02Composition and video-density guidance
  3. 03Beat and rhythm planning
  4. 04Narration and typography guidance
  5. 05Design-adherence checks
  6. 06Audio-reactive composition support

Use cases

  1. 01Developing a visual direction from a brief
  2. 02Planning rhythm across multiple scenes
  3. 03Checking design choices after authoring

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ryu1845/hyperframes --skill hyperframes-creative

After installing, type/hyperframes-creativein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

frame-presets/biennale-yellow/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/blockframe/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/blue-professional/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/bold-poster/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/broadside/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/capsule/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/cartesian/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/cobalt-grid/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/code-editorial/
caption-skin.html
frame-showcase.html
FRAME.md
frame-presets/code-editorial/fonts/
OFL-eb-garamond.txt
OFL-inter.txt
OFL-jetbrains-mono.txt

Details

From the project README

Plugin installs: Before setup or freshness commands, follow plugin execution rules when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.

HyperFrames Creative

Brand, pacing, style, narration, 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-animation — 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 scale, depth, and foreground detail. It explains how to avoid empty web-page layouts without imposing a universal element count.

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
    • Interactive selection → references/design-picker.md
  3. For multi-scene work, plan beats and rhythm before writing HTML → references/beat-direction.md. For scene transitions, jump to hyperframes-animation/transitions/.
  4. For motion-heavy work, read references/motion-principles.md (high-level guardrails), then go to hyperframes-animation for atomic rules.

Routing

TopicRead
Adopt a ready-made frame-preset as frame.md (optional)frame-presets/ · references/design-spec.md
Default palettes, motion, typography, lazy defaults to questionreferences/house-style.md
Named style presets, mood-to-style routingreferences/visual-styles.md
Palette-specific color tokenspalettes/*.md
Composition patterns — PiP, text-behind-subject, title card, slide showreferences/composition-patterns.md
Stats / infographic presentationreferences/data-in-motion.md
Structured expansion for open-ended promptsreferences/prompt-expansion.md
Video-medium density, scale, color, frame compositionreferences/video-composition.md
Per-beat direction, rhythm planning, transition timingreferences/beat-direction.md
Post-authoring spec verification (colors, type, corners, spacing, depth)references/design-adherence.md
High-level motion guardrails and GSAP-quality rulesreferences/motion-principles.md
Font selection, pairings, rendered-video type guardrailsreferences/typography.md
Story doctrine — hook language, value-before-evidence, storyboard-as-proposal, source-traceable visualsreferences/story-spine.md
Script pacing, tone, openings, number pronunciationreferences/narration.md
Precomputed audio bands mapped to motionreferences/audio-reactive.md

Scripts

  • scripts/contrast-report.mjs — inspect contrast warnings from rendered frames.
  • scripts/extract-audio-data.py — pre-extract audio bands for audio-reactive compositions.
  • scripts/package-loader.mjs — support script for bundled creative tooling.

contrast-report.mjs resolves helper packages from the current project first, then can bootstrap the bundled HyperFrames package version. Set HYPERFRAMES_SKILL_PKG_VERSION=<version> only when running the skill outside the bundled CLI/skill install and you need to pin that bootstrap version explicitly.

Run with explicit paths, for example:

python <SKILL_DIR>/scripts/extract-audio-data.py <audio-file>

Animation analysis (animation-map.mjs) lives in hyperframes-animation/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, narration, music, 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.

Comments

Markdown supported