Communitygithub.com

josueh04/product-video-skills

현재 세션이 Product Video Skills 작업 공간의 어떤 상태(설정 단계, 현재 폴더가 속한 제품 및 비디오, 각 비디오의 단계)인지와 정확히 입력해야 할 다음 명령어를 알려줍니다. 또한 문서를 바탕으로 작업 공간에 관한 '어떻게 ~하나요?' 질문에 답변합니다.

product-video-skills란 무엇인가요?

이 스킬은 사용자가 Product Video Skills 작업 공간 내에서 현재 위치와 상태를 한눈에 파악할 수 있도록 도와주는 오리엔테이션 도구입니다. `status.py` 스크립트를 실행하여 파일 시스템에서 직접 상태를 읽어오며, 각 비디오가 어떤 단계(예: 브리프 미서명, 소스 가져오기, 렌더링 완료 등)에 있는지, QA 결과가 최신 렌더와 일치하는지 등을 신뢰성 있게 보여줍니다. 사용자가 특정 질문(예: '어떻게 설정하나요?')을 하면 README, contracts.md, 관련 SKILL.md 등 여러 문서를 순차적으로 참조하여 정확한 답변을 제공하고, 답을 찾을 수 없을 때는 추측하지 않고 그 사실을 알립니다. Claude Code 환경에서 Product Video Skills를 사용하는 개발자에게 다음에 실행할 명령어와 작업 공간의 전체 맥락을 제시함으로써 생산성을 높이고 실수를 방지하는 데 초점을 맞추고 있습니다.

지원 대상✓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 unsigned(브리프 미서명), signed(서명됨), sources fetched(소스 가져옴), truth(진실), specs(명세), voice(음성), built(빌드됨), rendered(렌더링됨), QA failed(QA 실패), QA passed(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를 실행하여 작업합니다.
  • 브리프 미서명: 빌드는 리뷰어의 두 서명을 의도적으로 기다립니다. 이 스킬이 비롯된 프로덕션에서는 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.

관련 스킬