Prompt Library
100 real prompts from the VNG world registry.
Each prompt is generated from a live reference world with its own visual language, typography, palette rules, modules, interactions, and quality bar.
100 prompts100 world linksProtected copy APIHourly limits
001 / Nostalgia / Game
Retro Arcade
Pixel/terminal mono display + readable mono labels + compact sans body
Pixel art, 8-bit buttons, neon scoreboards, and playful skill tokens.
Build VritantaNextGen world 001: Retro Arcade. 1. Product Goal: Create a client-ready portfolio sub-site that feels like a complete design world, not a template. The page must sell this concept: Pixel art, 8-bit buttons, neon scoreboards, and playful skill tokens. Audience / commercial fit: This world is designed for nostalgia / game work and should feel like a complete product experience, not a decorative theme. 2. Story And Emotional Arc: Play is memory made interactive. Philosophy: Play is memory made interactive. 3. Visual Direction / Nature: Dark arcade room, chunky pixel borders, CRT glow, electric score panels. Visual language: Dark arcade room, chunky pixel borders, CRT glow, electric score panels. Hero image brief: Create a premium hero image for Retro Arcade: Dark arcade room, chunky pixel borders, CRT glow, electric score panels.. Use real or generated imagery that matches the world. Do not use placeholder boxes, random stock images, or abstract blobs as the main visual. 4. Typography System: Pairing: Pixel/terminal mono display + readable mono labels + compact sans body Font guidance: Display: Press Start 2P or VT323 for arcade routes; IBM Plex Mono or JetBrains Mono for technical labels; Inter for body copy. Scale: Hero 72-104px, section headings 36-48px, labels 11-12px uppercase with wide tracking, body 16-18px with 1.7 line-height. Rules: Use monospaced typography for headings and labels; keep body copy highly readable and avoid decorative script. Use typography as a major part of the design identity. Headings must feel authored, labels must feel intentional, body copy must remain easy to read. 5. Color System: Base/background: #07030B Primary accent: #EC4899 Secondary/support: #46F0FF Surface/detail: #FBBF24 Use the palette with restraint. One dominant background, one clear accent, one secondary highlight, and one surface/detail color. Maintain WCAG-readable contrast. 6. Layout Requirements: First viewport must contain: world eyebrow/id, large world title, client value statement, primary CTA, secondary index link, tech chips, and a strong hero visual. Below the fold include: client story, art direction, visible production prompt drawer, palette swatches, typography panel, 3 story cards, psychology, signature modules, and client proof. Use responsive desktop and mobile spacing. No overlapping text. No clipped buttons. No unreadable tiny paragraphs. 7. Required Features / Modules: - Collect portfolio tokens: build this as a visible, believable interaction module. - Scoreboard skill reveals: build this as a visible, believable interaction module. 8. Interactions: Collect portfolio tokens, Scoreboard skill reveals Every interaction should have a visible state: hover, selected, expanded, active, copied, or revealed. 9. Tech Focus: Canvas, CSS sprites, Keyboard UI Use implementation choices that support the concept; do not add a library unless it clearly improves the world. 10. CTA: Explore this world 11. Quality Rules: Make it feel like a senior designer and senior frontend engineer collaborated on it. Avoid generic purple gradients, beige template design, lorem ipsum, random unreadable text inside images, copied brand logos, weak shadows, unbalanced spacing, and decorative elements that do not support the world. Use exact content, clear hierarchy, and polished responsive behavior.