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

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

探索

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

工具

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

資源

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

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

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞模拟恐怖Wi-Fi规则解说

模拟恐怖Wi-Fi规则解说

AClaude Opus 5.5Anthropicvideo

问我:一个前提,格式为“如果你的___曾经___……不要___”(默认:“如果你的Wi-Fi曾经显示一个带有你名字的网络……不要连接”),时长(默认约5:20,大约700个口语词),一个强调色(默认暖琥珀色#FFB547),以及你将把旁白作为MP3上传还是由我生成(ElevenLabs密钥,如果没有则使用免费的本地语音)。 一个1920x1080、30fps的模拟恐怖“生存规则”解说视频,完全用代码绘制:一个HTML页面,一个全帧SVG用于场景,HTML图层用于HUD和字幕。 背景:纯近黑色#060606,从52%半径到rgba(0,0,0,.5)的暗角,以及每帧重新随机化的2%胶片颗粒。没有其他东西:没有扫描线,没有闪烁,没有调色。它必须读起来像深黑色,带有柔和发光形状。 图标:纯灰白色#ececec,圆角,填充形状无轮廓。一个人(头部r46,圆肩身体132x122,无面部),一个手机轮廓(12px描边,半径为宽度的14%),Wi-Fi符号(点r15,弧r62/118/174,22px描边,各90°),房屋,一个路由器(340x110机身,两根天线,4个状态灯r11),一个挂锁,一扇门,一张床,一个躺着的人形,一个平面图,4格信号条。 发光:场景组上一个SVG滤镜,5px模糊、70%透明度,加上22px模糊、38%透明度,合并到清晰源下方。柔和光晕,绝不泛光。 强调色:仅用于异常。标有YOUR NAME的网络行、其Wi-Fi弧线、填充的信号条,以及一个4角括号框(12px描边,50px腿长),会 snap 到任何“副本”上。红色#E5322D仅用于一个印章和一条斜线。 HUD为灰色#6f6f6f等宽字体20px,.2em字距:左上角案件编号,右上角运行时间码HH:MM:SS:FF,顶部中央七个24px编号框,规则通过后填充强调色,当前规则为白色描边。 规则卡:“RULE”为#d9d9d9 Montserrat ExtraBold 190px,数字居中,dominant-baseline central,置于190px强调色圆角框(半径26)中,一条600x7强调色线,然后规则为白色大写52px,.08em字距。规则7使用倾斜的红色REDACTED印章代替文本。 字体:仅Montserrat 600-900,外加一个等宽字体用于HUD。字幕大写,Bold 50px,.035em字距,一次一句,白色带4px/14px柔和发光,关键词(CONNECT、DISCONNECTED、FAMILIAR、YOU)使用强调色,居中,距底部110px。 收尾:RGB分离(红色和青色投影偏移4-18px),9条水平撕裂条和x轴抖动,仅在故障时刻出现。 禁止:颗粒超过3%、扫描线、亮度闪烁、硬切、文字运行到图标下方、任何形式的阶梯动画、图标上的渐变、AI图像或AI视频、任何真实频道的角色、名称、标志或口头禅。 约5:20,每句话都有自己的镜头或变换,没有任何东西保持静止。唯一的威胁,在1:00前陈述,并被每条规则保护:网络正在学习你,以便成为你,而且因为两个设备不能共享一个名字,你们中的一个会被断开连接。 一个手机Wi-Fi列表,行以0.35s间隔滑入,YOUR NAME行脉冲强调色(0s)→ 在“rename”时,一个文本光标在HOME_WIFI行中闪烁(5s)→ 在“walk”时,一个房屋剖面,一个人形从一个房间走到另一个房间,其Wi-Fi信号条上升(7s)→ 在“seven rules”时,七个框以弹簧效果弹出,四个在“four”时亮起,框7在“seventh”时获得括号(14-18s)→ 一个标题卡(22s)→ 再次列表,NEIGHBOUR、PRINTER和FBI_SURVEILLANCE_VAN在各自词语上高亮(26-34s)→ 房屋广播圆环(36s)→ 在“yours”时,一个新的YOUR NAME行滑入(44s)→ 在“no lock”时,一个打开的挂锁(47s)→ 在“full bars”时,弧线平滑填充,一个人形在“close”时出现在符号下方(49-51s)→ 在“learns a phone”时,粒子在手机和路由器之间反向移动,一条消息、钥匙、键盘和月亮图标在各自词语上落位(55-65s)→ 一个COPY条从60%缓动到94%,在“finishes”时达到100%并出现括号(67-72s)→ 两个相同的人形在同一个名字下,一个在“disconnected”时闪烁消失(75-81s)→ “ONLINE 0 DAYS”对“ONLINE 214 DAYS”(85s)→ RULE 1卡(86s)→ 在“copy of you”时,一个路由器变形为一个带括号的人形(106s)→ 在“familiar”时,列表显示HOME_WIFI · AUTO-JOIN旁边是YOUR NAME · NOT SAVED(110s)→ RULE 2,一个拇指悬停在Wi-Fi开关上,副本人形在每次“guessing”时抖动得更厉害(119-140s)→ RULE 3,一个平面图,信号条随着点的移动滑动到2、3、满格,括号在卧室门口(142-150s)→ 在“two of you”时,第二个人形在门旁淡入(158s)→ 一个案件文件,带有涂黑条和DISCONNECTED印章,两行相同的HANNAH · ROOM 12,两部手机,两个人形,一个在“disconnected”时淡出(167-189s)→ RULE 4,插头滑出,从30开始倒计时,路由器灯一个接一个熄灭,YOUR NAME仍然发光(194-212s)→ 在切断词上,缓慢推近一个带括号的人形,然后1.4s静电爆发,RGB分离和撕裂条(214s)→ SIGNAL RESTORED以等宽字体显示(216s)→ RULE 5,波从墙到沙发再到你反弹,一个虚线副本比人形慢一拍跟随,一个呼吸波形达到MATCH 100%(220-250s)→ RULE 6,一个设备列表逐行填充,UNKNOWN · SAME MODEL · 02:14以强调色显示,一根手指悬停在REMOVE上并停下,括号在“real”时在两个人物之间跳跃(252-277s)→ RULE 7带有REDACTED印章,RULE 1卡的幽灵,行变为CONNECTED(279-300s)→ 在“disconnected”时,一个人形带着故障淡出,括号在“which”时在两者之间闪烁(305-312s)→ 最后一个词以强调色巨大显示,一个嗡鸣声增强,在一个boom上切到黑(318s)。 对于任何其他前提,保持相同形状:威胁在早期陈述,o

詳細資訊
类型
AI 影片提示詞
畫面比例
16:9
Duration
5:23
更新於
2026年10月26日
分類
HorrorMysteriousDark
Source

如何使用這條提示詞

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

常見問題

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

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

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

示例由 Claude Opus 5.5 生成,參數:16:9 · 5:23 · Horror · Mysterious · Dark。沿用這些參數可獲得最接近的效果。

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

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

可以修改這條提示詞嗎?

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

更多 Claude Opus 5.5 提示詞

0:34
AClaude Opus 5.5
Ask me for my animal or topic ("Why is the X the most disturbing animal in the ocean?", "Why is X terrifying?"), or pitch 3, each with 5 true facts that get worse as they go. Ask which image model I have (GPT Image 2 or any model that takes a reference image at 4K, about $0.03 an image) and which voice I have (ElevenLabs, or Kokoro for free). Then write the script and the shot list with seconds, and show me both before anything costs money. A 1080x1920, 60 fps, 30-35 s vertical Short in the style of the big narrated animal-facts channels where a guy in a hoodie with a mic pops into every scene. Here everything is a flat 2D cartoon: thick dark brown outlines (#1f1418), flat colours, simple cel shading, big round googly eyes. The host: a cartoon young man with messy brown hair, glasses, a plain heather grey hoodie with no logo, dark jeans, white sneakers, always holding a black mic. - He is about 1000-1050 px tall on screen. His feet sit below the frame edge, so he is cut off at the shins. - He pops up from below the frame in 0.32 s with an overshoot ease. - His mouth flaps on the voice whenever he talks to camera. - His face always stays above the caption pill. The animal: one character in 9 poses (neutral, shocked, angry, plus costume poses for the facts: old with a beard and cane, a powdered wig, a teen with braces, drunk, a front view of the face, defeated on a plate). One costume per fact is the joke. A new place every 1.5-3 s. Never repeat a composition. Something always moves: - Animals swim with a tail wave and bob ±10 px. - The camera pushes in 2-4% per shot. - Pose swaps squash. - Hits shake the frame. Titles are one or two big words per beat in Luckiest Guy (Google Fonts), 104-190 px at y 430, tilted ±0.03-0.05 rad: - They wobble ±0.025 rad. - The outline is 0.22 of the size in #1f1418, with a darker copy of the colour 0.09 of the size underneath. - Colours are pairs of fill and shadow: yellow #ffd21f/#c27a10, red #ff4a3d/#8e1a14, white #ffffff/#9aa6b4, pink #ff7ab8/#a8336d, green #7dff6a/#2e9a2a. Captions: - 1-4 words in a white pill at y 1470: Luckiest Guy 66 px, dark text, a 7 px outline, pill height 1.55x the text. - The key word is yellow with a dark outline. - The pill pops from 0.82 to 1 in 0.13 s. A red marker ellipse circles the animal when its name is said. Banned: photoreal cutouts mixed into cartoon art, a real person's face, the real channel's logo or name on screen, a still frame over 1 s, the host covering the animal's face on its key word. Length: 30-35 s, about 115 words at about 3.5 words a second. Times are from a 33.5 s film; scale them to the voice. 0-1.9 s, the hook "Why is the X the most disturbing animal in the ocean?": - The animal glides in from off screen in 0.75 s while the host pops up bottom right, already talking. - On the animal's name: a red ring, the name as a title, and the host swaps to pointing at it for 0.7 s. 1.9-3.7 s: a punch-in on "disturbing". The water is graded red, the angry pose, an impact starburst, the word in red. 3.7-8.2 s, fact 1, the shocking number: - A counter rolls up to it. - Then a comparison everyone gets ("older than America") shown as a costume pose and a prop that springs in. 8.2-12.7 s, facts 2 and 3 played as gags: - One is a costume in a new place. - One is a race the animal loses. On "slower than you walk", the host strolls past it. 12.7-15.6 s: the gross detail, with a zoom into the face. 15.6-16.7 s: "But it gets worse." A red alarm grade with a pulsing vignette. The animal yells into the lens and the host swaps from talking to horrified. 16.7-21 s, the worst fact: - The host cowers behind the victim, which then vanishes in a poof. - An x-ray shot shows what is inside. 21-27.7 s: the human angle, each line with a person from the cast acting it out. The host joins in (drunk next to the drunk Viking). 27.7-29 s: someone happily eats it while the host turns green and gags. 29-33.5 s: the callback joke that ties back to the hook. The host talks to camera, then cracks up on the last word. Hold 1.15 s after the last word. 1. Tools: Python, Playwright with Chromium or Edge, FFmpeg, OpenCV, Pillow, numpy, soundfile. Install what's missing and tell me what you installed. 2. Art, 4 images in total (about $0.12). Every prompt starts with "Match the exact art style of the reference image: flat 2D cartoon, thick dark brown outlines, flat colours with simple cel shading, big expressive googly eyes, clean vector look". Feed the first sheet you like back in as the style reference for the rest. - Animal sheet: 1:1 at 4K, "a 3 by 3 pose sheet of the SAME cartoon X, 9 separate poses on plain pure white, plenty of white space, nothing touching, no grid lines, no text, no ground shadows", every pose a full side view facing right except the front face. - Cast sheet: 1:1 at 4K, 9 different characters and props for the facts, same wording. - Background grid: 9:16 at 4K, "a 3 by 3 grid of 9 equal tall vertical panels separated by thin white gutters, each panel an EMPTY scene, no characters, no text, keep the lower middle open". - Host sheet: 9:16 at 4K, 9 full-body poses at the same size: (1) facing the viewer, mic below the chin, mouth CLOSED, (2) EXACTLY the same pose with only the mouth WIDE OPEN, (3) talking and pointing to the side, (4) horrified with a hand on the cheek, (5) crouching and cowering with sweat drops, (6) running in side view facing right, (7) laughing and leaning back, (8) gagging with a green face holding a toothpick of food, (9) drunk with spiral eyes. 3. Cutouts: - Flood the white from the border (seeds every 64 px around the edge) with a floating range of 7, so soft glows go too. - Feather a 3 px band outside the shapes with alpha = clamp((250 - min(R
檢視詳情
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:23
AClaude Opus 5.5
Ask me for: my video idea (one line is fine), the setting, the length (60-90 s) and the narrator (an ElevenLabs voice, or "free" for a local text-to-speech). Everything is built in code: no AI images, no AI video. Make it MY story, not a copy of an example. The style is a second-person survival thriller with stickmen, built as a series: - "Imagine you…" hook with a time stamp in the first 3 s - a HUD with the DAY number and a clock that moves forward through the episode - 3-4 RULES, each one paid off on screen - a threat that escalates and is mostly shown, not told - a twist that makes one rule impossible - a two-choice ending ("DO YOU OPEN IT?" style, a green and a red option, "COMMENT BELOW") and "FOLLOW FOR DAY 2" Around 20-30 voice lines, 60-90 s, a new shot every 1.5-3 s. Write a beat sheet and the script first and show me both before building anything. - One line = one visual. Rules are short commands. - Open a new question every ~10 s and only answer it with a bigger one. - Put the viewer in POV for the scary parts: what you see through a door, a window, a phone, a peephole. - The ending is a choice where both options look bad. - Write numbers twice: the caption form ("11:58 PM") and the spoken form ("eleven fifty-eight P M") for the text-to-speech. - Rotate settings between episodes (apartment, subway, school at night, hospital, cabin, plane, office, motel) and fit the threat to the setting. Pick a palette per story, but keep the language: - real 3D low-poly sets with real lights and shadows; the mood comes from light (one warm practical, one cold fill, one strong accent such as a door gap, a screen or a siren) - the stickman is flat and 2D-looking: a light body with a thick dark outline, round strokes, dot eyes, no mouth; give the main character one mark (a scar, a cap, a colour) so doubles and callbacks read - the overlay: a monospace HUD top-left, chunky captions (1-3 words, key words in an accent colour), a tilted rule sticker with a big condensed title, phone screens drawn in 2D - banned: AI frames, glossy 3D characters, emojis, music with vocals, long captions A library to adapt to the story (never use all of them): - the opener: a camera move that starts tight on you and pulls out to show where you are - POV phone in your hands (2D phone UI, two stick thumbs) - a macro on the one detail that matters - outside chaos from above (balcony, bridge, window): physics vehicles, a running crowd, something collapsing or burning - third-person action in the room: walking with planted feet, reaching, hesitating, barricading - POV interaction: throwing, holding a torch, opening something - a close-up of your face for the reaction - a low angle on a door or vent: light leaking in, shadows moving - knocks, shakes, things falling - a fisheye peephole, camera or window view of the threat stepping closer - the choice screen and the end card What each tool is for. Install whatever is missing, and ask me before anything paid: - three . js: the 3D engine; it runs inside a web page. Download its module file locally so renders don't depend on the internet. Use its post-processing passes for bloom, plus one custom lens shader for vignette, grain, fisheye and colour fringing. - cannon-es: a JavaScript physics engine for vehicles, falling debris and collapses. - Playwright (Python): opens the page in a real browser (Edge or Chrome with the GPU on) and captures every frame as an image. - ffmpeg: the command-line video and audio tool. It joins the frames into an MP4, cuts and filters the audio (highpass, lowpass and echo for voices behind doors), mixes, normalises loudness and makes the phone-size copy. - ElevenLabs, or Kokoro (free local text-to-speech), for the narrator. - faster-whisper: free local speech-to-text with word timestamps. Use it to cut the voice cleanly and to time every caption. - numpy and Pillow: to check audio levels and make contact sheets of stills. - Sound: free downloaded sound effects from Mixkit (never synthesized) and a dark cinematic drone or tension bed with no vocals. 1. One HTML page (film . html) with the 3D renderer at 1080x1920 drawn into a 2D canvas that also holds the overlay. A function window . seek (t) draws frame t and must be a pure function of time; every cut, sound and move is keyed to the word times. 2. Stickman. Draw each figure with 2D canvas strokes onto its own texture and put it on a plane that always faces the camera, with an alpha test so it casts a real shadow and slight emissive so it reads in the dark. Pose with joint angles, and walk with 2-bone IK so the planted foot never slides. 3. Physics and cloth. Simulate once at load with a fixed timestep, record the positions, then sample them by time, so every render is identical. Cloth (sheets, curtains, flags) is a verlet particle grid with wall and floor collisions and pinned points you can release. 4. Voice. If you generate one long take, never cut it at the API's character timestamps: they drift and slice words. Transcribe the take with faster-whisper word timestamps, match it to the script, cut only in real silence between lines, and only add pause where the natural one is too short. 5. Captions. Re-transcribe each final line, normalise numbers ("6:42" = "6 42", "AM" = "a m"), align the caption words to what was heard, and snap each word to its real start in the audio. Check that every caption has voice under it within ~120 ms. 6. Render. Playwright steps window . seek through every frame at 30 fps, and ffmpeg encodes a high-quality master, then a phone copy under 30 MB. 7. Mix with ffmpeg: the voice on top, the musi
檢視詳情
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.
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞