LogoAhaPrompt
  • Prompts
  • Featured
  • Models
  • Submit
  • Blog
AhaPromptAhaPrompt

AI Prompts for Images, Video & Audio — Every Model, One Library

Built withLogoNEXTY.DEV
Explore
  • All Prompts
  • Featured Prompts
  • Image Prompts
  • Video Prompts
  • Audio Prompts
  • AI Models
  • Submit a Prompt
  • Blog
Languages
  • English
  • 中文
  • 日本語
  • 한국어

Copyright © 2026 AhaPrompt All rights reserved.

Privacy PolicyTerms of Service
HomeAI Prompt LibraryAI Video PromptsSimple Pomodoro Timer Mobile App

Simple Pomodoro Timer Mobile App

AClaude Opus 5.5Anthropicvideo

Build me a simple Pomodoro timer mobile app using ____. It basically just shows how much time's remaining and then has a nice little alarm sound when it's done. I click on it to change it, the basic stuff. Very simple

Details
Type
AI Video Prompts
Aspect Ratio
4:3
Duration
0:07
Updated
Nov 17, 2026
Category
RealisticMinimalist
Source

How to use this prompt

  1. 1Copy the full prompt with the copy button above.
  2. 2Open Claude Opus 5.5 by Anthropic, or your preferred AI video generator.
  3. 3Paste the prompt and keep the camera and motion terms — they steer the cinematography.
  4. 4Match the example's settings (4:3 · 0:07 · Realistic · Minimalist), then iterate — small wording changes shift the output a lot.

Frequently asked questions

Which AI model generated this video?

This clip was generated with Claude Opus 5.5 by Anthropic. The prompt on this page is the exact text used to create it.

What settings does this prompt use?

The example was generated with Claude Opus 5.5 using: 4:3 · 0:07 · Realistic · Minimalist. Reusing these settings gives the closest match.

How do I get similar results?

Copy the prompt as-is first, then change the subject while keeping the camera, motion, and lighting terms. Video models are sensitive to wording, so expect a few runs.

Can I modify this prompt?

Yes. Prompts work best as starting points — swap scenes, adjust pacing terms, or change the aspect ratio to fit your project.

More Claude Opus 5.5 prompts

0:27
AClaude Opus 5.5
Recreate Flappy Bird as if it launched in 2026. Make it a single playable HTML file.
Details
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.
Details
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.
Details
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.
Details
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.
Details
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.
Details
0:35
AClaude Opus 5.5
### Your mission Design and develop an experimental digital publication called **SIGNAL / NOISE**. It is an independent magazine about technology, artificial intelligence, digital culture, and the future of the internet. We want a website that can compete visually with the best digital editorial design projects. An experience with personality, not another generic SaaS landing page. You have creative freedom to decide the art direction, typography, composition, color palette, animations, and visual system. I don't want you to explain how you would design the website. **I want you to build it.** ### Product The website will have four main components: **1. Editorial cover** A first screen that immediately establishes the publication's identity. It must include the name SIGNAL / NOISE, the issue number (ISSUE 001), a featured editorial piece, and a visual composition that is memorable. **2. Article index** A selection of six fictional but believable articles about technology and digital culture. Don't use six identical cards. Design an editorial composition that allows you to distinguish lead stories, secondary articles, and short content. **3. Reading experience** Develop at least one full article, accessible from the cover. Article title: "The Internet Is Becoming a Place Without People". Include a standfirst, several sections, pull quotes, and some visual resource integrated into the content. It should be a pleasant and carefully crafted reading experience. **4. Navigation and interactions** Implement functional navigation, transitions, hover states, visual indicators, and small interaction details. Animations should add something to the experience, not be gratuitous decoration. ### Technical requirements - React, TypeScript, and Tailwind CSS. - You may use animation and icon libraries. - Responsive design for desktop and mobile. - Basic accessibility, keyboard navigation, and support for `prefers-reduced-motion`. - No static interfaces that only appear to work. - Don't use screenshots of other websites as a substitute for design. - You may use photographs or external visual resources, but integrate them into a coherent art direction. - The project must be able to run locally. ### Design criteria We are looking for: - A distinctive and recognizable visual identity. - Excellent typographic hierarchy. - Compositions that use space with intention. - A good balance between experimentation and usability. - Carefully crafted microinteractions. - Consistency between cover, index, and article. - A designed mobile version, not simply compressed. Avoid: - The generic look of a template. - Six perfectly aligned cards. - Decorative gradients with no function. - Flashy effects that hinder reading. - Unnecessary UI components. - The typical appearance of an AI product landing page. ### Creative freedom You don't have to follow any specific visual reference. You decide what SIGNAL / NOISE means as an editorial identity and how it should be expressed visually. You can be experimental, minimalist, brutalist, sophisticated, or adopt a completely different direction. What matters is that your decisions make sense as a whole. ### Deliverable Build the complete project. When finished, make sure it works and provide a brief explanation (maximum 200 words) of the main art direction decisions. **Don't ask me questions or request approval of the visual direction. Make the decisions and execute.**
Details
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.
Details
Browse all Claude Opus 5.5 promptsExplore AI Video Prompts