agentleFS
alisadiq-aialisadiq-ai/favstash-ai-video-editing-skills/skills/3-styles-on-camera/paper-grid/SKILL.md

paper-grid

Skill75 starsChanged 40 days agoApache-2.0View on GitHub

Style for edit-video: a white paper pane with a quiet grid above the speaker and one clean animated UI artifact per spoken line (cards that type, counters, lists that expand, approvals that click). Use for tool, repo, skill or feature explainers where each sentence names something that can be drawn as UI.

  • Installs packages

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every spoken item gets its own small, living artifact: a card types, a counter climbs, a row lights up, a cursor clicks.

    line 10
  2. Distinctive:

    Keep the identity: white paper, the quiet grid, white cards with one rim, one navy accent, Helvetica Neue, one clear idea per beat, real …

    line 15
  3. Distinctive:

    The library is a vocabulary, not a template: Use a component when it is the best picture of the line, and invent a new artifact when it …

    line 19
  4. Distinctive:

    Keep it alive with typing, counters, a highlight sweep, a live dot.

    line 58
  5. Distinctive:

    Don't reuse a reference creator's graphics or identity.

    line 68
  6. Very specific:

    Write the run's build script: one with reel.scene(...) per beat (example_build.py shows the mechanics, not a storyboard):

    line 78
  7. Very specific:

    Look before rendering: python3 scripts/snap.py <comp> <out> 0,40,120 for stills.

    line 86
  8. Very specific:

    Put initial state in gsap.set.

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Paper grid

A style on top of edit-video, which owns the cut, captions, sound and review. The top half is white paper with a quiet grid; the speaker stays in the bottom half. Every spoken item gets its own small, living artifact: a card types, a counter climbs, a row lights up, a cursor clicks.

Fixed identity, open imagination

Keep the identity: white paper, the quiet grid, white cards with one rim, one navy accent, Helvetica Neue, one clear idea per beat, real proof for facts. Everything else is designed for the story in front of you.

  • The library is a vocabulary, not a template. Use a component when it is the best picture of the line, and invent a new artifact when it isn't: a terminal that types, a diff that turns green, a flowchart that wires itself.
  • Each reel should feel designed for its topic. Change which artifacts appear, how they connect, the rhythm and the one or two moments that surprise.
  • Aim for one screenshot-worthy idea per reel: an object that transforms into the next beat, a satisfying click, a counter that lands on the spoken word.

Fits a talking head about a tool, repo, workflow or feature. Dark or saturated room footage benefits most: the white pane gives contrast and a clean seam. Not for personal reflections, jokes over footage or long screen demos that need the whole frame.

The look (starting defaults)

ElementSetting
Paper#fbfbfd pane at y 0–960. Grid 45px minor / 180px major lines at 5.5% / 10% ink, radial fade at the edges, drifting one cell over the reel
SeamHard split at y=960 with a 1px light line and a soft shadow into the camera
CardsWhite, 30px radius, one 1px rim, soft drop shadow, about 740–820 wide, centered on x=540
Chips64px white capsules with a 42px icon tile, 28px bold
Ink#0f172a text, #64748b muted, navy accent #1e40af / #5b9eff. Red, amber and green only where they mean something
TypeHelvetica Neue. Card text 30–36px, labels 21–28px, hero figures 200–270px
SkeletonsGrey bars and gradient avatars stand in for people and body text; only the words that carry the point are real

Tokens live in scripts/paper_grid.py (TOKENS), component CSS in assets/paper-grid.css. Override per reel with Reel(tokens=...).

Layout and motion

  • Split for almost everything. Artifacts sit at y 270–940; captions go on the speaker's headroom (about y=.55). Set split_video_top from the actual take so the head starts below the caption band.
  • Full camera only for re-hooks ("but the best part is…"): push in over the line, then return to the split on the reveal word.
  • Frame 1 shows the product moving: open on the split with the first artifact already on screen and settling.
  • One artifact per spoken item, on its word. It enters on the noun and acts on the verb. Entrances .35–.45s (cards rise 50px, chips pop), exits .2s, 6 frames before the next item. Carry one object through related beats.
  • Keep it alive with typing, counters, a highlight sweep, a live dot; no perpetual shimmer, spin or bounce. Start from the motion library.

Truth rules

  • Real proof for facts: the actual repo page, list or product screen (scripts/capture_page.py), checked against the source that day. Crop to the content that reads at phone size and push into the words that carry the beat.
  • Mockups stay generic: skeleton posts and counters carry no real names or results; unmeasured meters carry an ILLUSTRATIVE label and no numbers.
  • Don't reuse a reference creator's graphics or identity. Borrow the mechanism only.

Build

Needs Python 3.10+ and the workspace runtime from edit-video's init-workspace.mjs --install (HyperFrames and GSAP). Snapshots and page captures also need pip install playwright and Google Chrome.

  1. Cut the dialogue with edit-video and keep a word timeline; beat frames come from it.
  2. Capture proof into the run's assets/, cropped to the fact that matters.
  3. Write the run's build script: one with reel.scene(...) per beat (example_build.py shows the mechanics, not a storyboard):
    sys.path.insert(0, '<this skill>/scripts')
    from paper_grid import Reel
    reel = Reel('<run>/work/grid-v01', camera='<run>/assets/camera.mp4', total=1314)
    compile() writes the HyperFrames folder and checks the timeline script.
  4. Look before rendering: python3 scripts/snap.py <comp> <out> 0,40,120 for stills.
  5. Render with .favstash-studio/runtime/node_modules/.bin/hyperframes render <comp> --fps 30 --quality high --output <raw>.mp4, then scripts/fix-frame0.sh <raw> <visual>.mp4 if frame 0 came out black.
  6. Assemble dialogue, captions and sound in your editor or with FFmpeg, and review with edit-video.

Sound map (edit-video's SFX pack)

Visible eventCue
Frame 1hook-impact
Split ↔ full cameracamera-shutter; the light shutter for a smaller change
Re-hook buildmetallic-riser, resolving on the reveal
Card, chip or pill arrivalui-pop (merge arrivals under ~6 frames apart)
Toggle, highlight, button pressui-click
Expand, shrink, fly-awayzoom-swish
Typed texttyping-tick.wav, one cue per ~0.9s of typing
Earned approvalclean-ding.wav, once

Pitfalls already paid for

  • Anything that enters later must start hidden (opacity:0), or it shows before its cue.
  • Put initial state in gsap.set; a tl.set at 0 alone can revert on seek.
  • A <video> given only a width renders at the file's pixel height and letterboxes. Set an explicit height with object-fit:cover.
  • Give every component a distinct id; the library's own layers use root, top, grid, seam, camFull, camSplit and their V videos.
  • Snapshots can race on seek. Trust the encoded render when they disagree.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.