House Dice #

Two-player, streak-style dice game for atproto. Your daily roll -- data lives in your own PDS repo, not on any server House Dice controls.

What this actually is #

A frontend-only, static site. No backend, no database of its own -- every roll, streak, and setting is a real record written directly to the acting player's own atproto repo, read back the same way. Bundled with esbuild (ESM + code-splitting), served as plain static files, and authenticated via real atproto OAuth (Bluesky login), not a custom account system.

The games #

One shared lobby, several rooms, each its own self-contained dice mechanic with its own atproto collection:

• Seven-Up -- roll until you hit a 7, share your streak
• High Roller -- five rolls of five dice, best total wins
• Going To Town, Pig, Ship Captain Crew -- classic dice variants, each with their own room
• Prism, Contagion -- Dice Lab experiments
• Cosmic Junkyard -- its own scoring mechanic, shareable results
• Parlor, Lounge -- social/discovery spaces, not games themselves
• Sprite Hop -- a separate mini-game living inside House Dice, with its own mushroom economy, tunnel sequence, and kitchen/office rooms. See sprite-hop-reference.md for everything about this one specifically -- it's substantial enough to have its own dedicated doc.

Related, but genuinely separate project: dicesprite-agent #

A standalone atproto bot account (dicesprite.bsky.social), its own repo, its own small Node.js process -- not part of this static site at all. Built to eventually run bot-driven game mechanics (a daily guessing game, to start) that interact with players' own atproto records the same way this app does. Lives entirely on its own; nothing in dicestreak-atproto-alpha depends on it existing or running.

Where to actually find things #

This README is deliberately just a map, not the territory -- the real depth lives in four dedicated docs, each scoped to a different concern:

• house-dice-process-notes.md -- how development on this project actually works session to session (file delivery conventions, the discuss-then-build rhythm, documentation hygiene). Start here if you're picking this project up fresh.
• house-dice-build-config.md -- the real, current build/deploy setup: dependencies, the actual build command, environment-specific gotchas (PowerShell vs. bash, Tangled/SSH setup, npm quirks).
• sprite-hop-reference.md -- Sprite Hop's own mechanic design in full (part 1, authoritative current state) plus a speculative idea backlog (part 2, not required reading).
• threejs-tunnel-design-evaluation-status.md -- the tunnel sequence's own design reasoning and prototype history specifically.

Source of truth #

The developer's own local project folder, plus what's actually pushed to this repo on Tangled, is the real, current state of this project -- not any snapshot living in a Claude Project's knowledge panel, which is a manually-maintained mirror and can drift out of date.