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

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

探索

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

工具

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

資源

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

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

隱私政策條款與條件退款政策版權申訴 / DMCA
首頁AI 提示詞庫AI 影片提示詞简易番茄钟手机应用

简易番茄钟手机应用

AClaude Opus 5.5Anthropicvideo

用____帮我构建一个简单的番茄钟移动应用。它基本上只显示还剩多少时间,然后在结束时有一个好听的小闹铃声。我点击它来更改时间,就是这些基本功能。非常简单

詳細資訊
类型
AI 影片提示詞
畫面比例
4:3
Duration
0:07
更新於
2026年11月17日
分類
RealisticMinimalist
Source

如何使用這條提示詞

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

常見問題

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

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

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

示例由 Claude Opus 5.5 生成,參數:4:3 · 0:07 · Realistic · Minimalist。沿用這些參數可獲得最接近的效果。

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

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

可以修改這條提示詞嗎?

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

更多 Claude Opus 5.5 提示詞

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.
檢視詳情
0:24
AClaude Opus 5.5
Rebuild [any device] in code, part by part: 1. Write the parts list first, with dimensions. 2. Make every part its own function. Place them one at a time. 3. After each part, check clearance (≥ 0.05 mm), clashes and cable bends. Stop and fix anything that fails. 4. Animate the moving parts last. Show me the parts list first. No code until I say go.
檢視詳情
0:35
AClaude Opus 5.5
### Tu misión Diseña y desarrolla una publicación digital experimental llamada **SIGNAL / NOISE**. Es una revista independiente sobre tecnología, inteligencia artificial, cultura digital y el futuro de internet. Queremos una web que pueda competir visualmente con los mejores proyectos de diseño editorial digital. Una experiencia con personalidad, no otra landing genérica de SaaS. Tienes libertad creativa para decidir la dirección de arte, tipografía, composición, paleta cromática, animaciones y sistema visual. No quiero que me expliques cómo diseñarías la web. **Quiero que la construyas.** ### Producto La web tendrá cuatro componentes principales: **1. Portada editorial** Una primera pantalla que establezca inmediatamente la identidad de la publicación. Debe incluir el nombre SIGNAL / NOISE, el número de edición (ISSUE 001), una pieza editorial protagonista y una composición visual que resulte memorable. **2. Índice de artículos** Una selección de seis artículos ficticios, pero verosímiles, sobre tecnología y cultura digital. No uses seis tarjetas idénticas. Diseña una composición editorial que permita distinguir historias protagonistas, artículos secundarios y contenidos breves. **3. Experiencia de lectura** Desarrolla al menos un artículo completo, al que se pueda acceder desde la portada. Título del artículo: "The Internet Is Becoming a Place Without People". Incluye una entradilla, varios apartados, citas destacadas y algún recurso visual integrado en el contenido. Debe ser una experiencia de lectura agradable y cuidada. **4. Navegación e interacciones** Implementa navegación funcional, transiciones, estados hover, indicadores visuales y pequeños detalles de interacción. Las animaciones deben aportar algo a la experiencia, no ser decoración gratuita. ### Requisitos técnicos - React, TypeScript y Tailwind CSS. - Puedes utilizar librerías de animación e iconos. - Diseño responsive para escritorio y móvil. - Accesibilidad básica, navegación por teclado y soporte para `prefers-reduced-motion`. - Nada de interfaces estáticas que solo aparenten funcionar. - No uses capturas de otras webs como sustituto del diseño. - Puedes usar fotografías o recursos visuales externos, pero intégralos en una dirección artística coherente. - El proyecto debe poder ejecutarse localmente. ### Criterios de diseño Buscamos: - Una identidad visual distintiva y reconocible. - Excelente jerarquía tipográfica. - Composiciones que aprovechen el espacio con intención. - Buen equilibrio entre experimentación y usabilidad. - Microinteracciones cuidadas. - Consistencia entre portada, índice y artículo. - Una versión móvil diseñada, no simplemente comprimida. Evita: - El aspecto genérico de una plantilla. - Las seis tarjetas perfectamente alineadas. - Gradientes decorativos sin función. - Efectos llamativos que entorpezcan la lectura. - Componentes de UI innecesarios. - La apariencia típica de una landing de producto de IA. ### Libertad creativa No tienes que seguir ninguna referencia visual concreta. Decide tú qué significa SIGNAL / NOISE como identidad editorial y cómo debe expresarse visualmente. Puedes ser experimental, minimalista, brutalista, sofisticado o adoptar una dirección completamente diferente. Lo importante es que tus decisiones tengan sentido como conjunto. ### Entregable Construye el proyecto completo. Al finalizar, asegúrate de que funciona y proporciona una breve explicación (máximo 200 palabras) de las decisiones principales de dirección artística. **No me hagas preguntas ni solicites aprobación de la dirección visual. Toma las decisiones y ejecuta.**
檢視詳情
0:14
AClaude Opus 5.5
Ask me for: 8 to 12 UI states I want the shape to transform into (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use). Dribbble-level UI motion. One shape, no cuts: every state is the same element morphing its size, radius and color while its content swaps with a quick blur. A cursor controls every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, with only a tiny overshoot. The camera zooms so each state fills the entire frame. The last frame matches the first frame, so it loops perfectly. Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template. 120 BPM, 7 bars, something happens on every beat. Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs expand into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button. One HTML file, square 1440x1440. Every style is calculated from time inside seek(t): no CSS transitions, no timers, no state carried between frames. Springs use closed-form step responses. A value that changes targets multiple times is the sum of one spring per change, so it remains a pure function of time. The tab indicator's two edges follow different springs, so the leading edge stretches ahead of the trailing one. Use the same trick for the toggle knob. Drags use direct manipulation: while the cursor is held, the value is calculated from its position. On release it springs back from wherever it was. Analyze the song with numpy to find the beat grid and start on a downbeat. Position every UI sound by its measured peak. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps. Render one frame per beat before the full render. Fix anything off the grid, cramped or difficult to read. Never put will-change on anything the camera scales or the text becomes blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the final frame identical to the first, including cursor position and speed, or the loop stutters. Ask me for the inputs, then show me the state list on the beat grid before writing any code.
檢視詳情
0:27
AClaude Opus 5.5
Recreate Flappy Bird as if it launched in 2026. Make it a single playable HTML file.
檢視詳情
0:46
AClaude Opus 5.5
Rebuild [any device] in code, part by part: 1. Parts list with dimensions first. 2. Each part its own function. Place one at a time. 3. After each, check clearance (>= 0.05 mm), clashes, bends. 4. Plant 3 faults on purpose. Prove the check catches them. 5. Animate moving parts last. No code until I say go.
檢視詳情
0:20
AClaude Opus 5.5
Ask me for: the product name and a one-line promise, 3 to 5 UI moments to show, one accent color, 10 to 20 real vertical clips I own, and a royalty-free song with a clear drop (e.g. Mixkit, free for commercial use). High-end minimal. One idea per shot, plenty of empty space, one accent color, one clean sans (Geist or Inter) with tight tracking. Masked type reveals, match cuts, one consistent camera language. Real footage only, never placeholder cards. No full stops in on-screen text. Banned: shockwave rings, particle bursts, RGB split, camera shake, lens flares, neon glows, grid floors, flashing backgrounds, bouncy easing. 10 bars at 120 BPM, 2 seconds each. Bar 1: the hook appears word by word on the beats. Bar 2: one hook word morphs into the product UI. A cursor types and clicks. The drop: a circle expands out of the button into a dark scene. Then one move per bar: a wall of real clips with a scan line and 3 winners the key output revealed as big type a 3D carousel of real videos with floor reflections and a motion-blurred whip onto one hero clip the hero inside a phone next to a panel that flips into results big stats on push cuts a 3-word ticker a logo reveal a fade to black One HTML file at 1920x1080. Every style is calculated from time inside https://t.co/knoJJfMFI5(t): no CSS animations, no timers, no state between frames. Real video: extract clips into 30fps JPEG sequences with ffmpeg and swap img sources per frame. seek awaits the image decodes. Analyze the song with numpy: tempo, beat grid, energy per bar, and the drop. Calibrate the grid to the actual kick hits. Every cut lands on a downbeat, every UI hit on a beat. Render with Playwright: 3 subframes per frame at t minus, at, and plus 1/240s, then blend with ffmpeg tmix for real motion blur at 60fps. Place every sound effect so its measured peak, not its file start, lands on the event. Keep the effects quiet beneath the music. Loudnorm to -14 LUFS. Check 20 or more frames before the full render. Fix anything cluttered, overlapping, or difficult to read. Never set opacity or filter on a preserve-3d element, because it flattens and both faces become visible. Fade its wrapper instead. Measure element positions at runtime for accurate match cuts. Only use music and sound effects with licenses that allow commercial use. Ask me for the inputs, then show me a storyboard with every timing mapped to the beat grid before writing any code.
檢視詳情
0:14
AClaude Opus 5.5
Ask me for: 8 to 12 UI states I want the shape to morph into (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), black and white or a single accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use). Dribbble-level UI motion. One shape, zero cuts: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, with just a tiny overshoot. The camera zooms so each state fills the entire frame. The final frame matches the first frame, so it loops perfectly. Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template. 120 BPM, 7 bars, something happens on every beat. Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it transforms into a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs expand into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames. Springs use closed-form step responses. A value that changes targets multiple times is the sum of one spring per change, so it stays a pure function of time. The tab indicator's two edges follow separate springs, so the leading edge stretches ahead of the trailing one. Use the same trick for the toggle knob. Drags use direct manipulation: while the cursor is held, the value is calculated from its position. On release it springs back from wherever it was. Analyze the song with numpy to find the beat grid and start on a downbeat. Align every UI sound by its measured peak. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read. Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, including cursor position and speed, or the loop stutters. Ask me for the inputs, then show me the state list on the beat grid before writing any code.
檢視詳情
瀏覽全部 Claude Opus 5.5 提示詞探索AI 影片提示詞