About Me
I tend to work across UX, writing, art, code, and music.nu-Eden: Sundered Skies is the first project where those things stopped feeling like separate interests and started feeling like one body of work.
I did not come into games from a traditional game-dev path. I came in through web work, interface design, documentation, and a lot of self-directed creative work. That probably explains why I care as much about readability, structure, and tone as I do about mechanics.
nu-Eden: Sundered Skies started from a much larger and messier worldbuilding impulse, but the part that kept surviving revision was the design question underneath it: how to make movement expressive, interfaces readable, and systems thematically coherent without losing practical clarity.
the version of the project on this site is much less about presenting a giant archive and much more about showing how I think through player experience, system communication, visual language, and scope.
This page is the personal context behind that work. The rest of the site goes deeper into the project itself.
You can see the game prototype on thePrototype page, the design documentation on theGDD page, and a more detailed write-up in thePitch Essays.
I am most drawn to projects where system design and interface design have to solve the same problem together. That is a big part of why games appeal to me so much.
With nu-Eden, that usually comes down to a few recurring standards: movement should feel expressive, choices should create actual tradeoffs, dense systems should stay legible, and repetition should earn its place.
I also care a lot about coherence between mechanics and theme, but I try to keep that grounded. I am not interested in metaphor for its own sake. I want the way something plays to say something useful about the character, the world, or the system behind it.
In practice, that means being willing to cut or reframe ideas that add noise, flatten expression, or make the project harder to understand. On a first serious game project, that matters as much as ambition does.
Prototype & Site: The current build is a browser-based prototype and documentation system built with JavaScript, TypeScript, Next.js, and markdown. That choice is partly technical and partly practical: it matches my background, and it makes the work easy to review.
Design & Visual Work: I use Figma and Affinity Designer for interface structure, asset preparation, and visual language. A lot of that work is really information design: deciding what should stand out, what should stay in the background, and what players are expected to remember.
Writing & Documentation: Pitch essays, design notes, and markdown documents do a lot of the heavy lifting. They are not side material for me. They are part of how I clarify scope, test ideas, and communicate intent.
Working Constraints: Much of this project has been built on modest hardware and a lightweight workflow, including campus machines and phone-based notes. That pushed me toward tools and processes that favor portability, iteration, and documentation over heavy setup, which has honestly been healthy for the project.