Skip to content

svenkatreddy/universal-video-skills / skills/cinematic-direction

cinematic-direction

Verified

Direct the look of AI video like a cinematographer: camera language, movement, lighting, color, and style lenses. Use when a prompt needs a real shot in it, not just a subject, or when results look flat and amateur.

FileKindSize
SKILL.mdskill md2.4 KB
references/camera-language.mdmarkdown2.9 KB
references/lighting-and-color.mdmarkdown2.5 KB
references/style-lenses.mdmarkdown2.1 KB

references/camera-language.md

View on GitHub
# Camera Language

Three decisions per shot: how big, from where, and whether it moves. Say all
three.

## Framing (how big)

- **Extreme wide / establishing.** The place first, people small inside it.
  Use to open scenes or show scale.
- **Wide / full.** Head to toe, room to move. Action and choreography live
  here.
- **Medium.** Waist up. The workhorse: dialogue, interaction, readable
  gesture.
- **Medium close-up.** Chest up. Attention narrows to the face without losing
  the body.
- **Close-up.** Face fills frame. Emotion, realization, detail. Spend these.
  A video that's all close-ups has nowhere to go.
- **Extreme close-up.** An eye, a hand, a key turning. Punctuation, not prose.
- **Insert.** The object that matters: the letter, the knife, the ticket.
- **Over-the-shoulder.** Dialogue with geography. We see who they're talking
  to and where everyone stands.

## Angle (from where)

- **Eye level.** Neutral. The default; choose it deliberately, not by default.
- **Low angle.** Power, threat, awe. The subject looms.
- **High angle.** Vulnerability, smallness. The subject shrinks.
- **Bird's eye / top-down.** Pattern, layout, god's-eye detachment.
- **Dutch / canted.** Unease. A little goes a long way; a lot looks like a
  mistake.
- **POV.** We are the character. Powerful for immersion but hard to sustain:
  models drift out of POV fast.

## Movement (the one move)

- **Locked off / static.** The camera doesn't move. Say it explicitly.
  Stillness makes performance and light carry the shot.
- **Push in (dolly in).** Toward the subject. Realization, intimacy, dread.
  Slow.
- **Pull back (dolly out).** Away. Isolation, revelation of context.
- **Track / dolly alongside.** Move with the subject. Pace and pursuit.
- **Pan.** Rotate left/right from a fixed point. Following action or revealing
  space.
- **Tilt.** Rotate up/down. Reveal height, or a face after feet.
- **Crane / jib.** Sweeping vertical move. Openings, endings, grandeur.
- **Orbit.** Circle the subject. Intensity, scrutiny, time freezing.
- **Handheld.** Human shake, documentary urgency. Write "subtle handheld".
  Without that qualifier, models overdo it.
- **Whip pan / crash zoom.** Transitions and punctuation. Use between beats,
  not inside them.

## Lens and depth (the texture of the image)

- **35mm / 50mm / 85mm.** Say a focal length; models key on the numbers.
  Wider = more space and distortion; longer = compression and intimacy.
- **Shallow depth of field / f/1.8.** Subject sharp, world melts. The
  fastest "cinematic" switch there is.
- **Deep focus.** Everything sharp. Tableaus, detail-dense frames.
- **Anamorphic.** Widescreen flares, oval bokeh. Instant cinema grammar.
  Only use it if you mean the whole project to look that way.

## Writing it

`Camera: low-angle medium shot, slow push in, 35mm, shallow depth of field.`
Four tokens, complete shot. If you can't write the camera line this
compactly, you haven't decided the shot yet.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall