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

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

探索

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

工具

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

資源

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

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

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞土耳其共和国日竖屏Reels视频

土耳其共和国日竖屏Reels视频

AClaude Opus 5.5Anthropicvideo

用附件文件为10月29日共和国日制作一个9:16竖版Reels视频。视频开头我的画面占半屏,2-3秒全屏。使用Wikimedia Commons上真实的、公共领域的档案照片。音效从Openverse获取,仅限CC0。背景放一首适合共和国日的无版权进行曲,但音量要低。添加逐词字幕,将所有内容与配音精确到秒对齐。使用Remotion和HyperFrames。

詳細資訊
类型
AI 影片提示詞
畫面比例
9:16
Duration
1:13
更新於
2026年10月29日
分類
HistoricalShort FilmHoliday
Source

如何使用這條提示詞

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

常見問題

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

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

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

示例由 Claude Opus 5.5 生成,參數:9:16 · 1:13 · Historical · Short Film · Holiday。沿用這些參數可獲得最接近的效果。

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

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

可以修改這條提示詞嗎?

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

更多 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.
檢視詳情
0:58
AClaude Opus 5.5
Create a pure javascript animation. 30s-60s stop motion paper craft style video with appropriate audio on the topic what is docker containers and how they work. Entire video should be as high of a production value as possible. Please spend your time on this, it's very important. Use high quality text-to-speech model for generation. You can find open router API key in .env file. You can use any tools you can find access to and resources on the internet. You create the script, the assets, the animation, concept, everything. work autonomously until done. Quality is paramount. Production value should be on professional level. One more thing: max OpenRouter spend is $6.99
檢視詳情
1:00
AClaude Opus 5.5
Make a one-minute video about the Dodaios mascot (image attached). Research the Dodaios story yourself and tell it. Recreate the mascot from the image and animate it yourself. Build everything from scratch: no skills, no Remotion, no templates. Render 3D objects: terminals, nature, whatever fits, and make it as good as you can. I don't want any text, just animation, and I mean a real video, not just motion graphics. Think of crazy ideas I would never come up with, and make every scene look phenomenal: clean and detailed. I want people to watch it and think "yo, this is crazy, how did AI make this?" You can take inspiration from things online, but don't copy anything. Invent your own stuff. For the sound, no sounds made in code. Only use free, professional sounds and assets from online. Make it satisfying and high quality. Don't create slop, I want to see art and creativity. No fonts, no text, only clean animations of the Dodaios mascot. ultracode
檢視詳情
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.
檢視詳情
1:01
AClaude Opus 5.5
You are my AI animation studio, scriptwriter, illustrator, character animator, and production engineer. Your task is to create professional 2D animated explainer videos matching the visual language, character proportions, animation techniques, colors, pacing, and scene composition of my attached reference video, set.mp4. Use Claude Code, Python, SVG, HTML Canvas, JavaScript, FFmpeg, Playwright, and available audio tools. This must be REAL 2D cutout/vector animation, not AI-generated static images with zoom effects. Reproduce the reference's production characteristics as closely as possible while creating original characters, scenes, dialogue, and artwork. FIRST, inspect my uploaded video using FFprobe, FFmpeg, and OpenCV. Reference specifications: Resolution: 1920×1080 Aspect ratio: 16:9 Frame rate: 30 FPS Duration: approximately 61 seconds Style: Flat-vector animated documentary explainer Extract frames every 1–2 seconds and create a contact sheet. Study these specific sequences: 0–14s: Dark underwater environment, animated submersible, glowing blue depth, rocks, pressure gauge, and camera zooms. 14–22s: Dramatic transition into a passenger scene with expressive characters, colorful lightning effects, speech bubbles, and an explosion illustration. 22–31s: Warm beige office with an animated presenter, desk, computer, framed pictures, and an investigation displayed on a monitor. 31–45s: Underwater technical explanation using side-view machinery, depth indicators, warning graphics, and equipment close-ups. 45–53s: Bright turquoise laboratory with a scientist, microscope, flasks, machinery, and animated technical details. 53–61s: Gray industrial facility with engineers, business characters, machinery, gestures, speech bubbles, and approval graphics. Analyze the actual frames rather than relying only on these descriptions. Identify the reference's colors, character proportions, background geometry, camera movement, scene lengths, transitions, and animation patterns. Create a style specification before producing anything. This is the MOST IMPORTANT section. Use clean, flat 2D vector artwork. STYLE RULES: Large rounded cartoon heads Small simplified torsos Oversized circular hands Short rounded arms Simple geometric clothing Large expressive eyebrows Small stylized eyes Simplified noses and mouths Rounded hair shapes Minimal or no exterior outlines Flat solid color fills One darker shade for shadows and depth Soft, muted colors No realistic textures No 3D shading No photorealism Characters should have the same simplified, slightly exaggerated proportions and readable facial expressions seen in the reference. Create original character designs in this visual language. COLOR PALETTE: Underwater: Deep navy #061722 Ocean teal #064760 Dark rock blue #142D3E Highlight blue #0D7BA4 Office: Cream #FFF8E7 Warm beige #C9C3AA Brown #653A28 Coral red #DF5A69 Laboratory: Turquoise #16C2C6 White #F7F7F7 Dark charcoal #263139 Light gray #D6D9DC Industrial: Steel gray #AAB8C3 Pale blue #D1E4F2 Orange #FF883B Use colors appropriate to the setting while preserving the reference's overall art direction. Keep artwork crisp at 1920×1080. Create reusable 2D vector character rigs. Generate character sheets containing: Front view Side view Three-quarter view Sitting pose Walking pose Pointing pose Surprised expression Angry expression Worried expression Talking expression Separate: Head, torso, hair, eyes, eyebrows, mouth, upper arms, forearms, hands, and legs. Animate using hierarchical transforms and joint pivots. MOVEMENT: Head nods and slight rotations Eyebrow movements Blinking Mouth synchronization Arm gestures Circular hand movement Small body bounces Walking cycles Reaction poses Hands should remain large, rounded, and mitten-like. Use simple geometric animation rather than realistic anatomy. Keep characters visually identical throughout the video. Never regenerate a different-looking version of the same person. Build complete vector environments. Each scene must have separate background, midground, character, and foreground layers. Create reusable scene types: Underwater: Gradient-like flat-color depth, large layered rock formations, abstract rounded background shapes, particles, and equipment. Office: Cream walls, rounded furniture, illustrated computers, lamps, clocks, framed pictures, and warm lighting. Laboratory: Turquoise background, microscopes, test tubes, flasks, machines, pipes, and technical illustrations. Industrial: Steel beams, windows, pipes, platforms, railings, large machines, and engineers. Create additional environments as required by the story. All environments must share the same vector illustration style. Do not use stock photography or generic AI backgrounds. Use separate SVG shapes and layers so objects can move independently. Ask me for a video topic or suggest 5 interesting documentary/explainer ideas. Default video length: 55–65 seconds. SCRIPT STRUCTURE: 0–5s: Dramatic hook with an immediate visual action. 5–14s: Establish the situation and stakes. 14–23s: Show characters experiencing the situation. 23–32s: Introduce a person, discovery, investigation, or explanation. 32–44s: Explain the mechanism through machines, diagrams, measurements, or comparisons. 44–53s: Show the scientific or technical consequences. 53–61s: Deliver the reveal, conclusion, or unexpected twist. Use natural, engaging narration. Every sentence must have a visual action. Avoid filler and unnecessary exposition. Fact-check factual clai
檢視詳情
0:34
AClaude Opus 5.5
Ask me for: my map story in one line (a place, border, island, route or line on the map with one surprising fact) and the length (30-45 s). If I have no idea, pitch me 3 with a hook line each and let me pick. Check every fact on Wikipedia before you write a word. A 1920x1080 30 fps map explainer in the Johnny Harris / RealLifeLore look, made 100% in code as one HTML canvas page. Real satellite imagery for the close-ups, a vintage paper map for everything wider, red marker drawn on top. Satellite: Sentinel-2 cloudless 2016 tiles from EOX (CC BY 4.0, credit "Imagery: Sentinel-2 cloudless 2016 by EOX, contains modified Copernicus Sentinel data" small in the corner). Cut the land out and lay it over a drawn navy sea (#14304A centre to #0B1E31 edges) with a soft teal shallow-water halo (#2A6274). Paper map: ocean #A9C2C4, land #ECE2CA, countries in muted pastels (#E6C1A7, #EEDAA4, #D2DEB8), coast dark brown 1.25px over 3 soft water-lining strokes (30, 19, 10px), dashed brown borders, a 10° graticule at 26% opacity, labels in Cormorant Garamond 700 letter-spaced 8-16px. A paper texture multiplied over everything (85% on paper, 22% on satellite), 7% film grain, warm vignette. Red marker #D9291D, 7-10px, round caps, wobbling and re-drawn at 8 fps so it boils like ink. Handwriting in Permanent Marker. Callouts are physical paper: cream tags with a colour bar and a strip of tape (Oswald 700 54px title, Special Elite 28px subtitle typed in), torn strips with a yellow highlighter swipe, tear-off calendar pages, a red rubber stamp. A live lat/long readout in Special Elite bottom left on satellite shots. Banned: AI video or image generation, stock footage, word-by-word captions, hard cuts (one continuous camera only), any frame where nothing moves, icon packs, glossy gradients or glass UI. Length: 30-45 s at about 175 wpm, one continuous camera, no hard cuts. 0 s open tight on satellite of the subject with the hook line ("From this ___, you can ___"), a red marker circle draws around it on the key word with a handwritten word beside it → name the places: a paper tag slaps onto each one on its name, its subtitle types in on the next word → the key number: a dashed red measuring line or route draws in, with a black tag that counts up to the number → the context: a Google Earth pull-out from satellite to the paper map at continent or ocean scale in about 1.3 s, the big line, border or route draws in red marker with a handwritten label, then dive straight back in → the consequence: 2 physical props (calendar pages, clocks, price tags, flags) pop in on their words and one of them flips → the local twist: torn paper strips with yellow highlighter → the story: a red stamp slams the year with a camera shake, the frame splits into two tinted sides, a tracker card (date, time, counter) and a dotted path with a moving marker that crosses the line on the right word → the ending: pull all the way back to the big map with both sides tinted, a red circle on the subject, and a paper end card whose number gets scribbled out and replaced in marker by the real punchline, held 1.5 s after the last word. 1. Tools (all free, all local). Install what's missing and tell me what you installed: - Python with numpy, Pillow, OpenCV and Playwright (Edge or Chromium) - FFmpeg - faster-whisper small.en, int8 on the CPU - Kokoro (kokoro-onnx) with kokoro-v1.0.onnx and voices-v1.0.bin - d3 7.9, topojson-client 3.1, world-atlas 2.0.2 land and countries at 50m and 10m, Natural Earth ne_10m_geographic_lines (date line, equator, tropics) - Google Fonts: Permanent Marker, Special Elite, Oswald, Cormorant Garamond - one free tense documentary music bed, plus free SFX: pen marker line, writing scribble, paper slide, page turn, tape, whoosh in and out, impact, typing, and whatever the story needs 2. Voice (Kokoro): - Write short lines (about 10 per 30 s) and show me the script before you record. - Kokoro am_michael at speed 1.18, one wav per line, joined, then shrink every pause over 0.28 s to 0.2 s. - Run every place name through Kokoro's phonemizer and respell it until it's right ("Diomede" had to become "Diameed"). - Word times: faster-whisper on the final wav, cut into chunks at every pause. 3. Timing: key every camera move, pop-in, marker stroke and SFX to a word (by its nth occurrence, since "is" and "and" repeat), never to a second, so a new voice re-times the whole film. 4. Map engine: - Web mercator in world units (256 = the globe). Camera = focus point + its screen offset + zoom Z, at 2^Z px per unit. Zooms interpolate Z linearly under a quartic in-out ease. - Rotate the d3 projection so the story's region never touches the antimeridian cut. - Satellite: stitch tiles at 3 zoom levels around the subject (like z9, z11, z13). Mask the land (redder than blue by 4-6 levels after a 1.5px blur, opened and closed, specks removed, holes filled), feather the mosaic edges, fade the finer mosaics in as you zoom. - Satellite fades to paper between Z 9.3 and 7.3. 5. Marker and paper: - Strokes resample every ~26px and wobble ±1.5px (sine plus noise re-rolled 8 times a second). Draw a dark red underlay 1.6px wider, the red core, then a pink 30% highlight offset up-left. Circles go 1.1-1.13 turns. - Pop-ins are a spring (damping 0.48, 19 rad/s) from 55% scale with a small rotation settle. Exits shrink and fade in 0.22 s. - Handheld drift about ±2px and 0.06°, a 16px decaying shake on the stamp. 6. Render: - Every frame is a pure function of time. Playwright seeks it and grabs the canvas. - 8 motion-blur subframes over half a frame, raised up to 40 when the zoom is fast. - Look at a cont
檢視詳情
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
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞