Meta

The journey inside finally has a payoff. The hero copy now bows out as the camera flies through the door, leaving the screen clean for the ride — and once you’re standing in the room, new copy fades in: you’re standing inside the prototype. That’s where the honest part lives too: gamahaus is in private alpha, and right now its only users are my wife and me. A little pulsing status chip says exactly that — private alpha · 2 users — and it’ll tick up as the doors open. Build in public means the status is part of the page.

The hero leveled up. Scrolling now flies the camera through the doorway and into a furnished room — the breathing cube unfolds into floor, window, door, and bed as you go in, then folds shut on the way back out.

On top of that, a polish pass: a faint film grain across the frame, neon edges that pulse like a slow heartbeat, an idle drift that wanders instead of spinning like clockwork, and the cube now resting tilted from above. The resolution scaler also learned to recover — a momentary GPU dip no longer leaves it permanently soft.

The brand’s wireframe cube is now a live WebGL hero on the landing page itself — neon edges, bloom, follows your cursor. Built end-to-end with Claude.

Two things landed: the GamaHaus logo and a 14-section design language doc.

The logo is a wireframe isometric cube — three colored faces, magenta-front (#F507B4), cyan-right (#18D0E9), purple-top (#CB6CE6). Stroke-only, no fills. Three variants: tri-color default, mono-magenta for tight contexts, white for dark backgrounds. Reads as “3D space” without literally drawing a house — GamaHaus is the playground, not the blueprint.

The design language pins everything else: color tokens, magenta scale 50→900, Sora display + Inter body, pillowy radii, soft shadows, Phosphor icons, springy motion. Shadcn-Vue components on top of Tailwind, restyled day-one to match. Two surfaces at MVP — App (light) and Editor (always-dark, independent of theme).

Not a GamaHaus update — but this is the machine I’m building it on, so it counts. Logs aren’t always green checkmarks; sometimes they’re “spent a day digging out of my own past mistakes.”

Sat down to work at 6 AM and the laptop refused to boot to desktop. Disk at 100%, zero bytes free of 717 GB. GDM, MySQL, VirtualBox — all dead. Linux can’t start services without scratch space.

Spent a long session with Claude yesterday crystallizing the GamaHaus project bible — the design doc for the actual app this landing page exists to track.

26 sections, ~1500 lines. Tech stack (Vue 3 + Go/Fiber + PostgreSQL/Redis), modular monolith architecture, full database schema, auth, real-time, editor UX, avatar system, the GamaCoin virtual economy, license tiers, branch/template system, 5-phase dev roadmap.

Worth saying: Claude was the thinking partner here, not the typist. The bible came out of long back-and-forth conversations where we argued tradeoffs, killed weak ideas, and stress-tested decisions before they landed in the doc. AI does coding too — but using it as a brainstorming sparring partner is the part most people sleep on.

gamahaus.com is live. Hugo for the site, Cloudflare Pages for the host, GitHub for the source. Every push to main auto-deploys within a minute or two.

The log you’re reading is the whole thing. No hero section, no roadmap, no “coming soon.” Just entries, one per thing.

Registered the domain today. Starting a log here — one entry per thing made, thought, or broken. No plan, no roadmap. Just notes.