Communitygithub.com

josueh04/product-video-skills

說明當前階段在 Product Video Skills 工作台中的狀態(設定狀態、當前資料夾所屬的產品與影片、每支影片的階段),並顯示下一步應輸入的確切指令。也能根據工作台文件回答「如何...」的提問。

product-video-skills 是什麼?

此技能專門為 Product Video Skills 工作台提供單一畫面的導航與狀態報告。它能讀取工作台檔案系統中的實際狀態,而非依賴對話記憶,以確保資訊準確。支援的平台為 Claude Code 專案,透過執行 `status.py` 腳本讀取 `docs/contracts.md` 定義的檔案結構,推斷每支影片的最新階段(從草稿到已交付)。當使用者詢問當前或指定資料夾的狀態時,該技能會輸出簡潔的狀態摘要,並根據工作台 README、合約文件、其他技能的 SKILL.md 或產品規則來回答「如何做」的問題。它特別強調不應在該技能中開始建置、修復或交付,僅負責報告與引導下一步指令。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/josueh04/product-video-skills/tree/HEAD/skills/video-ask

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

/video-ask

在單一畫面中引導使用者:他們在哪裡、各項目的狀態為何、下一步該輸入什麼。

1. 從檔案讀取狀態,而非從記憶體

PVS_HOME="$(cd "$(cd "${CLAUDE_SKILL_DIR}" && pwd -P)/../.." && pwd)"
"$PVS_HOME/bin/pvs-py" "$PVS_HOME/skills/video-ask/scripts/status.py"

當使用者詢問的資料夾非當前資料夾時,請將該資料夾作為第一個參數傳入。 如果需要欄位(路徑、版本、階段)來回答精確問題,請加上 --json。

該腳本從 docs/contracts.md 定義的檔案中推斷每支影片的階段, 以最新達到的階段為準:簡要未簽署、已簽署、來源已擷取、事實、規格、配音、 建置中、已渲染、QA 失敗、QA 通過、已交付。QA 報告僅在其 sha256 與最新渲染相符時才會計入, 因此重新渲染後的 QA 會顯示為「已渲染」。請相信腳本的結果,而非先前對話回合的說法: 子代理可能已在此期間修改了檔案。

2. 回答

直接顯示腳本的輸出(輸出已經很簡潔),然後在單獨一行顯示下一步指令。 如果使用者提出問題(即引數),請在狀態之後回答,依序使用下列來源,並說明使用了哪個檔案:

  1. $PVS_HOME/README.md(技能說明、安裝方式、產品所需的輸入)
  2. $PVS_HOME/docs/contracts.md(檔案格式、資料夾佈局、命令列)
  3. 問題所涉及技能的 SKILL.md,位於 $PVS_HOME/skills/ 下
  4. 產品的 kit/RULES.md,用於回答「為什麼有這條規則」的問題

如果答案不在這些檔案中,請如實說明,不要猜測。

3. 遇到下列情況時應提示

  • 設定未完成: 下一步指令是 /video-setup。在此之前其他操作都不可靠。
  • 語音金鑰未設定: 使用者應在自己的編輯器中,將金鑰貼到工作台的 .env 檔案中, 切勿在對話中提供。voice.provider: say 在沒有金鑰時仍可運作。 絕對不要讀取 .env 來檢查:腳本已經會報告是否已設定。
  • 位於工作台根目錄且有產品: 每個產品都是獨立的 Claude Code 專案, 擁有自己的技能和鉤子。使用者應執行 cd products/<slug> && claude 來處理該產品。
  • 簡要未簽署: 建置會故意等待審查者的兩個簽名。在這些技能所屬的生產環境中, 26 個版本中有 9 個是因為沒有人同意影片必須解釋哪些功能而發生的。 請勿建議編輯審查者的簽名欄位。
  • QA 失敗: 請指向該影片的 qa/REPORT.md,以查看失敗的檢查項目。

請勿從此處開始建置、修復或交付。此技能僅負責報告;使用者會自行輸入下一步指令。

Individual skills in this repo

This repo contains 14 individual skills — each has its own dedicated page.

josueh04/product-video-skills

Extract, once per product, everything every video of it reuses and write it to kit/ and product.yaml (design tokens, font subsets as woff2, icon subsets as SVG from the product's own icon packages, logos in light, dark and app-tile variants from the repo, a fictional cast proposed once for veto and then frozen, the canonical-names map, pronunciations, banned terms and the read-only tool list). Use it when a product is set up or its kit is missing or incomplete, when a video needs an icon, font or logo that is not in kit/ yet, when someone asks for demo names, fake customers, phone numbers or emails, when a brand word is mispronounced or an old product name shows up, and when checking that demo data is fictional.

josueh04/product-video-skills

Interview the user about a product, then create products/<slug>/ with its own git history, a filled product.yaml and linked skills, fetch its sources and build its kit. Run only when the user types /product-new.

josueh04/product-video-skills

Back every sentence of a video's narration (audio/lines.tsv) and every screen it shows with a citation into the pinned source code (role/path:line@sha) or a docs URL, mark what is visible in the UI versus backend-only, flag restricted or unreleased features, and cut or rewrite anything unbacked; writes the video's TRUTH.md and checks it with truth_check.py. Use it whenever a script or narration is drafted or edited, before voice is generated, before a build, when someone asks "can we say this?", "is this true?", "does the product really do X?", when a reviewer asks for a feature or a claim the product may not support, and when a source document (pitch deck, PRD, marketing page) makes claims the video wants to repeat.

josueh04/product-video-skills

Check a rendered product video before anyone else sees it: worker-pattern flicker, black frames, loudness and true peak, clipping, clicks at clip edges, overlapping narration, speech to text against the script, banned terms and legacy names, camera zoom, contact sheets, frame strips at transitions and parity against the approved version; then write qa/REPORT.json, the only thing deliver.py accepts. Use it after every HyperFrames render, whenever someone asks "is the render clean", "QA this", "check the video", "check the audio", "why does it flicker", "there is a click", "compare v3 with v2", "did the approved part change", or before showing, sending, uploading or delivering any MP4, even when the request does not say QA. Also use it to triage a defect a reviewer reported in a render.

josueh04/product-video-skills

Write a product video's narration and turn it into voice clips with word timings, pronunciation fixes, sound effects and even loudness. The script becomes a table of moments and then audio/lines.tsv (one clip per sentence, with role and speed columns); tts.py voices it with ElevenLabs or the free macOS say voice, maps brand respellings back to the on-screen spelling, normalizes every clip and writes audio/timings.json for the composer; make_sfx.py builds typing tracks from real keystrokes and places recorded click and pop sounds. Use it whenever a video needs a script, narration, voice-over, lines.tsv, timings.json, TTS, a new take, a voice or casting choice, a pronunciation fix ("it says the name wrong"), a changed sentence, a tone note ("too hype", "sounds cut off"), audio levels, a click at the end of a clip, typing or click sounds, or when the build stage asks for the voice. Also use it for silent loops, which still need a moment table and SFX.

josueh04/product-video-skills

The animation rules that keep HyperFrames' parallel render workers from dropping, flashing or flickering elements, plus a static lint (lint_motion.py) that finds the violations in a video's template before it costs a render. Use it whenever you write or edit GSAP tweens, timelines, cursors, camera moves, typing, scrolls or pop-ups in a HyperFrames composition or a video's src/template.tpl, whenever a render shows flicker, stutter, an element that vanishes on some frames, a title that flashes, or a "WORKER PATTERN" line from scan_render.py or qa.py, and whenever the preview looks right but the MP4 does not. Also use it to review someone else's timeline code before rendering.

josueh04/product-video-skills

Pin a product's source code (read-only exports in sources/ plus sources.lock), confirm that the pinned commit is what runs in production, and map every screen of a video brief to its route, components, i18n strings and state, written to the video's SOURCES.md. Use it whenever a video needs to know where a screen lives in the code, when sources/ is missing or stale, before ui-spec-from-code or product-truth start on a video, after the product's frontend changed ("what changed", "which videos are affected", "refresh the sources", "is this checkout current", "which commit is in prod"), and when there is no code and you need an inventory of the no-code references (recordings, recovered captures, docs) a screen can be rebuilt from.

josueh04/product-video-skills

Compose a narrated product demo in HyperFrames: the stage (the product UI rebuilt at its real viewport and scaled to 1080p, camera, rack focus with veil, chapter titles, cursor and clicks, typing, streaming text, pop-ups, toasts, scrolls, end screen and lockup) and the build.py that anchors every beat to a word of the narration. Use it whenever you write or edit a video's video/build.py, src/template.tpl or src/app.css, place a beat on a word, add a chapter, a click, a pop-up or a push-in, frame a screen, build the end screen or lockup, snapshot setup beats, or render a draft or delivery MP4 of a product video in this workbench. Also use it when someone says "the cursor is off", "too zoomed in", "too fast", "it feels chaotic", "the title flashes", "sync the UI to the voice", or asks for a walkthrough, demo or pitch video of a UI.

josueh04/product-video-skills

Gather pixel references for UI that the code cannot show, or to check a rebuild against the real thing, using frames and timed OCR text from screen recordings, captures recovered from past Claude Code session transcripts, a local instance of the app built like production, and web research for third-party apps, plus side-by-side parity images and contact sheets. Use it whenever someone hands over a screen recording (.mov or .mp4) of the product, when a screen has no usable source code (a stale checkout, another company's UI such as a sign-in page, calendar or CRM, runtime output from a backend not in the repos), when asked "what does it really look like", "match the recording", "how long does that animation take in the app", "compare our render to the real app", or when screenshots from an earlier session might already exist. Never uses the reviewer's personal browser.

josueh04/product-video-skills

Turn a product's real frontend code into 1:1 rebuild specs for a video, one read-only subagent per screen, each returning static HTML, CSS with every variable resolved to its literal value and cited (role/path:line@sha), every state, transitions with exact durations and easings, icons from the code's own icon sets, and the exact i18n strings; plus resolve_tokens.py to write the product's design tokens to kit/tokens.css. Use it whenever a screen of the product has to appear in a video, when writing or fixing video/src/app.css or the template markup, when someone asks for exact sizes, colors, fonts, paddings, animations or icons of a screen, when a rebuilt screen "looks off" next to the real app, and when the design tokens or theme of a product need extracting. Framework adapters cover Angular with PrimeNG (proven), React, Vue, Tailwind and plain HTML (unproven).

josueh04/product-video-skills

Coordinate the build of one or more signed videos of the current product with subagents (source recon, product truth, UI specs, voice, one builder per video), re-run QA itself, then deliver. A light coordinator that never builds itself. Run only when the user types /video-build.

josueh04/product-video-skills

Start a new video of the current product - create videos/<video>/, write BRIEF.md, the feature coverage matrix (COVERAGE.md) and the claims sheet (CLAIMS.md), propose chapters, then stop for the reviewer's sign-off. Never builds. Run only when the user types /video-new.

josueh04/product-video-skills

Turn a batch of reviewer feedback on the product's videos into one table per video, fix every video that got notes in parallel (one subagent each) while keeping approved parts, re-run QA and parity, bump versions and deliver. Run only when the user types /video-review.

josueh04/product-video-skills

Check this machine and install the pinned video toolchain of the Product Video Skills workbench (HyperFrames CLI, its rendering Chrome and its agent skills from the same release, the Python environment, the speech model for QA), then run the self-check. Safe to run again. `/video-setup check` only reports.

相關技能