본문으로 건너뛰기
cccskills
무료GitHub에 공개

motion-styles

Opt-in library of established visual styles for code-drawn Helios videos: style cards (colour rules, type, motion grammar, a checkable signature list, the core rendering trick) with tested renderAt(t) demo pages, plus finishing passes and time tricks. Load it only when the user names a specific established style or medium they want reproduced (a print process, a retro screen look, a design movement), or asks to see Helios's style options. Do not load it to choose a look for a video request that names no style: design an original look instead, and at most offer this library.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios스타 123(GitHub 123 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(52)

  • SKILL.md8.7 KB
  • references/catalog.md4.2 KB
  • references/finishing.md25.5 KB
  • references/styles/art-deco.html13.2 KB
  • references/styles/art-deco.md8.3 KB
  • references/styles/ascii-crt.html14.2 KB
  • references/styles/ascii-crt.md7.9 KB
  • references/styles/aurora-glass.html9.1 KB
  • references/styles/aurora-glass.md7.5 KB
  • references/styles/bauhaus-poster.html10.8 KB
  • references/styles/bauhaus-poster.md8.1 KB
  • references/styles/blueprint.html16.4 KB
  • references/styles/blueprint.md8.9 KB
  • references/styles/cel-boil.html14.5 KB
  • references/styles/cel-boil.md7.7 KB
  • references/styles/dark-keynote.html12.4 KB
  • references/styles/dark-keynote.md8.4 KB
  • references/styles/flat-vector.html13.0 KB
  • references/styles/flat-vector.md7.9 KB
  • references/styles/halftone-dossier.html15.6 KB
  • references/styles/halftone-dossier.md7.6 KB
  • references/styles/hud-fui.html14.5 KB
  • references/styles/hud-fui.md7.7 KB
  • references/styles/isometric.html13.8 KB
  • references/styles/isometric.md9.7 KB
  • references/styles/one-line.html11.0 KB
  • references/styles/one-line.md7.4 KB
  • references/styles/pixel-art.html13.4 KB
  • references/styles/pixel-art.md8.4 KB
  • references/styles/risograph.html12.4 KB
  • references/styles/risograph.md8.0 KB
  • references/styles/shape-morph.html12.3 KB
  • references/styles/shape-morph.md7.1 KB
  • references/styles/silkscreen.html13.6 KB
  • references/styles/silkscreen.md7.2 KB
  • references/styles/spy-titles.html16.8 KB
  • references/styles/spy-titles.md8.3 KB
  • references/styles/sticker-explainer.html14.7 KB
  • references/styles/sticker-explainer.md9.6 KB
  • references/styles/swiss-grid.html9.8 KB
  • references/styles/swiss-grid.md9.2 KB
  • references/styles/synthwave-vhs.html17.7 KB
  • references/styles/synthwave-vhs.md10.7 KB
  • references/styles/ukiyo-e.html18.9 KB
  • references/styles/ukiyo-e.md7.5 KB
  • references/styles/variety-captions.html13.3 KB
  • references/styles/variety-captions.md9.7 KB
  • references/styles/watercolor-ink.html20.0 KB
  • references/styles/watercolor-ink.md10.2 KB
  • references/styles/woodcut.html14.9 KB
  • references/styles/woodcut.md7.2 KB
  • references/time-tricks.md17.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Motion styles

A style is a set of invariants: what the image is made of, which colours are allowed and what they mean, how things move, how the camera behaves, and what never happens. Get those right and the video reads as that medium; get them wrong and it reads as "flat vector with a noise overlay".

Each style is a card (references/styles/<slug>.md) and a demo (references/styles/<slug>.html), a complete page under the make-video contract that passes helios verify.

When to use this library

This library is a set of known answers, and known answers pull everything toward themselves. An agent that reads a menu of 24 looks before every video makes those 24 looks forever. So the library is opt-in:

The requestWhat to do
Names a style or medium ("make it risograph", "like an old blueprint", "Swiss style")Open that one card: references/styles/<slug>.md. If you're unsure of the slug, list references/styles/. Don't read the catalog.
Asks for style options, or says "surprise me with a known look"Read references/catalog.md and offer at most three styles chosen with a seed, plus one original direction. Build only what they pick.
Names no styleDon't use this library. Design an original look from the brief and a random seed (the make-video skill describes how). You may offer once, in one line, that a known style from this library is available. Load it only if they say yes.
Gives a brand or design systemFollow the brand. A card can lend a technique (a halftone, a grain, a draw-on) only if the user asks for that treatment.

Never copy a demo's composition. Demos show how a technique is built; the video should come from the user's subject.

Vary within the style

Two risograph videos should not be the same video in different words. Before the treatment, draw a random seed and let it make the choices the card leaves open.

If an apply-randomness skill is available, use it for this step. Otherwise:

LC_ALL=C tr -dc 'A-Za-z0-9' < /dev/urandom | head -c 256; echo

Look for a few verifiable patterns in the string (a digit run, a repeated fragment, a cluster of capitals, an odd/even split) and turn each into a concrete choice inside the card's "safe to change" axes: the subject's framing, the palette variant within the colour rules, the structure, which native move goes at the peak, the opening and the ending. Keep the seed and a one-line pattern → choice map in your notes. The card's invariants never change; the seed only moves what the card leaves free.

What a card holds

SectionWhat it fixes
Essence and NotThe medium in one line, and the cheap version to avoid
LookPalette rules (how many hues, what the one accent is reserved for, what is never coloured), type, materials
MotionEasing, timing, stepping, allowed and banned transitions, camera grammar
Signature checklist5–7 features with numbers, checkable on stills ("overshoot 1.15 → 1.0 within 8 frames", not "bouncy")
Native movesMoments only this medium can do. Put one at the emotional peak.
Core techniqueThe rendering trick that makes it look right
PitfallsWhat goes wrong, including encode and determinism problems
Check on stillsWhat to look for in still, sheet --strip and sheet --crop

Workflow

  1. Read the card the user asked for, start to finish.
  2. Seed and mini-treatment. Draw the seed (above). Sketch three possible structures from it and pick one. Place one native move at the peak. Write down what you'll learn from the demo and what you won't take from it.
  3. Style frames before motion. Build two or three key frames with the real drawing code and render them with helios still. Check them against the signature checklist. Fix the look before animating anything.
  4. Build with the demo's technique, not its composition: your subject, your structure, a palette chosen within the card's rules.
  5. Review. Stills at 6–10 key times, a sheet every 0.5 s, a strip over the fastest move, crops of fine texture and text, then verify and check. Tick the signature checklist.
  6. Not the demo again. Compare your video with the card's demo on six things: structure, opening, signature shot, camera path, rhythm, ending. At least four must differ.

Rules for every style

  • The card's invariants override generic motion rules. Swiss bans bounce and fades; silkscreen and ukiyo-e ban dissolves; Bauhaus and pixel art want empty space, not four layers of depth; collage-like and cel styles cut hard by design. Where a card conflicts with motion-design-rules or other generic advice, the card wins.
  • One accent, one job. Almost every style reserves one colour for one element or one moment. Don't spend it everywhere.
  • Stepped things on twos, camera on ones. Characters and hand-made elements step at 12 fps (Math.floor(t * 12 + 1e-4) / 12); the camera moves smoothly, because a stepped camera judders. Render stepped styles at --fps 24 so each drawing holds exactly two frames.
  • Texture is seeded, and mostly fixed per shot. Registration offsets and paper come from hash(shotIndex); boil and grain step at 12 fps from Math.floor(t * 12); accents get analytic "kicks". Nothing comes from Math.random().
  • Texture must survive encoding. Halftone dots at a period of at least 7 px, hairlines at least 1.5 px, grain subtle. Check with sheet --crop and render the final with --preset medium.
  • Pass the flash check. helios check (WCAG 2.3.1) counts luminance flips per block of pixels. A zoom or pull-out across dense high-contrast texture (a wall of tiles, sand, magnified halftone) fails however slowly it moves, and so does a big shape that slides out and back on every beat. Fixes are in finishing.md.
  • One world-to-screen function. Anything that tracks a subject (labels, effects, reticles) goes through the same camera function as the subject, or it drifts after the first camera move.
  • Subject big at key moments: at least a third of the frame height.
  • Text in the style's world. Captions are a cartouche, a stamped band, a NOTE box, a LOG strip or a toast, not a default subtitle bar. Hold each for at least max(1.8 s, letters / 15 + 1.5 s).
  • Original content only. Describe a medium's grammar; never imitate a specific artist, studio, film, brand or event identity.

Shared references

  • references/finishing.md: grain, dither, vignette, glow, paper, ink plates and a WebGL press shader, halftone, CRT/VHS, film damage, die-cut outlines, chrome text.
  • references/time-tricks.md: exposure sheets, stepped and remapped time (sceneTime), springs and impulses, keyframe tracks, log and smooth zooms, precomputed integrals, curvature-weighted pen timing, and in-page motion blur that keeps text and counters sharp.

Make your own style

To adapt a card into the user's own style, sort its sections into three groups:

  • Safe to change: the palette (within the card's colour rules), type, tempo, sound, which native moves you use.
  • Changes its character: materials and rendering, the colour logic itself, camera grammar. Change these knowingly.
  • Can't change: the essence and the core technique. Change those and it's a different style.

Write a new card in the same format next to the original, list what changed and why, render a style frame beside the original's, and make a 15–30 s test that shows every change.

Credits

Styles are adapted from two MIT-licensed libraries: lemo-opuscar by LemoLab (the style-card format and most print, graphic and retro styles) and mg-styles-15 by Vincentwei1021 (motion-graphics styles, sub-frame-safe timing and the signature-checklist prompt structure). Cards and demos are written in our own words and code, and no assets are copied. Each card names its source. See THIRD_PARTY.md.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Story-first motion design philosophy for animated video: motion must earn its place; arc (establish, complicate, resolve); show vs tell; shots as units of thought; quiet vs loud motion; Disney principles with restraint; timing heuristics; composition; grammar by medium (product demos, logos, data viz, explainers); technical commitments (deterministic time, scrubbability, refs); cutting discipline; explicit anti-patterns. Use when planning, storyboarding, critiquing, or implementing programmatic or motion-driven video (Helios, Remotion, explainers, loops, UI capture, logo reveals), or when the user asks for motion direction, pacing, or visual-story structure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

Find, preview, cut and credit archival B-roll from the Internet Archive (archive.org) for a Helios video — public-domain, CC BY and CC BY-SA film plus Prelinger Archives. Use when a Helios composition needs real footage as a plate, cutaway, masked fill or texture. Not for generating footage or editing the user's own camera video.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

End-to-end production plan template for feeling-first cinematic product promos: brief interrogation, 45s beat structure (cold open through brand), hero-element metaphor, storyboard fidelity ladder, visual system (palette, type, camera, texture), motion mix and easing vocabulary, audio and captions, tooling (animatic through HTML or AE), deliverables matrix, accessibility, review milestones, and compromises to accept or refuse. Use when planning, pitching, storyboarding, or producing polished brand films for any SaaS or consumer product—not category-specific; pair with skills/design/animated-video-philosophy for broader motion principles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

Workflow for creating a new Helios composition. Use when building a new animation project or converting an existing animation to run in Helios.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

Patterns for using Helios with Vanilla Canvas API. Use when building high-performance 2D/3D animations without frameworks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

Chart.js integration patterns for Helios. Use when creating animated data visualizations with Chart.js.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

BintzGavin/helios1232026년 10월 26일 업데이트

BintzGavin의 스킬 모두 보기

이 스킬의 문제 신고