Full-stack and game engineer. Building persistent worlds and tools that make complex systems understandable.
I work across interactive 3D, real-time backends, Farcaster, and data pipelines. My focus is the complete product: how it feels, how its state behaves, and how it can be tested, operated, and improved over time.
Warpkeep is a persistent strategy world built around a real person, a permanent keep, and a place worth returning to. Gather resources, choose what to build, and turn progress into a home with its own character.
The current development direction is Warpkeep 0.4: The Verdant Citadel. It brings the gathering and building journey into a coherent, readable experience across desktop and mobile, with a lush visual identity and meaningful reasons to return. The existing alpha remains the live baseline; 0.4 is under development.
The work spans React and Three.js presentation, server-owned gameplay in SpacetimeDB, Farcaster identity, Cloudflare services, asset provenance, and release and recovery tooling.
Game and development guide · Asset archive · Water rendering (planned) · Community
| Project | Purpose |
|---|---|
| SnapMeter | A Farcaster activity dashboard with durable collection, rolling metrics, and visible data-quality states. Open dashboard |
| Clawberto Farcaster Context | Searchable daily context from Farcaster node data, with linked conversations and reusable CSV/JSON exports. Explore context |
| Degen Dogs Mission 3 | Independent community analytics on Base, with an inspectable archive and a reproducible Python and SQLite dashboard pipeline. Explore dashboard |
| Ashen Hallow | A browser fantasy autobattler with deterministic simulation, tactical deployment, and army progression across rounds. Play |
Browse the full project catalog for more tools, prototypes, research, creative work and source archives.
I build primarily with TypeScript, React, Three.js, Python, and SQL, supported by real-time databases, Cloudflare, and reproducible delivery tools.
I use AI agents for research, implementation, and review, with clear ownership and evidence for the result. Durable documentation, meaningful tests, direct inspection of the user experience, and honest release status are part of the work. A successful build is one step; a useful, dependable product is the aim.