Made with Nano Banana 2 Lite · CC0 · 7 Oct 2026

Flat colour

Generated from: a scene from a small video game about: Protocol Zero — MVP scaffold of a web-based investigative strategy game: the player is a "Protocol Investigator" who investigates a simulated Web3 incident (a treasury drain), browses and filters an Evidence Room, drags evidence onto an interactive Investigation Board and connects items with relationship labels, writes a hypothesis answering what/who/how/why/what-next with a confidence slider, submits it, and gets a scored AI evaluation with feedback. Core loop: discover → investigate → connect → reason → decide → learn. Stack: Next.js, React, TypeScript, Tailwind CSS, dark "intelligence terminal" aesthetic (near-black navy, subtle grid, light-gray type, one restrained cyan accent, glowing data states — professional cybersecurity/SaaS feel, no meme or crypto-bro design). Build first: landing page (hero "PROTOCOL ZERO — THINK. INVESTIGATE. SOLVE.", three steps INVESTIGATE/CONNECT/REASON, CTA), auth (email login/signup), player dashboard (welcome, continue investigation, skill bars, recent investigations), case selection with difficulty/pseudodifficulty gating, briefing for Case 001 "The Missing Treasury", evidence room with search/filter (transactions, wallets, governance, communications, documents, protocol, timeline) and an inspect panel, investigation board (drag nodes, connect with labeled relationship lines, zoom/pan, autosave), hypothesis submission with the five text areas and confidence slider, results screen with overall score plus accuracy/evidence/reasoning/confidence/decision breakdown, strengths/missed-clues/feedback, XP + level progression, and skill scores. Implement one handcrafted, fully playable case (Case 001, difficulty 1) as a seed: briefing, ~10 evidence items with timestamps/actors/wallets, 2 red herrings, hidden truth kept server-side, deterministic scoring fallback if no LLM is wired yet (rule-based check of culprit, mechanism and key evidence mentions in the hypothesis text). Architecture must keep the hidden case truth server-only and leave room for more cases, a per-case AI evaluator, leaderboard, achievements and mobile/touch board support later., as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.