gemini-nexus is a conversational AI chatbot product. The product intent, taken directly from the authoritative requirement thread, is to build a chatting AI chatbot with a modern look — a chat experience where a person types messages to an AI assistant and reads its replies, presented in a contemporary, motion-first interface rather than a conventional form-like chat template.
The audience is a broad consumer/prosumer audience: people who want intelligence on demand through natural conversation. The emotional register the product must hit is futuristic curiosity — talking to something that feels alive and advanced.
The product name gemini-nexus was chosen by the user and is the canonical product name.
gemini-nexus is delivered as a first-party custom web application with two pages:
Both pages are application-owned and require no account or sign-in. The Chat User can open the product and begin conversing immediately; there is no identity establishment, invitation, or provisioning step in the current scope.
The product requires backend integration: submitted chat messages must be answered by AI response generation. The AI response generation capability is a required inference — it is the indispensable mechanism that makes the accepted chat journey executable. It does not introduce a separate user-invoked goal.
The interface is the product's imagery. There is no stock photography, no flat illustration, and no conventional white-card chat surface. The assistant is represented as a real-time refractive 3D orb, and the conversation is rendered as two distinct signals: assistant text streaming bare on the dark ground with a luminous cyan caret, and user messages as magenta-edged glass capsules aligned right.
Delivery ownership. gemini-nexus is a first-party custom UI application. Both the Landing and Chat surfaces are owned and rendered by the application itself. The application owns the conversation workspace, the composer, the message stream rendering, and the visual presentation of the assistant.
Access ownership. Both accepted pages are publicly reachable with no access requirement. The Chat User does not create an account, sign in, or establish an identity to use the product. There is no application-owned identity, no session-bound private state, and no permission differentiation in the current scope. Conversation state is held for the duration of the user's visit to the Chat workspace; the product does not promise durable cross-visit conversation history.
AI response ownership. AI response generation is a backend capability that the application integrates. The Chat User's interaction with it is entirely through the Chat page: they submit a message and observe the streamed reply. The backend is not a human-facing destination and does not own any user interaction.
Current boundary. Current scope is: the Landing entry surface, the Chat conversation workspace, message submission, AI response generation and streaming, and the modern cinematic visual and motion system described in the creative direction.
Future boundary. Anything not listed above — including durable conversation history across visits, user accounts, multi-conversation management, model selection by the user, and sharing — is out of current scope and is not built, not navigable, and not part of current acceptance.
FR-1 — Chat with an AI chatbot As a Chat User, I should send messages to an AI chatbot and read its replies, so that I can hold a conversation with an AI.
FR-2 — Modern chat interface As a Chat User, I should experience the chatbot through a modern-looking interface, so that the product feels like talking to something alive and advanced rather than filling in a form.
FR-3 — AI response generation As a Chat User, I should receive an AI-generated answer to each message I submit, so that the conversation actually progresses.
FR-4 — Enter the chat experience from the Landing page As a Chat User, I should be able to enter the chat experience from the Landing page, so that I can begin a conversation.
Product context. The Chat User is the primary and only active human actor in gemini-nexus. They arrive at the product wanting intelligence on demand — to ask something and get an answer — without setup, sign-in, or configuration. They may arrive cold on the Landing page or go directly to the Chat workspace. They are a broad consumer/prosumer user, not a specialist operator; they judge the product by whether the conversation feels immediate, coherent, and alive.
Primary goal. Hold a conversation with the AI chatbot: send messages, receive coherent AI responses, and continue the exchange.
Distinct accepted responsibilities.
Relevant inputs and decisions. The Chat User's inputs are their own typed messages. Their decisions are what to ask, when to submit, and whether to continue the conversation after reading a reply. They make no configuration, model-selection, or account decisions — none are in scope.
Interactions with other accepted participants. The Chat User's only counterparty is the AI assistant, which is not a human persona. The assistant's side of the exchange is expressed as observable product behaviour: the orb brightening and accelerating while generating, the reply streaming token-by-token with a luminous cyan caret, and the orb settling when the reply completes. The Chat User reads the assistant's reply and responds to it in turn.
Observable success. The Chat User submits a message and sees it recorded in the conversation as a right-aligned magenta-edged capsule; the assistant's reply streams into the conversation as bare text with a cyan caret; the orb visibly signals generation and then settles; the Chat User can immediately submit another message.
What makes this role's work different. The Chat User's work is conversational turn-taking, not task execution or administration. There is no data to manage, no configuration to set, and no state to own beyond the live conversation. Their entire responsibility is to initiate turns and read responses — which is why the product's visual and motion system carries the assistant's presence rather than any control surface.
The creative direction is authoritative for this section. Muse: Gleb Kuznetsov. Headline concept: a conversation inside a living data space — cinematic future tech, where the assistant is an intangible luminous intelligence and the chat stream is a data stream.
| Role | Token | Value |
|---|---|---|
| Background (deep near-black navy ground) | --bg | #05060E |
| Surface (lifted panel / glass overlay) | --surface | #0E1122 |
| Text (cool white body) | --text | #EAF0FF |
| Primary (assistant glow, cyan) | --primary | #00E5FF |
| Accent (human/user signal, magenta) | --accent | #FF3DF2 |
| Muted (metadata, timestamps, steel) | --muted | #7A85A8 |
Color rules. Electric cyan (#00E5FF) is the assistant/primary glow — used for the AI orb, the streaming cursor, focus rings, and active states. Magenta (#FF3DF2) is the human/user signal and appears only in the user's own message rail, the send button, and one gradient stop of the orb. Body text is cool white (#EAF0FF); metadata and timestamps use muted steel (#7A85A8). Glows are always low-opacity (8–20%) so text contrast stays above 4.5:1 — never place body copy directly on a glow.
Full-bleed dark canvas with floating glass panels. 1px luminous borders at rgba(0,229,255,0.25). 16–24px radii on panels. Pill capsules for message bubbles and the composer. Thin concentric rings and radial tick marks around the assistant orb. Hairline circuit-like connector lines (1px, cyan at 20% opacity) linking the composer to the orb to imply a live signal path. No hard drop shadows — depth comes from glow bloom and layered translucency.
Split-stage layout: a fixed left rail (72px) holding the orb, session list, and HUD stats, and a right conversation stage occupying the remaining viewport. The orb sits top-left of the stage, half-cropped by the viewport edge. Messages flow in an asymmetric column — user messages right-aligned in a magenta-edged capsule, assistant messages left-aligned on bare dark ground with a cyan caret, no bubble. HUD strips (token count, latency, model name) run as 1px-ruled rows along the top of the stage. The Landing page uses the same grid with the orb promoted to full-bleed hero.
No stock photography, no flat illustration. The visual subject is a procedural 3D orb — a refractive, glowing volumetric sphere with an inner particle field and orbiting data rings, rendered in real time with React Three Fiber. Secondary imagery is generative: particle streams, thin luminous wireframes, topographic data lines. The interface itself is the imagery.
White or near-white chat surfaces with blue/indigo user bubbles; centred headline + subheadline + blue CTA hero composition; gradient-blob backgrounds or animated mesh gradients behind the hero; a grid of identical rounded cards with hover-lift on the landing page; Inter, Roboto, Arial, Helvetica, Poppins, or system-ui anywhere in the type stack; flat vector robot/chat illustrations or stock photography of people at laptops; bouncy spring easings, emoji-heavy UI, or playful mascot characters; placing body copy directly on top of a glow or particle field without a darkened scrim. The generic indigo/blue-on-white SaaS template is forbidden for this project.
The orb is the assistant's body, and the composer is wired to it.
The public entry is a full-viewport dark void (#05060E). A single large refractive orb — approximately 55vw, positioned right-of-centre and cropped by the top and right edges — glows cyan-to-magenta and drifts continuously. Over it, a 9-column headline in Space Grotesk 600 at ~100px sits flush-left reading "TALK TO SOMETHING THAT THINKS", with the word THINKS set in outlined cyan stroke. Type and 3D subject occupy the same space; the headline is not stacked above the orb but laid across it.
Below the headline, a single-line composer capsule — glass, 1px cyan border, placeholder "Ask anything…" — carries a magenta send node. There is no subheadline, no blue button, and no gradient blob. Top-left, a 3-line HUD block in JetBrains Mono 11px uppercase (MODEL / LATENCY / TOKENS) is separated by 1px cyan rules. Bottom-right, a scroll cue is a thin cyan vertical line that pulses downward.
The concept is implementable with accepted content and controls only: the orb, the headline, the composer capsule, the HUD block, and the scroll cue. It introduces no new behaviour, page, or destination. The composer capsule is the same entry affordance that carries the Chat User into the Chat page; the HUD block previews the same instrumentation that runs above the conversation stage; the orb is the same assistant body that appears in the Chat rail.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl
Focal subject. The real-time refractive 3D orb — a glowing volumetric sphere with an inner particle field and orbiting data rings, rendered with React Three Fiber, positioned right-of-centre at ≈55vw and cropped by the top and right edges.
Input → transformation → outcome thesis. The Chat User's attention and scroll are the input. As they scroll the Landing page, the camera performs a dolly across the orb and its particle field, scrubbing the viewpoint through the volumetric form. The outcome is that the Chat User arrives at the composer capsule having moved through the assistant's body rather than past a static image — the assistant reads as a place, not a picture. The composer capsule remains the single accepted entry control throughout.
Motion vocabulary. Cinematic and continuous. The orb slow-orbits and breathes on a 60–90s loop. Particle streams drift within and around it. Thin luminous wireframes and topographic data lines move at low opacity. Hairline circuit-like connector lines (1px, cyan at 20% opacity) imply a live signal path. Hover on any panel raises its border glow from 20% to 45% over 220ms with no lift. No b
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!