Communitygithub.com

josueh04/product-video-skills

現在のセッションがProduct Video Skillsワークベンチのどの状態にあるかを示し(セットアップ状態、現在のフォルダが属する製品と動画、各動画のステージ)、次に入力すべき正確なコマンドを表示します。また、ワークベンチに関する「どうやって...」という質問にもドキュメントから回答します。

product-video-skills とは?

このスキルは、Product Video Skills(PVS)ワークベンチ内でのユーザーの現在位置を明確にし、次のアクションを正確に指示するための案内役です。スクリプト`status.py`を実行して、ファイルシステム上の実際の状態(署名済みかどうか、ソース取得済みか、レンダリング完了かなど)を読み取り、それを基に各動画の進行ステージを表示します。このスキルは記憶に頼らず、常に最新のファイル状態をチェックするため、サブエージェントによる変更も反映されます。また、ユーザーが「どうやって...」と質問した場合、`README.md`、`docs/contracts.md`、各スキルの`SKILL.md`、製品の`kit/RULES.md`から順に回答を探し、見つからなければ推測せずに「見つかりません」と伝えます。セットアップ未完了やボイスキー未設定、署名待ち、QA失敗などの重要な状態を自動的に指摘しますが、このスキル自体は構築や修正を行わず、あくまで情報提供と次のコマンド指示に徹します。主にClaude Code環境で使用され、各製品が独立したプロジェクトとして動作する前提で設計されています。

対応✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/josueh04/product-video-skills/tree/HEAD/skills/video-ask

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

/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 で定義されているファイルから各動画のステージを推測します。到達した最新のステージは次の通りです: brief(概要)未署名、署名済み、ソース取得済み、truth(真実)、specs(仕様)、voice(音声)、built(ビルド済み)、rendered(レンダリング済み)、QA失敗、QA成功、delivered(納品済み)。 QAレポートは、その sha256 が最新のレンダリングと一致する場合にのみカウントされます。そのため、QA後に再レンダリングすると、再び rendered と表示されます。会話の前のターンで言われたことよりも、スクリプトの出力を信頼してください。サブエージェントがその間にファイルを変更している可能性があります。

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 を実行して作業します。
  • 概要未署名: ビルドはレビューアによる2つの署名を意図的に待ちます。これらのスキルの元となった本番環境では、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.

関連スキル