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

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

探索

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

工具

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

資源

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

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

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞3x3网格音乐视频剪辑

3x3网格音乐视频剪辑

AClaude Opus 5.5Anthropicvideo

创建一个高能量的1:1海报网格音乐视频,时长与所提供的音乐完全一致。将画面分割成3x3的等大方格网格,方格之间用细灰线分隔,保持原始素材在全部九个方格中作为一幅连续、清晰可辨的图像。中心方格及其四个边缘相邻方格(上、右、下、左)构成一个十字形核心,完美同步播放,每个方格都有各自独特的视觉处理。四个角方格通过独立的特效和时间变化创造性地延展其相邻的核心方格,绝不进行完全复制。将 aggressive 风格感染在相邻方格之间蔓延,与运动回声、时间偏移、帧重复和冲击冻结的节奏性级联相融合。精确地随音乐触发密集、层叠的视觉效果、闪光、图形符号和连锁反应。让原始素材和配乐引导所有创作决策,使剪辑始终保持不断演变、不可预测且在视觉上壮观震撼。全程保留原始角色、动作和场景的连续性。特效用于增强素材,而非取代素材。保留原始视频的音频,包括对话、音效和环境声,并将其与所提供的音乐自然混合。不要静音、替换或移除原始音频。不要出现任何排版、文字、字母或数字。

詳細資訊
类型
AI 影片提示詞
畫面比例
1:1
Duration
1:01
更新於
2026年10月25日
分類
VFXMotion GraphicsMusic Video
Source

如何使用這條提示詞

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

常見問題

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

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

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

示例由 Claude Opus 5.5 生成,參數:1:1 · 1:01 · VFX · Motion Graphics · Music Video。沿用這些參數可獲得最接近的效果。

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

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

可以修改這條提示詞嗎?

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

更多 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: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: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.
檢視詳情
9:03
AClaude Opus 5.5
Ask me for my topic and my script. If I have no script, write one from my topic. Ask which image model I have: GPT Image 2, or any model that takes reference images at 2K-4K, at about $0.03-0.05 an image. Ask which voice I have: ElevenLabs, or Kokoro for free. Before generating everything, show me a look test: one plate, one character sheet cut out and rigged, and a 10 s shot with typing, a tag and a character who talks and points. Wait for my OK. A 1920x1080 animated explainer in the style of the big flat-vector infographic channels. - Every line of narration is acted out by cartoon people inside a full illustrated place. - All motion is code. There are no AI video generations, just a few still images that code cuts up, rigs and animates. Art: - Flat colour shapes with NO outlines, at most one slightly darker flat shade for form, simple geometric shapes and crisp edges. - Muted palette: dusty blue-grey, slate teal, warm beige, navy, soft purple. Salmon-pink skin, big round heads, dot eyes, small bodies. - Mood comes from the plate's own light: daylight, a cold blue night, warm indoor lamps. Code colours: - ink #2b2d42, red #d62828, orange #f4a261, gold #f6b93b, green #2fb37a, navy #1f2a48 - headline tomato #e2552f and purple #5b3fa6 - grey labels #8a8c9c, white cards #ffffff - Font: Montserrat 800-900 (Google Fonts), all caps on cards and signs. Pace: - A new place every 3-4 s, about 10 places a minute. - Something new arrives every 2 s: a tag, a stamp, a person walking in, a number. - Never hold a still over 1 s. Never have a character who doesn't move. Banned: - outlines, glossy UI panels floating over the art, emoji, burned-in subtitles - any channel's logo or name, photos of real people - facts written on a plain colour card when the place could hold them About 60 images in all ($2-3). Every prompt starts with this style core, word for word: "Flat vector illustration in exactly the same art style as the reference images: NO outlines or line art anywhere, every shape is a flat solid colour fill with at most one slightly darker flat shade for form, simple geometric shapes, crisp clean edges, no gradients, no texture, no painterly lighting. Muted modern palette: dusty blue-grey, slate teal, warm beige, navy, soft purple, salmon-pink skin. No text, no letters, no numbers, no logos." Then add one line that locks the setting ("The setting is [time, place]: [materials, light sources], nothing from other eras unless asked"). Feed 3-5 frames of a reference channel in as style references, with their logo cropped off. 1. Hero plates, about 24, one full 16:9 image each, for places you zoom into or come back to. - EMPTY: "no people, no characters, no animals". - Straight-on, with an open floor in the middle where characters will stand. - Blank signs, boards, screens and pages that code writes on later. 2. Quad plates, about 19, giving 76 more places. Pack 4 places into one image: "The image is a 2x2 grid of FOUR completely separate scenes, each filling exactly one quarter of the image (each quarter is itself a 16:9 picture), divided by perfectly straight thin pure-white gutters, one vertical down the exact centre and one horizontal across the exact centre." - Then describe the TOP-LEFT, TOP-RIGHT, BOTTOM-LEFT and BOTTOM-RIGHT scenes. - Split each quad on the brightest white row and column near the centre, walk out while the line stays over 60% white, and trim 6 px more. - Crop each tile to 16:9 at 1920x1080. - Object close-ups make great tiles: a desk, a screen, a document, a plate of food, a vault. 3. Main characters, 2-3 of them. Write one fixed description per character (age, hair, face, every piece of clothing with colours) and paste it word for word into every sheet. - Base sheet: 6 views. (1) front, neutral, drawn WITHOUT ARMS, only round smooth shoulder sockets where the arms would join; (2) the same armless front with a second emotion; (3) side view walking right; (4) seen from behind; (5) and (6) two poses the script needs. - Expression sheet: 6 armless fronts (hopeful, disgusted, terrified, exhausted, sick, shocked, or whatever the script needs), with the base sheet as a reference. - Pose sheet: 6 full poses with their props (sitting at a desk typing, sleeping, eating, running, signing, falling), with the base sheet as a reference. 4. Everyone else: role sheets of 4-6 people, each drawn in the exact pose their shot needs; crowd sheets of 8-10 small figures; prop sheets. - Every sheet: "on a solid flat chroma green background (#00B140) with lots of empty green space between figures; nothing touches, nothing on any character or object is green, full bodies, nothing cut off by the edges". 5. Thumbnail art: the same characters with richer saturated cartoon lighting and extreme emotions, the top quarter left free, no text, with the base sheets as references. Cutouts: - The background is every border-connected pixel with G - max(R,B) over 40 and within 110 of the median green. Key only from the border, or dark clothes leak. - Add a 2 px soft alpha band and clamp G to max(R,B) + 6 inside it, which kills the green fringe. - Group the pieces by figure and drop specks. Name every sprite, and show me a named contact sheet. Armless front figures become puppets: - Split the head at the neck: the narrowest alpha row under the head. - Find both shoulder sockets and the eye boxes. - Inpaint the hole under the head from the body's own colours, so a nod never shows a gap. - Write everything to rig.js: size, neck, sockets, eye boxes, skin RGB, sleeve RGB. - Arms: upper L1 about 0.13 of the figure's height, lower L2 about 0.12, thickness about 0.04. Use sleeve colour to the
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞