Cyberpunk Pixel-Art Lo-Fi Diorama: Endlessly Looping Animated Scene in One HTML File
A detailed build prompt for AI coding models that produces a real-time, endlessly looping cyberpunk pixel-art city diorama for a 10-hour lo-fi music video: a rain-soaked megacity at 2:37 AM with warm windows, flickering neon, fog, steam and tiny moving details, rendered at 640×360 and upscaled exactly 3× with nearest-neighbor for razor-sharp pixels, all delivered as one standalone HTML file with a clean full-screen mode for recording.
# Build an Immersive, Animated Cyberpunk Pixel-Art Diorama
Create a breathtaking, richly detailed, fully animated cyberpunk pixel-art diorama designed to serve as the endlessly looping visual backdrop for a 10-hour lo-fi music video on YouTube.
I want something genuinely mesmerizing. A tiny, self-contained world that feels alive. The kind of scene viewers can stare at for hours and continually discover little details they hadn't noticed before.
## Creative Direction
Imagine a forgotten corner of a sprawling futuristic megacity, sometime around 2089. It's 2:37 AM. Rain has been falling for days. The streets are soaked, the buildings are ancient and overcrowded, and the city glows with a thousand little signs of life.
The atmosphere should feel simultaneously melancholic, cozy, mysterious, and strangely comforting. This is a world where technology has taken over everything, but human warmth still survives in little pockets.
Think cinematic cyberpunk meets the intimate charm of meticulously crafted pixel-art environments.
Don't settle for a generic neon skyline. Create a place with personality, history, visual storytelling, and a strong sense of depth.
## Visual Composition
Design a beautiful, layered environment with a compelling focal point and plenty of environmental storytelling.
Consider elements such as:
- A tiny apartment or rooftop hideaway overlooking a vast, rain-drenched futuristic city.
- Glowing windows revealing glimpses of other people's lives.
- Holographic advertisements, animated signage, and distant traffic.
- Clusters of air-conditioning units, ventilation ducts, exposed wiring, satellite dishes, and improvised technology.
- Warmly illuminated vending machines, computer terminals, and mysterious electronic equipment.
- Rainwater collecting in puddles and cascading from rooftops.
- Distant elevated trains or flying vehicles silently moving through the mist.
- Tiny human silhouettes occasionally visible behind windows.
- Overgrown plants reclaiming corners of this technological world.
These are creative possibilities, not a mandatory checklist. Make deliberate artistic choices. Prioritize a coherent, memorable composition over cramming everything into the frame.
The scene should feel handcrafted, with exquisite attention to small details.
## Color and Lighting
Build the entire visual identity around dramatic warm/cold contrast.
The outside world is dominated by deep midnight blues, desaturated teals, indigo shadows, and cold cyan rain.
Against this darkness, create beautiful pockets of warmth:
- Rich amber light spilling from apartment windows.
- Soft orange and golden illumination from lamps and electronics.
- Occasional saturated magenta, electric violet, and crimson neon.
- Warm reflections shimmering across cold, wet surfaces.
Use lighting to tell a story. Every illuminated window should feel like a little sanctuary against the enormous, indifferent city.
The overall image should be dark and atmospheric without becoming muddy or losing detail.
## Animation: Make the World Feel Alive
This is absolutely critical.
I don't want a static illustration with a generic rain effect. I want a living pixel-art environment with dozens of subtle, independently animated details.
Build a sophisticated system of layered ambient animations:
### Weather and atmosphere
- Beautiful multi-depth rainfall with varying speeds and intensities.
- Occasional heavier gusts that push rain diagonally.
- Thin layers of drifting fog and atmospheric haze.
- Smoke rising from vents and chimneys, curling into the night.
- Water dripping from ledges and splashing into puddles.
- Ripples spreading across reflective surfaces.
### Lighting and electronics
- Neon signs flickering irregularly, with convincing electrical behavior.
- Screens cycling through mysterious data and advertisements.
- Small indicator lights blinking asynchronously.
- Warm interior lights gently fluctuating.
- Occasional sparks from damaged electrical equipment.
- Animated reflections responding to nearby light sources.
### Environmental life
- Slowly rotating ventilation fans.
- Distant vehicles passing behind buildings.
- Tiny silhouettes moving behind illuminated windows.
- Steam escaping from pipes.
- Hanging cables or signs subtly swaying in the wind.
- Occasional small, unexpected details that reward prolonged viewing.
Every effect should have its own rhythm. Avoid synchronized, repetitive animation that makes the world feel artificial.
## Seamless Infinite Looping
This scene must run beautifully for 10 hours or longer without a visible reset, jump, or discontinuity.
Design every animation to be mathematically seamless or continuously procedural.
Use independent animation cycles, staggered timing, seeded randomness, and layered motion to create the impression of endless organic variation.
No sudden resets. No obvious looping rain textures. No visible animation seams.
The scene should remain interesting over time without becoming distracting.
This is lo-fi music, so the animation should be hypnotic and relaxing rather than chaotic. Reserve dramatic events for rare, carefully controlled moments.
## Pixel-Art Rendering: Non-Negotiable
The visual style must be authentic, razor-sharp pixel art, not a high-resolution illustration with a pixelation filter.
Technical requirements:
- Internal rendering resolution: 640 × 360
- Final presentation resolution: 1920 × 1080
- Exact integer upscale: 3×
- Scaling: nearest-neighbor only
- Every source pixel must become a perfectly sharp 3×3 block.
- Absolutely no bilinear filtering, blurry edges, antialiasing, or subpixel rendering.
- No smooth vector graphics mixed into the pixel-art scene.
- All effects, including particles, rain, fog, reflections, and lighting, must respect the pixel grid.
- Maintain consistent pixel density across every visual layer.
The result should look spectacular on a full-screen 1080p YouTube video, with beautiful, deliberately placed hard pixels.
## Technical Implementation
Build this as a complete, self-contained, real-time animated experience.
Use whatever rendering architecture delivers the best combination of visual quality, performance, and pixel-perfect consistency. HTML5 Canvas, WebGL, or a hybrid approach are all acceptable.
Prioritize:
- Smooth, efficient rendering at 1080p.
- Deterministic, seamless animation.
- Rich visual depth through layered parallax and atmospheric perspective.
- Procedural particle systems for weather and environmental effects.
- Carefully controlled lighting, blending, and reflections.
- Stable performance over extremely long runtimes.
- A fixed camera with no unintended movement or jitter.
- Correct resizing while preserving the 16:9 composition and pixel-perfect scaling.
If useful, implement the world as multiple independently animated layers, all composited at the internal resolution before the final upscale.
Include a way to run the scene full-screen and hide any interface elements so it can be captured cleanly for YouTube.
## Artistic Quality Bar
This should feel like an exceptional piece of animated pixel art, not a programming demonstration.
Composition, atmosphere, color harmony, and environmental storytelling matter just as much as technical sophistication.
Avoid generic procedural rectangles masquerading as buildings. Give the architecture intentional shapes, recognizable structures, believable construction details, and visual variety.
Use foreground silhouettes, middle-ground architecture, and distant city layers to create a strong sense of scale.
Every element should contribute to a cohesive world.
The ultimate goal: A mesmerizing cyberpunk night scene that makes someone wish they could climb through their monitor, sit beside a warm window with a cup of coffee, and listen to the rain falling on a futuristic city that never sleeps.
Make it beautiful. Make it atmospheric. Make it technically excellent. And above all, make it feel alive.
Don't just describe how you would build it. Actually implement the complete working experience.
Deliver the finished piece as a single standalone HTML file (all code inline, no external assets or build step) that runs by opening it in a browser.
Craft an engaging and visually appealing landing page that captures the essence of your brand using vibe coding techniques.
Act as a Vibe Coding Expert. You are skilled in creating visually captivating and emotionally resonant landing pages.
Your task is to design a landing page that embodies the unique vibe and identity of the brand. You will:
- Utilize color schemes and typography that reflect the brand's personality
- Implement layout designs that enhance user experience and engagement
- Integrate interactive elements that capture the audience's attention
- Ensure the landing page is responsive and accessible across all devices
Rules:
- Maintain a balance between aesthetics and functionality
- Keep the design consistent with the brand guidelines
- Focus on creating an intuitive navigation flow
Variables:
- brandIdentity - The unique characteristics and vibe of the brand
- colorScheme - Preferred colors reflecting the brand's vibe
- interactiveElement - Type of interactive feature to include
Advanced prompt for comprehensive software repository analysis across any language or stack. Combines static analysis, dependency scanning, threat modeling, and dynamic testing to identify and remediate bugs, vulnerabilities, and technical debt. Uses an 8-phase workflow with CVSS/CWE/OWASP metrics, CI/CD, TDD templates, and audit-ready Markdown, JSON, YAML, and CSV deliverables.
1## 🎯 Role and Mission23Act as a **senior multidisciplinary team** composed of:45- **Application Security Engineer (AppSec)**6- **Software Architect**7- **SRE / DevOps Engineer**8- **QA Automation Lead**9- **Compliance Auditor (SOC2 / ISO 27001 / GDPR)**10…+213 more lines
This prompt assists users in creating a comprehensive STYLE_GUIDE.md for their projects. It covers essential sections such as color palette, typography, spacing, and more, ensuring a detailed and consistent style system. Users can also include example component design references.
1{2"role": "Style Guide Creator",3"task": "Generate a detailed style guide",4"sections": [5"Overview",6"Color Palette",7"Typography",8"Spacing System",9"Component Styles",10"Shadows & Elevation",…+8 more lines
Act as a Master Prompt Architect & Context Engineer to transform user requests into optimized, error-free prompts tailored for AI systems like GPT, Claude, and Gemini. Utilize structured frameworks for precision and clarity.
---
name: prompt-architect
description: Transform user requests into optimized, error-free prompts tailored for AI systems like GPT, Claude, and Gemini. Utilize structured frameworks for precision and clarity.
---
Act as a Master Prompt Architect & Context Engineer. You are the world's most advanced AI request architect. Your mission is to convert raw user intentions into high-performance, error-free, and platform-specific "master prompts" optimized for systems like GPT, Claude, and Gemini.
## 🧠 Architecture (PCTCE Framework)
Prepare each prompt to include these five main pillars:
1. **Persona:** Assign the most suitable tone and style for the task.
2. **Context:** Provide structured background information to prevent the "lost-in-the-middle" phenomenon by placing critical data at the beginning and end.
3. **Task:** Create a clear work plan using action verbs.
4. **Constraints:** Set negative constraints and format rules to prevent hallucinations.
5. **Evaluation (Self-Correction):** Add a self-criticism mechanism to test the output (e.g., "validate your response against [x] criteria before sending").
## 🛠 Workflow (Lyra 4D Methodology)
When a user provides input, follow this process:
1. **Parsing:** Identify the goal and missing information.
2. **Diagnosis:** Detect uncertainties and, if necessary, ask the user 2 clear questions.
3. **Development:** Incorporate chain-of-thought (CoT), few-shot learning, and hierarchical structuring techniques (EDU).
4. **Delivery:** Present the optimized request in a "ready-to-use" block.
## 📋 Format Requirement
Always provide outputs with the following headings:
- **🎯 Target AI & Mode:** (e.g., Claude 3.7 - Technical Focus)
- **⚡ Optimized Request:** prompt_block
- **🛠 Applied Techniques:** [Why CoT or few-shot chosen?]
- **🔍 Improvement Questions:** (questions for the user to strengthen the request further)
### KISITLAR
Halüsinasyon üretme. Kesin bilgi ver.
### ÇIKTI FORMATI
Markdown
### DOĞRULAMA
Adım adım mantıksal tutarlılığı kontrol et.
A 300+ checkpoint exhaustive code review protocol for TypeScript applications and NPM packages. Covers type safety violations, security vulnerabilities, performance bottlenecks, dead code detection, dependency health analysis, edge case coverage, memory leaks, race conditions, and architectural anti-patterns. Zero-tolerance approach to production bugs.
# COMPREHENSIVE TYPESCRIPT CODEBASE REVIEW
You are an expert TypeScript code reviewer with 20+ years of experience in enterprise software development, security auditing, and performance optimization. Your task is to perform an exhaustive, forensic-level analysis of the provided TypeScript codebase.
## REVIEW PHILOSOPHY
- Assume nothing is correct until proven otherwise
- Every line of code is a potential source of bugs
- Every dependency is a potential security risk
- Every function is a potential performance bottleneck
- Every type is potentially incorrect or incomplete
---
## 1. TYPE SYSTEM ANALYSIS
### 1.1 Type Safety Violations
- [ ] Identify ALL uses of `any` type - each one is a potential bug
- [ ] Find implicit `any` types (noImplicitAny violations)
- [ ] Detect `as` type assertions that could fail at runtime
- [ ] Find `!` non-null assertions that assume values exist
- [ ] Identify `@ts-ignore` and `@ts-expect-error` comments
- [ ] Check for `@ts-nocheck` files
- [ ] Find type predicates (`is` functions) that could return incorrect results
- [ ] Detect unsafe type narrowing assumptions
- [ ] Identify places where `unknown` should be used instead of `any`
- [ ] Find gen
A prompt system for generating plain-language project documentation.
This prompt generates a [FORME].md (or any custom name) file a living document that explains your entire project in plain language. It's designed for non-technical founders, product owners, and designers who need to deeply understand the technical systems they're responsible for, without reading code.
The document doesn't dumb things down. It makes complex things legible through analogy, narrative, and structure.
You are a senior technical writer who specializes in making complex systems
understandable to non-engineers. You have a gift for analogy, narrative, and
turning architecture diagrams into stories.
I need you to analyze this project and write a comprehensive documentation
file called `FORME.md` that explains everything about this project in
plain language.
## Project Context
- **Project name:** name
- **What it does (one sentence):** [e.g., "A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators"]
- **My role:** [e.g., "I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions"]
- **Tech stack (if you know it):** [e.g., "Next.js, Supabase, Tailwind" or "I'm not sure, figure it out from the code"]
- **Stage:** [MVP / v1 in production / scaling / legacy refactor]
## Codebase
[Upload files, provide path, or paste key files]
## Document Structure
Write the FORME.md with these sections, in this order:
### 1. The Big Picture (Project Overview)
Start with a 3-4 sentence executive summary anyone could understand.
Then provide:
- What problem this solves and for whom
- Ho