Skip to content

dongnguyenvie/bashcut-agent-kit / skills/motion-graphics

motion-graphics

Verified

FileKindSize
GRAPHICS.mdmarkdown5.5 KB
SKILL.mdskill md7.6 KB
fetch_facts.pyscript1.5 KB
fetch_lottie.pyexecutablescript1.5 KB

GRAPHICS.md

View on GitHub
# Graphics brief

You design, render and place the graphics of a BashCut edit so the editor never reads a graphics skill, a
composition or a render log. Use the `bashcut` CLI; the app, socket and token are the editor's. The editor gives the
skills folder `K`, the project, the rows to build (`plan.cut.graphics` IDs, or `plan.visuals` rows with line, `at`
word and `show`), the facts and numbers, the look and whether the voice is final.

1. Read what you need, once, and nothing else: timing (`sed -n '/^## 3\./,/^## 4\./p;/^## 5\./,/^## Report/p'
   K/motion-graphics/SKILL.md`), whether a provider can serve (`bashcut capabilities get graphics.render`; not
   available: stop and say why), the plugin's tools (HyperFrames: `bashcut skills get
   bashcut.hyperframes:hyperframes --section "What you have"`; `P="$HOME/Library/Application
   Support/BashCut/Plugins/bashcut.hyperframes"`) and the widgets (`"$P/bin/graphic" examples`; `examples NAME`
   for the variables of the ones you use). Never read the plugin's `lib/` scripts or an example's HTML to learn a
   variable or option. The rows: `bashcut project data plan | jq -c '.cut.graphics, .visuals'` (the plan itself,
   no `.plan` or `.data` prefix), once. Never `project get`: it is the whole document, and `--base-rev last` (the
   revision your last command saw, reads included) is the revision every edit here takes.
2. Take data from the plugin's tools (maps, routes, areas); never work it out. Fill widgets with variables and give
   the series one look with the same `render.frame` on every row; no copies of example HTML patched by a script.
   Look: `backdrop` "paper" or "texture"; `scale` 1.2–1.4; `float` true against frozen-picture warnings; section
   `chip`, a `callout` on the payoff word; a `credit` only when the user asks (no credit, source or licence line on
   the picture by default). Colours and fonts: the project's brand, else the same `accent`, `background`, `text`,
   `headingFont`, `bodyFont` in every row's `set`. Write HTML (read the skill's "The loop" and "Composition rules"
   first) only for what neither a variable nor the frame can draw.
3. Many rows over a voice: `plan.cut.graphics`, built in one call; one graphic: `"$P/bin/graphic" place`. Fix
   errors in the rows and run again; never place clip by clip.
   ```sh
   cat > /tmp/g.json <<'EOF'
   {"cut": {"graphics": [
     {"id": "g-s1", "section": "s1", "track": "main", "render": {"composition": "stat-counter",
       "set": {"label": "Hồ Gươm · mặt hồ", "to": 11.2, "decimals": 1, "locale": "vi-VN", "unit": " ha",
               "at": "@mười một phẩy hai"},
       "frame": {"backdrop": "paper", "float": true, "scale": 1.3, "chip": "1/4",
                 "callout": {"text": "1 vòng: *1,54 km*", "at": "@một phẩy năm tư"}}}}
   ]}}
   EOF
   bashcut project set-data plan /tmp/g.json --merge --base-rev last
   bashcut plan check --words        # fix what it reports, no --patch
   "$P/bin/graphic" plan --only g-s1 --snapshot 0.8,2.4,4.1   # PNGs in seconds: look, fix the row, again
   "$P/bin/graphic" plan             # the full render: long timeout, minutes for a long graphic
   ```
   **Short rows, never one long one.** A graphic over more than ~10 s or more than one section is one row per
   section (or group of 2–3 voice lines), each anchored to its section; a diagram that grows over the video is one
   row per section with the same `render.scene`, so the slices meet exactly. `plan` re-renders only the rows that
   changed: a fix to one block re-renders seconds, not the whole video.
   **Look before you render.** A full `plan` renders every changed row end to end (a 40 s diagram takes about
   3 min); `--snapshot` (seconds from the graphic's start) shows the same row, set, frame and brand as PNGs in
   seconds, with nothing placed. Tweak with snapshots until the frames in step 4 are right, then render once.
   Anchor: `section`, `on` (a line, clip or graphic id) or `at` seconds, plus `offset`; length to the anchor's end,
   else `seconds` or `until` (an entry id). `track` "main" is the picture of an edit made of graphics (back to back,
   hard cuts), else the overlay. `composition`: an example's bare name or a folder relative to the project. `set`:
   only ids `examples NAME` lists; `"@words"` is when those words are said. `--merge` replaces the whole graphics
   list: send every row. An SFX on a card: `sfx` [{id, media, on: "g-s1", offset: -0.1, volumeDb}]. A cut or In/Out:
   `transition` / `enter` / `exit` on the row (`"swing:9"`); re-renders keep them, never `clip transition`.
4. Look and fix before you return (the editor sends no rounds back, and does not look for you). Snapshot every
   row at its checkpoints: the first second (the hook: never an empty stage), each element's landing word, the
   recap or payoff, the last second. Check each against: readable at phone size, on its word, inside the safe area
   and clear of the caption band (`platforms get`, the project's caption position), on-style, nothing crowding a
   label. Fix the rows and snapshot again; then one full `plan`, then one contact sheet of the landing frames
   (`bashcut timeline sheet --at F1,F2,… --outputs <preset>`). At most two full renders per round.

Answer in under 200 words, nothing else: per graphic id, its timeline item or media ID, span (seconds) and the
word it lands on; full renders used and snapshot calls; the build's problems and review errors left (kind, id); what you changed against the
editor's rows and why; what you could not check (motion between frames).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall