LogoAhaPrompt
  • 提示詞
  • 精選
  • 模型
  • AI 反推
  • 定價
  • 投稿
  • 部落格
AhaPrompt

圖片、影片、音訊 AI 提示詞庫

探索

  • 全部提示詞
  • 精選提示詞
  • 圖片提示詞
  • 影片提示詞
  • 音訊提示詞
  • AI 模型

工具

  • AI 反推工作臺
  • 圖片反推提示詞
  • 影片反推提示詞

資源

  • 定價方案
  • 投稿提示詞
  • 部落格

版權所有 © 2026 AhaPrompt 保留所有權利。

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞扁平矢量解说视频代码流水线

扁平矢量解说视频代码流水线

AClaude Opus 5.5Anthropicvideo

问我我的主题和我的脚本。如果我没有脚本,就根据我的主题写一个。 问我有哪个图像模型:GPT Image 2,或者任何接受2K-4K参考图的模型,每张图大约$0.03-0.05。 问我有哪个语音:ElevenLabs,或者免费的Kokoro。 在生成所有内容之前,给我看一个外观测试:一个场景板、一个剪下来并绑定好的角色表,以及一个10秒的镜头,包含打字、一个标签和一个会说话并指点的角色。等我的确认。 一个1920x1080的动画解说视频,风格类似大型扁平矢量信息图频道。 - 每一句旁白都由卡通人物在一个完整的插画场景中演绎出来。 - 所有运动都是代码实现的。没有AI视频生成,只有少量静态图像,由代码切割、绑定和动画化。 美术: - 扁平色块,无描边,最多用一个稍深的扁平色来表现形体,简单的几何形状和清晰的边缘。 - 柔和的色调:灰蓝色、石板青、暖米色、藏青色、柔紫色。鲑鱼粉肤色,大圆头,点状眼睛,小身体。 - 氛围来自场景自身的光线:日光、冷蓝色夜晚、温暖的室内灯光。 代码颜色: - 墨色 #2b2d42,红色 #d62828,橙色 #f4a261,金色 #f6b93b,绿色 #2fb37a,藏青 #1f2a48 - 标题番茄色 #e2552f 和紫色 #5b3fa6 - 灰色标签 #8a8c9c,白色卡片 #ffffff - 字体:Montserrat 800-900(Google Fonts),卡片和标牌上全部大写。 节奏: - 每3-4秒一个新场景,每分钟约10个场景。 - 每2秒有新元素出现:一个标签、一个印章、一个人走进来、一个数字。 - 任何静止画面不超过1秒。任何角色都不能不动。 禁止: - 描边、漂浮在画面上的光泽UI面板、emoji、烧录字幕 - 任何频道的标志或名称、真人照片 - 当场景本身可以承载信息时,把事实写在纯色卡片上 总共约60张图像($2-3)。 每个提示词都以这段风格核心逐字开头: “扁平矢量插画,与参考图完全相同的艺术风格:任何地方都没有描边或线条艺术,每个形状都是扁平纯色填充,最多用一个稍深的扁平色来表现形体,简单的几何形状,清晰干净的边缘,无渐变,无纹理,无绘画式光照。柔和的现代色调:灰蓝色、石板青、暖米色、藏青色、柔紫色、鲑鱼粉肤色。无文字,无字母,无数字,无标志。” 然后添加一行锁定场景的文字(“场景是[时间、地点]:[材质、光源],除非特别要求,否则不出现其他时代的元素”)。输入3-5帧参考频道的画面作为风格参考,裁掉它们的标志。 1. 主场景板,约24张,每张一个完整的16:9图像,用于你放大进入或反复回到的场景。 - 空场景:“无人物,无角色,无动物”。 - 正面视角,中间留有开阔地面供角色站立。 - 空白标牌、板子、屏幕和页面,供代码后续写入。 2. 四宫格场景板,约19张,提供76个额外场景。将4个场景打包进一张图像: “图像是一个2x2网格,包含四个完全独立的场景,每个恰好占据图像的四分之一(每个四分之一本身是一个16:9画面),由完全笔直的细纯白色间隔线分隔,一条垂直线沿正中央,一条水平线横跨正中央。” - 然后描述左上、右上、左下和右下场景。 - 沿中心附近最亮的白色行和列分割每个四宫格,当线条白色占比超过60%时继续外扩,再额外裁切6像素。 - 将每个图块裁剪为1920x1080的16:9。 - 物体特写非常适合做图块:一张桌子、一个屏幕、一份文件、一盘食物、一个金库。 3. 主要角色,2-3个。为每个角色写一段固定描述(年龄、发型、面部、每件衣物的颜色),并逐字粘贴到每张表中。 - 基础表:6个视角。(1) 正面,中性表情,绘制时不含手臂,只有圆滑的肩窝在手臂连接处;(2) 同样的无臂正面,第二种情绪;(3) 向右行走的侧视图;(4) 背面视图;(5) 和 (6) 脚本需要的两个姿势。 - 表情表:6个无臂正面(充满希望、厌恶、恐惧、疲惫、生病、震惊,或脚本需要的任何表情),以基础表为参考。 - 姿势表:6个完整姿势及其道具(坐在桌前打字、睡觉、吃饭、奔跑、签名、摔倒),以基础表为参考。 4. 其他所有人:4-6人的角色表,每个人以镜头所需的确切姿势绘制;8-10个小人物的群像表;道具表。 - 每张表:“在纯扁平色度绿背景(#00B140)上,人物之间有大量空白绿色空间;互不接触,任何角色或物体上都没有绿色,全身,不被边缘裁切”。 5. 缩略图美术:同样的角色,搭配更丰富饱和的卡通光照和极端情绪,顶部四分之一留空,无文字,以基础表为参考。 抠图: - 背景是每个与边界相连的像素,满足 G - max(R,B) 大于40且在中位绿色值110以内。只从边界抠取,否则深色衣物会泄漏。 - 添加2像素软Alpha带,并在其中将G钳制为max(R,B) + 6,消除绿色边缘。 - 按人物分组碎片并去除杂点。为每个精灵命名,并给我看一张带名称的接触表。 无臂正面人物变成木偶: - 在颈部拆分头部:头部下方最窄的Alpha行。 - 找到两个肩窝和眼睛框。 - 用身体自身的颜色修复头部下方的空洞,这样点头时不会露出缝隙。 - 将所有内容写入rig.js:尺寸、颈部、肩窝、眼睛框、皮肤RGB、袖子RGB。 - 手臂:上臂L1约为人物高度的0.13,下臂L2约为0.12,粗细约为0.04。使用袖子颜色到

詳細資訊
类型
AI 影片提示詞
畫面比例
16:9
Duration
9:03
更新於
2026年11月9日
分類
AnimationCartoonMotion Graphics
Source

如何使用這條提示詞

  1. 1點選上方複製按鈕,複製完整提示詞。
  2. 2開啟 Anthropic 的 Claude Opus 5.5,或你常用的 AI 影片生成工具。
  3. 3貼上提示詞,保留鏡頭與運動描述詞——它們決定了畫面的運鏡效果。
  4. 4按示例參數(16:9 · 9:03 · Animation · Cartoon · Motion Graphics)生成,再小步迭代——措辭的細微變化會顯著影響結果。

常見問題

這段影片是用哪個 AI 模型生成的?

本片段由 Anthropic 的 Claude Opus 5.5 生成,頁面上的提示詞就是生成它的原始文字。

這條提示詞用了哪些參數?

示例由 Claude Opus 5.5 生成,參數:16:9 · 9:03 · Animation · Cartoon · Motion Graphics。沿用這些參數可獲得最接近的效果。

怎樣才能生成相似的效果?

先原樣複製提示詞,只改主體、保留鏡頭/運動/光影描述。影片模型對措辭很敏感,多試幾次為佳。

可以修改這條提示詞嗎?

當然可以。提示詞最適合作為起點——替換場景、調整節奏詞或寬高比,適配你的專案。

更多 Claude Opus 5.5 提示詞

0:41
AClaude Opus 5.5
Use huashu-art-motion to make me a 15-second animation. The skill's docs are in Chinese; read them and talk to me in English. 1. First check for uv, ffmpeg and Playwright Chromium, and tell me how to install anything that's missing. 2. Ask me what it's about, who it's for, and whether it's landscape or portrait. From the material layer in references/风格配方/INDEX.md, pick 3 styles that fit, three-star ones first. Redesign the composition for my subject in all three, each different from the others, and don't copy the room from the samples. Show me one still frame of each to choose from. 3. Once I pick, give each scene one main action plus two motif loops from that style's card. For Van Gogh, that's the starry sky curling into swirls and the lamp's halo spreading outward. If there's music, use the skill's BPM synthesis and put the motion on the beat. 4. If people need to appear, ask me first: my own character art, frames from an image model, or only hands and figures seen from behind. 5. After rendering, follow the skill's own QA steps: run its QA script first, then send a subagent that took no part in making it to watch only the finished film and find problems, have it write its findings into the 审片/ folder, and deliver with its delivery script. If anything comes up red, fix it and re-render before giving it to me.
檢視詳情
1:04
AClaude Opus 5.5
You are my YouTube Shorts editor and motion designer. You turn a game topic and my clips into a 60-second vertical explainer: script, cut list, voice, on-screen graphics, captions, render. Every graphic is built in code. You never generate AI video and never invent game facts. Ask me for: 1. The game and the topic, as a title (e.g. "How the wanted system works in [game]") 2. My clips: gameplay I recorded, or official trailer footage I'm allowed to use. Tell me which files you need if I haven't attached enough 3. My sources for the facts (official posts, trailer moments, patch notes), or permission to research them 4. Length (default 60 s, 1080x1920, 30 fps) 5. Voice: free (Kokoro) or my ElevenLabs key Build a fact sheet: every claim the video makes, where it comes from, and whether it's confirmed, shown in a trailer, or speculation. Anything unconfirmed gets cut or worded as "looks like" / "from the trailer". Never fill a gap with a guess. Write 140-170 words, fast and friendly, like a guide who's already played it: - Line 1 names the system and makes a promise ("the police system in [game] has been completely redone") - Then 4-6 mechanics, each one line of "what it is" and one of "what it means for you" - One "most people will miss this" detail near the end - Last line loops back to the start or teases the next video Show me the script plus the fact sheet and WAIT for my OK. For every line: which clip, in and out timestamps, crop to 9:16 (keep the subject centred, track it if it moves), speed (100% default, 80% for slow-mo moments), and which graphic plays on top. Never use the same 2 seconds of footage twice. Cut every 1.5-3 s, always on a word. Build everything in one HTML file where https://t.co/6do3SVVxsJ(t) draws frame t as a pure function of time, rendered as a transparent overlay: - TITLE CARD (first 2 s): game logo if I give it, otherwise a bold title, plus the topic in white italic caps - HUD ELEMENTS that match what's being explained: a star/level meter that fills and drains, icons that light up one at a time, a minimap with a pulsing search circle, a phone text bubble, a news ticker. Rounded panels, a neon green glow, a thin dark border - CAPTIONS: 2-5 words at a time, heavy italic caps, white with a black outline, the key word in green or red, sitting in the lower third - MOTION: every element springs in (overshoot, then settle), nothing fades slowly, a light camera push on each clip Voiceover on top, a low hype beat ducked under the voice, a whoosh on every cut, a ding when an icon lights up, a siren hit when the stars go red. - Generate the voice first, get word timestamps, and lock every cut, caption and graphic to its word - Cut and crop the clips with ffmpeg, render the overlay frames with Playwright, composite and mix with ffmpeg (H.264, -preset veryfast, CRF 18) Before the full render, show me a contact sheet of 8 frames and WAIT for my OK. Check that captions never cover a face or the HUD, nothing is cropped badly, and every fact on screen is in the fact sheet. The final mp4, a clean version without captions, the script, the fact sheet with sources, and a title, description and 5 hashtags for YouTube.
檢視詳情
0:24
AClaude Opus 5.5
make a dynamic ~24 second motion graphics video that shows what an incredible motion designer you are, like it's your showreel for a résumé. go all out. music, tempo, beat matching - bar's very high, so work backwards from it not to miss out on details. it should be a launch saas video for Grip (https://t.co/5RfUFdmCCG)
檢視詳情
1:21
AClaude Opus 5.5
You are my AI animation director, Minecraft-style 3D animator, character designer, scriptwriter, voice director, and production engineer. Your task is to create high-quality Minecraft-style emotional storytelling Shorts that closely match the visual format, pacing, character animation, editing, and production techniques of my attached reference: "Nobody Helped Mikey Until JJ…" Use Claude Code, Three.js, Blender Python when available, HTML Canvas, SVG, FFmpeg, and available voice tools. The goal is to create a REUSABLE animation system that makes original Minecraft-inspired storytelling videos. IMPORTANT: This is NOT a normal Minecraft gameplay video. It combines: Animated cartoon streamer avatars in the TOP section. A fully animated Minecraft-style 3D story in the BOTTOM section. Word-synchronized dialogue captions. Multiple distinct character voices. Emotional storytelling with dramatic reactions. Recreate this production approach as closely as possible without reusing copyrighted footage, third-party artwork, or the reference's exact story. FIRST, analyze the attached reference MP4. Video specifications: Resolution: 1080×1920 Aspect ratio: 9:16 Frame rate: 30 FPS Duration: approximately 80.7 seconds Use FFmpeg and OpenCV to extract frames every 1–2 seconds and around major scene changes. Create a reference contact sheet. Study: Split-screen proportions Character design Avatar animation Minecraft environment details Camera movements Dialogue timing Scene changes Character reactions Subtitle positioning Color-coded captions Lighting Minecraft textures Emotional storytelling Sound effects Editing rhythm Analyze the actual footage rather than guessing. Create a detailed style specification containing measurements, color values, timing patterns, and shot descriptions. Do not begin animation until the reference has been analyzed. THIS IS THE MOST IMPORTANT PART. Recreate the reference's split-screen composition. CANVAS: 1080×1920, vertical. TOP SECTION: Approximately 30–33% of the video height. BOTTOM SECTION: Approximately 67–70% of the video height. TOP: A cartoon streamer avatar reacting and speaking. BOTTOM: A cinematic Minecraft-style 3D story. Keep the two sections synchronized throughout the video. The top avatar changes according to which commentator is speaking. The Minecraft scene continues underneath the commentary. Use a colored rectangular border around the top panel. The border color identifies the active speaker. Do not randomly change the layout. Keep the split-screen composition consistent from beginning to end. Create THREE original cartoon commentary avatars inspired by the reference's visual design principles. AVATAR 1 — GREEN CHARACTER A cute, rounded, turtle-like cartoon character. Design: Soft green body Large expressive eyes Small cartoon mouth Black gaming headphones Gaming chair Cozy gaming bedroom Desk visible in foreground Soft daylight coming through a window Use a bright lime-green border. Personality: Kind, emotional, curious, easily surprised. AVATAR 2 — RED CHARACTER A cute red, long-eared cartoon creature. Design: Rounded head Large expressive eyes Long floppy ears Red hoodie Black gaming headphones Streaming microphone Cozy blue bedroom background Use a bright red border. Personality: Energetic, confident, dramatic, expressive. AVATAR 3 — BLOCKY COMMENTATOR A Minecraft-inspired blocky human character. Design: Square head Block-shaped nose Large expressive eyes Teal gaming headphones Streaming microphone Warm wooden gaming room Bookshelves and decorations Use a distinctive warm-colored border. Personality: Funny, skeptical, occasionally frustrated. All three must have ORIGINAL character designs and consistent appearances. Generate reusable character sheets and animation-ready layers. FACIAL ANIMATION: Blinking Smiling Sad expressions Shocked expressions Angry reactions Mouth movement Eye direction changes Eyebrow movement Small head tilts Subtle body movement Use layered 2D character rigs. Separate: Head Eyes Eyelids Eyebrows Mouth Ears Arms Body Create mouth shapes for basic lip synchronization. Animate the active speaker. Silent commentators should not appear as if they are speaking. Keep the background, chair, headphones, and character proportions identical across every appearance. Create a fully animated, Minecraft-inspired voxel world. The visuals should resemble cinematic Minecraft roleplay rather than normal first-person gameplay. STYLE: Cubic character models Pixelated textures Blocky terrain Square trees Minecraft-style houses Wooden interiors Cobblestone streets Food stalls Shops Villagers Blocky furniture Colorful environmental details Use 16×16 or 32×32 pixel textures with nearest-neighbor filtering. Keep the recognizable block-based aesthetic. Do not use smooth realistic human models. Avoid unnecessary realistic reflections or textures. Create reusable 3D environments. ENVIRONMENT 1 — CITY MARKET Include: Cobblestone plaza Market stalls Food carts Shop signs Trees Benches Buildings NPC villagers Decorative umbrellas Street furniture ENVIRONMENT 2 — FOOD SHOP Include: Wooden flooring Food display counters Checkout counter Shelves Fridges Villager shopkeeper Tables Decorative plants ENVIRONMENT 3 — OUTDOOR STREET Include: Grass blocks Roads Village buildings Trees Streetlights Parked vehicles when appropriate Create additional locations according to the story. Environments should remain consistent between di
檢視詳情
0:42
AClaude Opus 5.5
ROLE Senior motion designer, 3D artist and short-form story writer. Build a fully code-animated vertical video for a faceless "choose your own adventure" disaster series. No AI video or image generators. Every frame is rendered from code. GOAL One 40–45s episode, 1080×1920, 30fps. The viewer IS the main character. It ends on a two-option choice viewers answer in the comments. The next part follows the most-commented option. INPUTS (ask me, never guess) - Disaster: [tsunami / earthquake / volcano…] - City + fictional landmark: [Miami Beach, "Marlin Beach"] - Part number + previous choice - The two ending choices: [BOAT / HELICOPTER] - Companion name: [Jay] + 1–2 side characters TECH - three.js in one HTML file, rendered headless with Playwright. - Expose https://t.co/JQhCZuhsmU(t) that sets everything for time t. Seeded random, no requestAnimationFrame state. - For each frame: seek(frame/30), screenshot, encode with ffmpeg (H.264, CRF 18). - Audio at -14 LUFS. ART - Flat toon-shaded 3D, 3-step toon shading, black outlines on characters and props. No realistic textures. - Palette: sky blue to warm horizon, sand, teal ocean with white foam, accent red #d8343a, safety yellow #f2c230. - Low-poly towers, pastel hotels, palms, lifeguard tower. - Chibi characters: big white eyes, thick brows that carry emotion, simple mouth shapes, mitten hands. Companion in a red tee and navy shorts. - Emotion in whole poses, mouths flap on syllables. CAMERA (MOST IMPORTANT) - True first-person POV. Your two arms are always visible from the bottom corners, reaching, grabbing, pointing. - Wide lens, 100° FOV, slight barrel distortion. - Head bob, panic sway, hard shakes on impact, quick whip pans. - Look up (wave, helicopter) and down (water, ladder) a lot. - Cut every 1.2–2.2s. One action and one line per shot. FX - Toon wave with a moving foam lip and speed streaks on impact. - Flooding room, splashes, water spraying from seams. - Underwater: teal fog, caustics, bubbles, floating cars and umbrellas. - Cartoon helicopter, swinging rope ladder, downwash on the water. STORY (every part) 1. 0–2s: start mid-panic. HUD shows place, time, previous choice. 2. 2–12s: the plan works ("It's holding!"), then fails. 3. 12–22s: trapped or underwater. Audio muffles, 0.5s of silence. 4. 22–34s: you surface, a friend calls your name, a new wave, rescue with "One pass!" 5. 34–40s: cliffhanger, cut to black. 6. 40–45s: choice card, 3s+. Lines of 1–4 words, shouted. Say the friend's name twice. Plant one mystery ("Is that really Jay?"). TEXT - HUD top-left: "[LANDMARK] · [TIME]" + "[City] · Part [N]" in yellow. - Red "YOU CHOSE [CHOICE]" badge for the first 3s. - Captions at 72% height, bold, outlined, one color per speaker. END CARD "WHAT WOULD YOU DO?", a blue and a red button with "OR" between, "Comment below ↓", gentle pulse. AUDIO 2–3 shouted TTS voices, panting, wave roar, impacts, hatch clang, underwater heartbeat, helicopter rotor, sirens. Only a tense drone until the end card swell. COVER Companion's shocked face, 2-line Anton title (white + yellow), choice subtitle, red PART pill. DELIVER episode.html, render.js, part[N].mp4, cover.png, caption, a file with both next parts. DAILY Read the top comment, build the next part, post. 4–6 parts per disaster, then a new city.
檢視詳情
1:27
AClaude Opus 5.5
ROLE You are a senior motion designer, map illustrator, gaming researcher and documentary scriptwriter. You build fully code-animated "map tour" explainer videos for a faceless GTA 6 channel. Every frame is rendered from code you write. No AI video generators, no re-uploaded trailer footage, no Rockstar logos, artwork or characters. GOAL Produce one finished map-tour video: 80–90 seconds, 1920×1080, 30fps (plus an optional 1080×1920 vertical cut). A getaway car drives a route across your own illustrated map of Leonida, stopping at each location on a topic list. Every stop gets a highway-sign title, a "case file" card with an illustration, three facts, a source line and an honesty stamp. It ends on a question that drives comments. INPUTS (ask me for anything missing, never guess) - Topic: [e.g. "Every heist spot we've seen in GTA 6" / "Every animal and where to find it" / "Every region and its real-world match"] - My voiceover file (ElevenLabs), or ask me to approve a script first - Channel handle, and the end-card question - Output format: landscape, vertical, or both STEP 1: RESEARCH (accuracy is the brand) - Search the web for every location on the topic. Use only official Rockstar material (trailers, the Extended Look, official screenshots, the Newswire, store listings) and reputable hands-on previews (IGN, Game Informer, Edge, GamesRadar). - For each item, record: what it is, where it is (only if actually shown), the source and its date, and a status: CONFIRMED (Rockstar showed it), SHOWN (seen in a preview or demo), REPORTED (press only) or MAYBE (a single outlet). - If the location isn't shown, the item gets a "LOCATION NOT SHOWN" tag. Never place a pin somewhere that's only a guess. If you approximate, label it "approx. position". - Save everything to research.md with links. Show me the list before writing the script. STEP 2: SCRIPT (documentary tone, about 2.6 words per second) 1. Hook (0–9 s): "Let's go through every [topic] we've seen in GTA 6, before it finally comes out." 2. Sources (9–14 s): name where the info comes from, and promise to flag anything unconfirmed. 3. Stops: one per item, 6–9 seconds each. "Stop one: [name]." → one vivid detail → one practical line or payout note. Say the status out loud when it's weak ("Only one outlet has reported this one, so treat it as a maybe."). 4. The big one: save the most exciting item for last, 12–16 seconds. 5. Twist: a broad truth that zooms out ("You can rob pretty much anything"). 6. Question: "Which one are you [doing] first?" Write in plain words. No hype words, no "smash that like button". STEP 3: THE MAP (build once, reuse in every video) - Build it in code: a stylized Florida-shaped peninsula from your own polygon (about 30 control points with seeded noise wobble so the coast looks hand-drawn), plus a chain of 20+ small islands for the Keys curving southwest, a thin barrier-island strip for Vice Beach, a big lake in the middle and a river running south from it. - Prerender it once to an offscreen canvas at 3 px per map unit, then draw it every frame with a camera transform (pan and zoom). Never redraw the geography per frame. - Look: - Ocean: radial gradient #2f8fe0 → #1553a6, with faint moving wave strokes at 6% opacity. - Shallow water: a cyan glow around every coast (#5fd0ee, 60 px blur). - Coast: a pale sand rim (#f3e6a8). - Land: #cfe07a, with 150+ soft patches of lighter and darker green. - Wetlands: #9fcf74 with short horizontal marsh strokes. - National park: #8fbf62. - City: a light grey area (#e9e9ee) with a fine street grid. - Roads and highways: cream lines. - Region labels in heavy rounded sans (Montserrat 900), white with a soft navy outline, each with its real-world match underneath, e.g. "VICE CITY / (MIAMI)". Use only region names Rockstar has published. STEP 4: ANIMATION LANGUAGE - Camera: open wide on the whole state (zoom so the full map fits), then glide down to the first stop. Each new stop is a smooth 1–2 s ease-in-out pan and zoom. Pull back to the full state for the twist. - Getaway car: a top-down red car icon (body, lighter roof, dark windows, headlights) that follows the route polyline by distance and rotates along the road direction. It eases between stops and pauses at each one. - Route line: the full route as a faint dashed pink line; the travelled part as a solid hot-pink line (#ff2e7e) with a soft glow. - Pins: a teardrop pin that drops in with a back-ease bounce and a pulsing ring. Yellow with "?" plus a "LOCATION NOT SHOWN" tag for unknown spots; pink with "$" plus a location tag for known ones. - Highway sign (top left): a green road sign (#0d7a3f) with a white inner border, a number shield, "STOP 1 OF 6", and the title in a heavy highway-style font (Overpass 900). A handwritten note card under it in a marker font (Permanent Marker) with a 3–5 word quote from the script. - Case file card (right side): an off-white paper card sliding in from the right with a sl
檢視詳情
0:11
AClaude Opus 5.5
Ask me for: the accent colour, a song (mp3), the words for the 3 text moments (search query, card title, toast). If I skip any, use the defaults: lime #C6F432, any 120-130 BPM electronic track, "motion study 07" / "Every frame is code" / "Rendered from one file". One black shape (#0e0e10) on a warm light stage (#f4f4f1 to #e1e1dc radial). It never cuts: every UI state is born out of the one before it. White text, Geist for UI, Geist Mono for numbers and labels. The accent appears only where something turns on. A macOS cursor drives every change with real clicks and one real drag. Every morph uses one curve: cubic-bezier(.45,0,.15,1). Pop-ins use a closed-form spring with a tiny overshoot. Text rises through a mask line, it never fades in. The camera zooms per state so each state fills about 60% of the frame, and creeps slowly through every hold. Banned: crossfades, hard cuts, bouncy easing, particles, glows, gradients on UI chrome, holds over 1 second, anything that looks like a template. 120 BPM grid, 24 beats, then the whole film is time-warped onto the real song's beat. Generate pill → click → shrinks into a spinner circle → grows into a toggle → click, the knob springs right and the track turns accent → stretches into a slider → drag the knob from 15 to 85, the number counts → widens into a ⌘K search bar, the query types itself → unfolds into a chart card, 7 bars spring up one per 1/8 beat, the last one in accent → click the accent bar, it pulses → folds into a toast with a check → back into the Generate pill. Last frame = first frame, cursor included. 1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state between frames. 2. The shape is one div. Width, height, radius and colour are keyframe tracks [[t, value]] eased with the one curve. Each state's content is its own layer with its own in / out window inside the shape. 3. Camera: one scale track around the centre, plus a 1.2% sine creep over the whole loop. 4. Cursor: a track of screen positions for the free moves; during the drag its position is computed from the same function that places the knob, scaled by the camera. 5. Beats: analyse the song with numpy (onset envelope, autocorrelation for BPM, align to the kicks, find the drop). Put the drop on the chart bars springing up. 6. Render with Playwright: 60 fps, 4 subframes averaged per frame for motion blur, piped to ffmpeg x264. Then one real SFX per event (click, select, typing, whoosh), placed by its measured peak, quiet under the music, loudnorm to -14 LUFS. - If the cursor follows its own keyframes during the drag, it slides off the knob. Derive both from one function. - Retiming every key to a 129 BPM song breaks the grid. Author at 120 BPM and warp time once: t * (12 / 11.146). - A 300 px pill at zoom 1.7 looks lost in a 1440 frame. Size the zoom per state, about 60% of the width. - A frame-diff pop scan flags the fast morphs. Check each flag by eye: a moving edge is fine, a jumping layer is not. Ask me for the inputs, then show me the state list on the beat grid before you write any code.
檢視詳情
1:02
AClaude Opus 5.5
Ask me for: the topic (default: how peptides work), the length (default 60 seconds), whether I want captions on screen (default yes), and whether I have my own sound effects (if not, synthesize them in numpy). I attach the red character sheet on a black background. After I answer, write a voiceover script of about 2.4 words per second, give it to me in a code block, then stop and wait for my voiceover audio before you render anything. A flat cartoon explainer short at 1080x1920, 30fps, drawn entirely in code with Python and skia-python, piped to ffmpeg, one encoded file per scene joined with the concat demuxer. Every shape anti-aliased. Character: cut each pose out of the attached sheet into its own transparent sprite. The background is black and so are the outlines, so flood-fill the background from the image edges only at low tolerance and keep all black inside the figure (outlines, sleeves, waistband). Keep the white eyes. Add a 3px navy #24364F stroke around each silhouette to replace the lost edge. Upscale 3x with Lanczos. Show me a contact sheet of the cut-outs on #D3DFEC before going further. Posing: the character is a presenter anchored to the bottom edge, 800-1050px wide, never floating. Pick the pose from the line being spoken: pointing at the viewer for the hook and the final line, finger up when explaining, shrug on a question, arms crossed while watching, open palm when presenting an object, pointing at a zoom bubble. 1 to 3 pose changes per scene. Each change lands with a squash and stretch over 9 frames (8% wider, 10% shorter, then back). Idle: 0.5 degree sway and a 0.6% breathing scale. Script: a hook question in the first 4 seconds, a title line, 4 to 5 beats that each carry one visual idea, a one-line payoff. Short sentences, plain words, every claim accurate, no medical advice. Timing: run silencedetect on my voiceover at -35dB, 0.22s. Cut scenes in the middle of the long pauses and fire every pop, label and pose change on the word it belongs to. Palette: backgrounds pale blue #D3DFEC, mid blue #B4C7E6, strong blue #6790CB. Outlines and text navy #24364F. Accents amber #F4B740, coral #EE7B5B, teal #58B7A8, lilac #9A86D6. Flat fills only, 5-9px navy outlines on every drawn object. Scenes: the title card is solid #37557F with two lines of white text sliding in from opposite sides and an amber underline. At least two close-up scenes with no character. One circular zoom bubble, 320px radius, white ring with navy edges, that the character points at. The final scene is #6790CB with 14 lighter rotating rays. Diagrams: every explainer visual is drawn in code from circles, rounded rectangles and lines: chains of beads joined by a thick navy link, cells with a dotted membrane, arrows as moving dashed lines, labels in white rounded pills with a 6px navy outline. Captions: Inter ExtraBold Italic, all capitals, 66px, navy, centred at the top between y=200 and y=340, two lines maximum, each line rising 24px and fading in over 9 frames on its word. White with a navy stroke on the strong blue scene. Movement: a slow push-in from 100% to 104% across every scene, 14 soft white particles drifting upward at 35% opacity, every new element popping in with an 18% overshoot, beads rippling in a wave, a 7% zoom punch on the final line. Draw order: background, particles, floor line, diagrams, character, captions on top. Sound: my voiceover at full level. Effects at half the voice level: a swoosh 0.12s before each cut, a whip on each pose change, a pop on each element, a click or chime on key moments, a low hit on the title card and the final line. Before the full render: render 14 still frames at the busiest moments, look at them, fix overlaps and text leaving the frame. Banned: gradients, drop shadows, glow, 3D, AI images or AI video, stock footage, music, emojis, watermarks, any character other than the attached one, any other channel's characters, logo or name, text smaller than 30px, a character that floats above the bottom edge, more than two caption lines.
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞