)équence de combat de boss de mécha d'anime cinématographique
De Wikiprompt, l’encyclopédie libre de prompts
)équence de combat de boss de mécha d'anime cinématographique Une invite détaillée pour générer une séquence de bataille de mechas anime cinématographique avec des designs de personnages spécifiques, des directives de style et des découpages de scènes minutés.
Médias associés
Contenu du PromptEnregistrer
🌐
Create a cinematic anime mecha boss battle sequence.
Use @ pilot for the girl inside the cockpit.
Use @ mech for the mecha bot.
Use @ dragon for the white fire-breathing dragon.
use @ mechs2 mechs2 as the storyboard dont render text or arrows.
Maintain visual continuity.
STYLE: clean cinematic anime mecha action, crisp linework, smooth cel-shading, soft faded pastel colors, muted cream whites, pale lavender armor, dusty beige smoke, warm orange fire glow, pale blue sky, thin anime line art, subtle scuffs, soft haze, gentle bloom, clean ruined city backgrounds, stylized smoke, dynamic anime camera, strong scale, high clarity.
IMPORTANT: Match the reference image style. No photorealism. No gritty dark grading. No CGI movie look. No video game cinematic look. No plastic textures. Keep the soft muted pastel fade.
CHARACTER CONTINUITY:
@ pilot is a young female anime pilot with short brown hair, gold eyes, white cockpit helmet, visor, focused expression, sweat on her face, and a clean futuristic HUD.
@ mech is a large off-white and pale lavender combat mecha with a teal visor, bulky limbs, heavy feet, battle-worn plates, vents, joints, scuffs, and clean panel lines.
@ dragon is a giant white dragon with bone-cream scales, blue-gray under-scales, beige spikes, amber eyes, sharp teeth, pink mouth, long tongue, wings, and orange fire breath.
@ pilot stays inside @ mech. Do not show @ pilot outside.
Do not change @ mech design. Do not create a second mech.
Do not add extra dragons.
TEXT RULES: no subtitles, captions, speech bubbles, comic text, logos, watermarks, or readable words. Only abstract HUD graphics allowed.
This is Part 2.
Continue directly from Part 1.
@ dragon has just recoiled from the punch.
Do not defeat @ dragon in this sequence.
0:00-0:03
Open on @ dragon rising back up from the hit with a violent roar. Low angle from behind @ mech looking up at @ dragon. Dust and broken concrete fall around them. The dragon's throat begins glowing bright orange.
0:03-0:07
Fast dynamic push-in on @ dragon's jaws as a huge fireball rapidly forms. The glow intensifies inside its throat and mouth. Heat distortion ripples through the air. Cut to dramatic side and front angles of the dragon unleashing the massive fireball down the ruined street toward @ mech.
0:07-0:10
Inside the cockpit, @ pilot reacts instantly. Warning graphics flare across the HUD. She braces and activates a defensive power. Exterior shot: @ mech plants its feet and raises both arms forward as a glowing energy shield begins forming in front of it.
0:10-0:13
The fireball crashes into the energy barrier. Huge impact. The shield bends under pressure but holds. Dynamic rotating camera around @ mech as flames, sparks, smoke, and shockwaves explode outward. The ground cracks under @ mech's feet as it pushes back against the blast.
0:13-0:15
Close alternating shots between @ pilot straining in the cockpit and @ mech holding the barrier. The shield flares brighter and finally stabilizes, fully stopping the fireball. End on a powerful wide shot of @ mech standing firm behind the glowing shield while fire rolls around it and @ dragon glares from across the ruined city.
Cut on tension.
End on a cliffhanger.
Connectez-vous pour voir le prompt complet
Continuer avec:
En vous connectant, vous acceptez nos Conditions et Confidentialité
Utilisation
Ce prompt est conçu pour être utilisé avec creative. Copiez le contenu ci-dessus et collez-le dans votre outil d’IA préféré.
Pour de meilleurs résultats, personnalisez les espaces réservés (indiqués par des crochets ou des majuscules) selon vos besoins.
Références
- Catégorie: Prompts creative
- Source: https://x.com/mdmadeit/status/2067056365517033822
Discussion
0 commentaires