Communitygithub.com

Tech7516/Inventaire_PCP16

Read when creating a complete edited video — promo, product/demo, explainer, topic, social/Reels/TikTok, 探店/local business, e-commerce/packshot/360, DTC/before-after ad, or any 20s+ multi-shot/storyboarded piece — for the current project or a user-supplied subject. Also use whenever the video pairs with narration/voiceover or a separate audio track, or must be timed to a measured audio length (even one image-to-video clip plus one voiceover line), since only the Remotion timeline keeps the audio from being cut off.

Inventaire_PCP16 是什么?

Inventaire_PCP16 is a Claude Code agent skill that read when creating a complete edited video — promo, product/demo, explainer, topic, social/Reels/TikTok, 探店/local business, e-commerce/packshot/360, DTC/before-after ad, or any 20s+ multi-shot/storyboarded piece — for the current project or a user-supplied subject. Also use whenever the video pairs with narration/voiceover or a separate audio track, or must be timed to a measured audio length (even one image-to-video clip plus one voiceover line), since only the Remotion timeline keeps the audio from being cut off.

兼容平台✓Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/Tech7516/Inventaire_PCP16/tree/HEAD/.atoms/skills/promo-video-production

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

When to use

Use this skill when the user asks for a promotional video, product video, demo video, marketing video, launch video, explainer video, brand video, designed video, multi-shot video, storyboarded video, social/Reels/TikTok discovery video, local business video, restaurant/food vlog style video, product ad, e-commerce / Amazon-style product video, packshot or 360 product-spin video, storefront / local discovery video, DTC / direct-response / before-after conversion ad, 20s+ edited video, or any complete video that introduces a subject visually.

Prefer this Remotion workflow whenever the request describes a complete edited video with timeline, shots, captions, audio, camera language, visual style, consistency requirements, CTA/end card, or multiple scenes — even if the user never says "promo" or "promotional". Use direct AI video generation only for a single short source clip or background loop, not as the final delivery path for a complete multi-shot video.

The video subject can be either:

  1. Project promo — a project, app, or feature that the agent itself is building or that already exists in the workspace, or another existing app already identified in the user request or prior confirmed context. First resolve the source app being promoted. app/promo is the output video project, not automatically the source app.
  2. Topic promo — a user-supplied topic, concept, brand, or external subject that does not require a workspace project. Examples: "the Solar System", "Song dynasty history", "what is a vector database".

Both paths share the same Remotion template, the same composition presets, and the same render commands. Only the storyboard authoring differs.

Command

Use RemotionPromoRenderer.render for final promo export after validation. This command is documented by this skill and may be called even if it is not listed in <Available Commands>.

width/height/source_orientation MUST come from the storyboard's Export Spec, not from this example. The example below shows landscape values as placeholders; if the storyboard is portrait, pass width=1080 height=1920 source_orientation=portrait (and square → 1080/1080/square). The output filename is promo-<width>x<height>.mp4, so a portrait render that wrongly used 1920x1080 is a sign you copied the example instead of reading the storyboard.

<RemotionPromoRenderer.render>
<promo_dir>/absolute/path/to/app/promo</promo_dir>
<width>WIDTH_FROM_STORYBOARD</width>
<height>HEIGHT_FROM_STORYBOARD</height>
<source_orientation>ORIENTATION_FROM_STORYBOARD</source_orientation>
</RemotionPromoRenderer.render>

Subject classification

Before doing anything else, classify the subject from the original user request. Do not ask the user to clarify if the request already names a topic or project.

  • If the user message names a clear external topic / concept (e.g. "create a promotional video about the solar system") and the workspace has no app/frontend or no application code to promote → topic promo.
  • If the user message references an existing app/frontend build, an in-progress app the agent has been generating, or an upcoming feature → project promo.
  • If the subject is a physical product, a retail/local business or place, or a direct-response offer with no rebuildable app UI as its primary subject (e.g. a car-diffuser ad, a jewelry 360 spin, a ramen-shop local discovery, a pet-hair-remover DTC ad) → commerce promo.
  • If both apply (e.g. "make a promo for our solar-system explainer app") → treat the app as primary and use the topic as supporting subject; this is a project promo.

Use these tie-breakers when more than one could fit: a rebuildable software UI is the subject → project promo; a physical product / physical place / offer with no rebuildable UI → commerce promo; an external concept or knowledge with no product → topic promo. A mixed case (e.g. a DTC software product whose ad also shows a real checkout screen) is classified by what the hero shots sell, and may borrow the other class's rules per-shot (e.g. one ui-demo checkout beat inside a commerce promo).

Topic promos and commerce promos are first-class. Do not reject or stall on a topic promo just because there is no app/frontend in the workspace, and do not downgrade a commerce promo to a topic promo just because the product has no app/frontend to rebuild.

Compliance baseline

Promo videos must default to conservative ad-safety rules. Use only claims, offers, prices, discounts, gifts, brand names, CTAs, certifications, sales numbers, effects, and services that are present in the user's request, project, ad copy, or landing page. Do not imply official partnerships, platform recommendations, brand endorsements, or certifications unless the source material explicitly provides them.

Do not use misleading or unverifiable claims such as guaranteed results, absolute rankings, risk-free promises, fake scarcity, fake countdowns, fake notifications, fake buttons, fake system UI, fake testimonials, fake reviews, fake news, or exaggerated result screenshots. Do not directly target sensitive personal attributes such as health, finances, age, race, religion, sexuality, disability, marital status, body shape, or appearance; use neutral audience wording instead.

Do not include unlicensed brand marks, recognizable people, copyrighted characters, third-party product UI, media, fonts, watermarks, adult content, gore, shock, hate, harassment, humiliating content, weapons, drugs, gambling, tobacco, or political-sensitive material. For high-risk categories such as medical, supplements, weight loss, cosmetic procedures, finance, loans, crypto, gambling, alcohol, dating, children, legal, recruiting, real estate, politics, religion, or social issues, keep the video informational and avoid strong promises, dramatic before/after visuals, or aggressive conversion pressure.

Keep footage clear, stable, and high quality: no flicker, severe compression, stretching, watermark, black bars caused by bad asset sizing, or edge-cropped subtitles/logos/CTAs. If compliance is uncertain, choose the safer, more neutral, information-first expression. This baseline reduces risk but is not a platform approval guarantee.

Final conversion CTAs are static video content, not interactive web UI. Do not render the closing CTA as a clickable-looking website button, fake click target, arrow button, fake input, fake popup, fake system UI, cursor target, hover/pressed state, or any control that implies the viewer can click to navigate. Use an end-card line, brand tagline, account handle, URL, QR placeholder, or plain "visit / scan / follow" text instead. Product demos and page walkthroughs may show real or simulated UI buttons, forms, and navigation when they demonstrate the product flow, but they must not become the final conversion CTA.

Any visible URL, account handle, QR target, browser address-bar text, or brand endpoint must come from the user's request, confirmed project source, landing page, or another verified asset. If the project only exposes a placeholder domain or no confirmed public address, omit the URL and end with brand copy instead; for a browser-window treatment, use a non-URL page label or leave the address bar blank. Do not infer a domain, handle, or destination from the app name, repo name, download filename, template placeholder, env var token, or similar hints.

Core workflow

  1. Initialize the Remotion project with FrontendEngineer.use_template("remotion") if app/promo is not already ready. The tool itself rejects a non-Remotion source before copying, so you do not need a separate verify step.
  2. Pick the target orientation up front from the user request and storyboard plan: landscape (16:9), portrait (9:16), or square (1:1). All later validation, smoke, and full-render commands must use the matching variant.
  3. Classify the subject (project promo vs. topic promo) using Subject classification above. Do not stop to ask "what should this be about?" if the original request already names a topic or project.
  4. Ground the subject:
    • Project promo: first resolve the source app being promoted, then read that app's app/frontend source, manifests, and prior validation feedback. If the current workspace mainly contains the promo output, do not treat app/promo itself as the source app. Once you identify the source app, lock that source project root / frontend path in promo_storyboard.md or working notes and keep reusing the same path after switching into app/promo; do not downgrade to topic promo just because the promo workspace itself has no app/frontend. Before writing Remotion code, record the key source frontend file paths you will rely on in promo_storyboard.md (pages/routes/components for the demo beats). Later, when implementing src/, reopen those source files and copy/recreate from the code instead of relying on a long prose summary.
    • Topic promo: extract the subject from the user message and prior conversation; pull additional facts from your own knowledge or external tools (image / video / audio generation, search if available). Do not require a workspace project to exist.
    • If the user provided reference images but the current request only exposes file paths instead of attached image content, read image-understanding and call ImageAnalyzer.analyze_images before storyboarding so the visual plan is grounded in the actual image content rather than filenames.
    • If the user provided a website URL as the promo subject, use Browser.goto to visit the page, then Browser.take_screenshot to capture the visual, then call ImageAnalyzer.analyze_images on the screenshot before storyboarding so the visual plan is grounded in the actual page content rather than the URL alone.
  5. Apply the Compliance baseline: confirm which facts, claims, offers, and assets are actually supported by the request, product, ad copy, or landing page. Do not invent unsupported offers, certifications, sales numbers, effects, official partnerships, platform endorsements, or brand backing; when uncertain, choose conservative information-first wording and visuals.
  6. Determine the default language for newly generated promo content before writing promo_storyboard.md. If the user explicitly specifies an output language, use that language. Otherwise, default to English. A user message written in Chinese/Japanese/etc., the surrounding chat language, or the system prompt language is not an explicit language request. Record the decision directly in the storyboard as Language: English (default) or Language: Chinese (user specified) before drafting shots, copy, narration, or generation prompts.
  7. Create promo_storyboard.md before writing video code or generating assets. Use the field set that matches the subject type (see Storyboard requirements). For promo/remotion runs, promo_storyboard.md is the only planning artifact; do not create or maintain a separate todo.md.
  8. If the user requests narration, voice-over, spoken walkthrough, or the storyboard clearly needs a narrator, include a short-segment narration plan in the storyboard, check each segment's script length against its target shot seconds, then read audio-generation and call AudioCreator.generate_audios with one request per shot/beat.
  9. After TTS generation, prefer each audio segment's returned duration. If duration is missing or null, measure the real duration from the returned URL (for example with ffprobe), then decide the final per-shot timing from those measured durations. This calculation is not enough if it only appears in thought or terminal output.
  10. Immediately update promo_storyboard.md with each narration URL, measured audio seconds, final shot start/end/duration, total duration, and any script/timing changes. This is a hard checkpoint: do not call MusicCreator.generate_music, VideoCreator.generate_videos, generate more visual assets, or write src/timeline.ts until the updated timing is persisted in promo_storyboard.md. After this lock, promo_storyboard.md must no longer keep placeholder TBD timing rows or an outdated total duration.
  11. By default, promo videos should also include one global background-music plan unless the user explicitly says no music or the piece is clearly better without music. Read music-generation and call MusicCreator.generate_music with exactly one instrumental / no-vocals request after the final shot timing is locked. The prompt must include the target total seconds, mood, pacing, instrumentation, and whether the track should leave room for narration.
  12. After music generation, use the returned URL directly and prefer the returned duration, just like narration. If duration is missing or null, measure the real BGM duration with ffprobe. Immediately update promo_storyboard.md with the BGM URL, measured seconds, target total duration, fit strategy, and planned mix values before writing src/timeline.ts or src/PromoVideo.tsx. The locked storyboard/timeline duration is the source of truth. Never shorten the video just to match a short BGM; trim, minimally loop, or regenerate the music instead unless the user explicitly asked for a shorter cut.
  13. Generate any other needed AI image/video/audio assets after the storyboard is written and the narration + BGM timing is settled in promo_storyboard.md.
  14. Read remotion-best-practices and focus on the sections relevant to the storyboard.
  15. Edit the Remotion implementation in place under app/promo — keep the template's flat src/ layout (src/Root.tsx, src/PromoVideo.tsx, src/timeline.ts, src/components/, src/scenes/, src/app-demo/). Do not move sources into a subdirectory like src/remotion/. Before validation, do one quick self-check: remove unused imports/vars, omit redundant Sequence from={0}, keep motion purely frame-driven (no CSS animation / transition, tim

相关技能