Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an editable pixel card battle demo video for [PROJECT] and [AUDIENCE]. Build a new result from [APPROVED_CONTENT] and [BRAND_RULES], using the credited reference to discuss composition and timing.
Required Content and Inputs
Introduce two opposing players and a small hand of cards; select a legal action; animate its cost and combat result; resolve the turn with a readable board state.
Ask for exact on-screen copy, authorized assets, intended destination, output dimensions and licensed audio. Identify missing task data before implementation. Keep real claims and sample data distinct; do not invent customer results or capabilities.
Scene Plan
- Introduce two opposing players and a small hand of cards. Define the visible action, its result and the transition anchor.
- select a legal action. Define the visible action, its result and the transition anchor.
- animate its cost and combat result. Define the visible action, its result and the transition anchor.
- resolve the turn with a readable board state. Define the visible action, its result and the transition anchor.
Return a timing table with scene start and end, copy, assets, motion and audio cues. The reference is 15 seconds at 1280 × 720; adapt the timeline to the supplied content instead of forcing unreadable text into that duration.
Motion and Visual System
Build the animation from explicit card, resource and turn records. Snap sprites to a pixel grid while keeping numeric values and interaction highlights unambiguous.
Use the selected project design system. Establish final readable states before animating entrances. Preserve image and logo proportions, separate editable type from raster art and use a restrained hierarchy for supporting labels. Keep one recognizable anchor between adjacent scenes.
Implementation and Audio
Use the existing project stack and an explicit timeline that can be inspected at any timestamp. Store copy, data, colors, scene timing and motion parameters in editable configuration. Seed any randomness so the same timestamp renders consistently. Do not depend on wall-clock timers to define an export frame.
Map supplied music or sound cues to timeline markers. If audio is missing, deliver a silent timing preview first. Do not claim beat or voice synchronization without the actual authorized track.
Review Priorities
- Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game.
Inspect the longest real label, the first and last frame and both sides of each scene boundary. Check phone-size reading, foreground occlusion and the actual output aspect ratio. Compare the exported duration, frame count and audio tail with the approved timeline.
Deliverables
Return editable source, the timing table, one still per scene, a poster and an MP4. Provide the low-cost scene preview before the full render. Distinguish a pre-rendered interface demonstration from working application behavior.
Reference creator: @aisongman. Source: https://x.com/aisongman/status/2103763192971461057
Download Prompt + Video
Download the editable prompt and the creator reference video together. Use both to guide your own motion study.
How to Write a Pixel Card Battle Demo Video Prompt
This pixel card battle demo video prompt focuses on a concrete sequence: introduce two opposing players and a small hand of cards; select a legal action; animate its cost and combat result; resolve the turn with a readable board state. Use the reference checkpoints to decide what remains stable, what changes and how the viewer understands the result.
Reference: @aisongman. OpenDesign editorial adaptation.
Plan the Pixel Card Battle Demo Sequence
Start with a viewer outcome for pixel card battle demo. The scene plan is: introduce two opposing players and a small hand of cards; select a legal action; animate its cost and combat result; resolve the turn with a readable board state. Decide which information each stage introduces and which earlier element the viewer should still recognize. Supply the actual names, assets and task records before choosing decorative transitions. A useful storyboard shows the visible result of each action, not merely a list of effects.
In the Prompt
Introduce two opposing players and a small hand of cards; select a legal action; animate its cost and combat result; resolve the turn with a readable board state.
Apply It to Your Version
For [PROJECT], identify the required inputs for “Introduce two opposing players and a small hand of cards” and the result needed for “select a legal action”. Make one still for each stage and remove any scene that has no supported content.
Control the Motion Mechanism
Build the animation from explicit card, resource and turn records. Snap sprites to a pixel grid while keeping numeric values and interaction highlights unambiguous. Specify the anchor, moving parts and settled state for every transition. Inspect intermediate frames as well as the finished composition: a transition can look polished at either end while its geometry, labels or cause-and-effect relationship breaks in the middle. Keep the motion parameters editable so one failure can be corrected without redesigning the whole film.
In the Prompt
Build the animation from explicit card, resource and turn records. Snap sprites to a pixel grid while keeping numeric values and interaction highlights unambiguous.
Apply It to Your Version
Implement the relationship described above as a small set of named parameters. Compare a slow diagnostic preview with normal playback and identify the frame where the intended relationship becomes clearest.
Allocate Reading Time and Frame Space
The measured reference lasts 15 seconds and uses 1280 × 720 pixels. Use those dimensions to understand the composition, then plan the actual destination. In this sequence, “select a legal action” and “animate its cost and combat result” need their own readable states. Include entrance time, a stable hold and transition time in the budget. Longer names, localized copy or a vertical version may require a different camera crop and a longer hold; shrinking every label is not a reliable adaptation.
In the Prompt
Return a timing table with scene start and end, copy, assets, motion and audio cues.
Apply It to Your Version
Test the longest approved line in the intended output size. Mark when the information is fully visible and when it leaves. If the hold is too short, revise the scene budget before adding more visual layers.
Review the Specific Failure
Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game. Check this task-specific risk before evaluating polish. Compare the render with the same approved input records and inspect the scene immediately before and after a revision. Keep the content fixed while changing one relevant parameter, so an attractive new render does not silently replace the original task with a different result.
In the Prompt
Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game.
Apply It to Your Version
Return the failed checkpoint, the corrected checkpoint and the exact change. Preserve the rest of the approved sequence and list any result that still depends on missing assets, data or product support.
Check the Sequence and Export
Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game.
- Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game.
- Read every important label at the intended playback size.
- Inspect the boundary frames for geometry, state and continuity.
- Confirm approved input data, source credits and asset permissions.
- Match export dimensions, duration and audio to the approved timeline.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Revise only the pixel card battle demo sequence. Keep approved assets and copy. Check the game rules with at least one invalid move, a blocked action and a finished turn. Do not use another game's copyrighted card art or present a staged battle as a complete playable game. Show the corrected scene and its boundary frames before rendering the full film again.