Przejdź do treści
Biblioteka skilli
Marketing i treści · Automatyzacja

directing

/directing

Reżyseruje samouczek w Tutorial Studio: od zatwierdzonej historii do filmu z nagraniem, lektorem i poprawkami kadrów oraz czasu.

Repozytorium
clickcast ↗
Licencja
MIT
Ostatnia zmiana repozytorium
02.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 02.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Reżyseruje samouczek w Tutorial Studio: od zatwierdzonej historii do filmu z nagraniem, lektorem i poprawkami kadrów oraz czasu.

Oryginalny opis (EN)

Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.

Jak działa

  1. 1. Write shotlist.json
  2. 2. Check, voice, film
  3. 3. Draft
  4. 4. Changes after review
  5. 5. Final (only after the Producer confirms the user approved the draft)
  6. Optional: animated cards with HyperFrames
Sekcje z nagłówków SKILL.md, w oryginale · 86 linii, 805 słów
Podgląd SKILL.md
---
name: directing
description: Director skill for Tutorial Studio. Use after the user approves story.md to turn it into shotlist.json and run the crew tools — capture.py --check, voice.py (narration), capture.py (filming the web app as videoshots or screenshots), build.py (draft/final render) — then verify the draft. Also use to fix a failing step, re-film a scene, or change zooms, callouts, timing or cards.
---

# Directing — from approved story to draft video

Input: the **approved** `story.md` (status `APPROVED`; if not, stop and tell the Producer),
`analysis/analysis.md` (+ `pages.json`) for selectors, `notes.md` intake, `style.json`.
Output: `shotlist.json`, then `renders/draft.mp4` + `renders/storyboard.html`.
The full shotlist format is in `reference.md` next to this file — read it before writing one.

## 1. Write shotlist.json

- One scene per story scene, same ids (`s01`…), `chapter` = the story's chapter name,
  `mode` = the story's look. One step per narration line: `say` = the line **word for word**,
  `do` + `target` = the action. Extra silent steps (`wait`, `scroll`) are fine.
- A story row that covers several fields ("Fill in your details.") = the narrated step on the
  first field, then one silent step (no `say`) per remaining field. Don't add narration the story
  doesn't have.
- Selectors from the analysis, most stable first (`[data-testid]`, `#id`, `[name]`,
  `role=…`, `text=…`). Never nth-child chains.
- Sign-in and any preparation the viewer shouldn't watch go in `setup` (not filmed). Credentials
  only as `${DEMO_EMAIL}` / `${DEMO_PASSWORD}` from the project's `.env`; password steps get
  `"secret": true`.
- Emphasis from the story: `zoom`, `callout`, `spotlight`, `focus` (highlight something other than
  what's clicked, e.g. the total after saving). House default is **no zoom** (style.json
  `camera.auto_zoom` = never): the whole page keeps the viewer oriented. Add `zoom` only where the
  story marks it or a control is too small to read — at most once or twice a scene, never on
  consecutive form fields. If a zoomed frame cuts off what the step is about, drop the zoom
  rather than fighting it.
- A click that should land as the line ends ("…then click **Save**.") gets `"act_at": 0.8`.
- `intro.say` / `outro.say` from the title/end card narration; `title`, `subtitle`, `outro.title`,
  `outro.text` from the story.

## 2. Check, voice, film

```
py scripts/capture.py <name> --check     # plays every step fast, no filming: fixes selectors cheaply
py scripts/voice.py <name>               # narration clips (cached; only changed lines are redone)
py scripts/capture.py <name>             # films; each step lasts as long as its line
```
- A failing step prints its key (`s02.3`) and saves `capture/<scene>/error.png`. Look at the
  image, fix the selector or add a `wait`/`setup` step, and `--check` again.
- Make the take repeatable: each run starts in a fresh browser profile (empty cookies and
  storage). If the app keeps data server-side, make sure re-running doesn't fail (e.g. unique
  names), or ask the Producer to have the user reset the demo data.
- `voice.py` engine/voice come from the intake (`shotlist.voice` or `style.json`). `recorded`
  writes `voice/script.md` for the user to record; it exits listing what's missing.

## 3. Draft

`py scripts/build.py <name> --draft` (720p, "DRAFT" badge, ~real time the first time). It renders
in parts — title card, each scene, end card — cached in `renders/.cache/parts/`; later runs redraw
only parts whose content changed (it prints which), so after re-filming one scene the draft takes
seconds, not minutes. It also writes one clip per part in `renders/scenes/` for the storyboard's
per-part review (`--fresh` redraws everything). Then **look at it** — after a re-render, only the
redrawn parts:
extract frames at each zoom, callout, chapter label and card
(`ffmpeg -ss <t> -i renders/draft.mp4 -frames:v 1 -vf scale=960:-1 check.png`; step times are in
`renders/timeline.json`) and check:
- the cursor lands on the right control and the click ripple is on it;
- zoomed views keep the important thing and enough context inside the frame (otherwise remove the
  zoom); callouts don't cover what they label;
- nothing private is on screen (real names, emails, tokens, notifications);
- the narration matches what's on screen at that moment (open storyboard.html to skim);
- `build.py` printed `ok loudness` and no `!!` lines (overlapping narration means a line is
  longer than its step: shorten the line, or add `pause`).
Fix and rebuild before handing back. Report to the Producer in ≤10 lines: draft path, length,
what you checked, any compromise (e.g. "s03 is screenshots because the chart animates slowly").

## 4. Changes after review

Use the "What to re-run" table in `AGENTS.md`. Re-film only affected scenes with
`capture.py --scene <id>` (earlier scenes are replayed unfilmed to reach the right state).
The user's comments: `py scripts/review.py <name> --list`. After the new draft, mark what you fixed
with `--done <key>="short reply"` and report to the Producer which parts were redrawn.

## 5. Final (only after the Producer confirms the user approved the draft)

`py scripts/build.py <name> --final [--music library/music/<file>] [--captions]` → check frames
and loudness again → hand back `renders/final.mp4`.

## Optional: animated cards with HyperFrames

Built-in cards are drawn by `build.py` in the brand colours. For a richer look, make a full-frame
card with the `/hyperframes` skills (if your agent has them; `npx hyperframes` otherwise) at
the video's resolution, render it to `projects/<name>/assets/title.mp4`, and set
`"intro": {"card": "assets/title.mp4", "say": "…"}` (same for `outro`).
Pliki w paczce (2)
  • SKILL.md 6 KB
  • reference.md 7 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · tohawk89/clickcast100MIT
tohawk89/clickcast100MIT

Migawka bazy z 13.11.2026 · wersja paczki 17aca211443e (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90tutorial-pipeline
    Prowadzi produkcję narracyjnego wideo-poradnika aplikacji webowej w Tutorial Studio: przyjęcie, scenariusz, reżyserię i dwie bramki zatwierdzeń.
  • 90tutorial-pipeline
    Prowadzi produkcję narracyjnego wideo-poradnika aplikacji webowej w Tutorial Studio: przyjęcie, scenariusz, reżyserię i dwie bramki zatwierdzeń.
  • 100higgsfield-shotlist-director
    Zamienia brief, scenariusz lub pomysł na jedną spójną listę ujęć dla Seedance 2.0 jako edytowalny artefakt HTML z globalnym prefiksem stylu, słownikiem zasobów i nazwanymi promptami scen.
  • 98resolve-screen-tutorial
    Buduje samouczek programowy w DaVinci Resolve na podstawie zrzutów ekranu: ruchy kamery, kursor, podświetlenia, napisy i karty tytułowe.
  • 95capture-director
    Nagrywa dopracowane klipy demo stron internetowych bez udziału człowieka i składa je z planu ujęć, karty tytułowej i muzyki.
  • 90anime-core-director
    Reżyseruje film animowany: projektuje postacie, niebo i światło oraz sprawdza wyrenderowane arkusze kontrolne.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.