Cinematic Shot Grid
Una pagina per scena: ogni inquadratura, movimento di camera e segnale di cui la troupe ha bisogno.
Trasforma uno script in una griglia visiva delle inquadrature — una cella per inquadratura con schizzo del fotogramma, dimensione del piano, angolazione della camera, movimento, segnale audio e durata — così il ritmo di una scena è visibile in un colpo d'occhio e la giornata di riprese scorre su un'unica pagina.

Installala in 3 passaggi
Nessuna registrazione. Nessuno strumento da riga di comando. Scegli la tua AI, copia una riga e incollala.
Preferisci fare da te? Acquista la skill ($4.99), scarica lo ZIP dalla conferma d'acquisto, decomprimilo nella cartella mostrata sopra e riavvia la sessione della tua AI — stesso risultato. L'hai già acquistata? Il tuo assistente AI può scaricarla per te.
Cosa contiene
Un file SKILL.md (la guida operativa) + un modello di partenza. Un'anteprima:
Cinematic Shot Grid
When to use
- You have a finished script but no plan for how it actually gets shot, angle by angle
- Your shoot day keeps stalling because nobody agreed on coverage before the camera rolled
- You are directing a short film, music video, or ad and need the crew to see the whole scene at a glance
- You keep overshooting — hours of footage for a two-minute scene — because shots were never locked in advance
- You need to hand a director, DP, or client one page that shows the scene's visual rhythm before anyone picks up a camera
Workflow
- Break the script into beats (input: script pages → output: beat list)
Read the scene and split it into beats: each beat is one change in what the audience should feel or learn. A two-page scene usually yields 4–8 beats. Write each beat as one line — what happens, and what the audience should take from it. If a beat can't be stated in one line, it is two beats. - Assign one shot per beat — then add the coverage (input: beat list → output: shot list)
Give each beat its primary shot: the angle that carries the beat's meaning. Then add only the coverage the edit actually needs — an establishing shot to open the scene, cutaways for reactions or details, and a closer or wider shot where the emotion turns. Every shot must justify itself against its beat; a shot with no beat is a shot you will cut. - Lay out the grid (input: shot list → output: shot grid)
Draw the grid: one cell per shot, in story order, left to right, top to bottom. Each cell holds a rough frame sketch (stick figures are fine — composition and eyeline matter, draftsmanship doesn't), the shot size (wide / medium / close-up), the camera angle, and the beat number it serves. The grid is the scene's map: anyone should be able to read the scene's rhythm by scanning it. - Add the camera and sound pass (input: shot grid → output: annotated grid)
For each cell, add three lines: camera (static / pan / dolly / handheld — and where it starts and ends), sound (dialogue line, sound effect, or music cue), and duration (estimated seconds). Keep movements simple and motivated: the camera moves because the story moves, not because the rig is available. Check that consecutive shots cut together — eyelines match, screen direction stays consistent, and no two adjacent shots are the same size from the same angle. - Lock the shoot plan (input: annotated grid → output: shoot-ready grid)
Read the grid as a shoot day: group shots by setup (same camera position, same lighting) to minimize company moves, and mark the order you will actually shoot them in. Flag any shot that needs special gear, a location change, or a prop. Print or export one page per scene. On set, the grid is the plan — if a shot gets dropped, cross it out on the grid so the editor knows it was a decision, not an oversight.
Anteprima del modello
Cinematic Shot Grid — Scene Template
One scene = one grid. Break the script into beats before assigning a single shot.
Scene: {scene title / number}
Script pages: {pages} | Target runtime: {seconds} | Location: {location} | Characters: {names}
Beat list (one line each — what happens + what the audience should take from it)
Shot grid (story order, left to right, top to bottom)
Total estimated runtime: {sum} seconds vs. target {target} seconds
Continuity check
[ ] Eyelines match between consecutive shots [ ] Screen direction consistent (180-degree rule held, or deliberate break marked)
Il pacchetto della skill (SKILL.md + modello) è scritto in inglese.


