[Placeholder] As the sole developer, I handled every aspect of Nitrojet — from core systems programming in Unity to boss AI design, level layout, UI/UX, sound design, and the full original soundtrack. This project pushed my ability to manage scope across a long development cycle while maintaining design coherence.

[Placeholder] I focused particularly on movement mechanics, ensuring the player's momentum felt satisfying at every speed. Iteration on the feel of movement drove many other design decisions downstream.

[Placeholder] Building Nitrojet as a solo project taught me how to ruthlessly cut scope without losing design vision. The biggest lesson was that the feel of a game emerges from hundreds of small decisions — none of which can be delegated. I'd approach boss design differently next time, focusing earlier on readable silhouettes and attack telegraphing.

[Placeholder] Safe Travels was driven by a deliberate aesthetic vision: the grainy, low-poly early-3D look of late-90s games. I wanted the world to feel slightly uncanny — friendly but geometrically wrong in subtle ways. Every model was constrained to a specific poly count and vertex-snapping rule.

[Placeholder] The procedural animation system was built from scratch in Godot using IK chains for limb placement. The goal was locomotion that felt organic but clearly mechanical — a little like a spider moving its legs independently over uneven terrain.

[Placeholder] One of the most unusual design choices in Safe Travels is the "car-look" mechanic — the player's vehicle turns its entire body to face points of interest rather than just a camera pivot. This creates a sense of personality and attention that makes the world feel reactive. I documented the iterations that led to the final implementation.

[Placeholder] Safe Travels was the first time I let aesthetic goals drive technical decisions rather than the other way around. Building the procedural animation system first — before any gameplay existed — forced me to understand what the game needed to feel like before knowing what it needed to do.

[Placeholder] On 27 Photos I led level design for the majority of the puzzle stages. The game is built around photographs as the primary interactive element, and I designed the spatial logic that connects visual clues to player movement.

[Placeholder] I also contributed to the design philosophy doc — defining what made a good "photo puzzle" and building a language of difficulty that could be shared with the whole team.

[Placeholder] Working on a team required me to communicate design intent much more explicitly than when working solo. Writing shared design documents and defining a "level language" that others could use pushed me to articulate instincts I'd previously left implicit.

[Placeholder] Beach Car Game is a solo project with heavy emphasis on design documentation. Every mechanic has a corresponding design rationale, and the project served as a testing ground for structured design process habits I wanted to build before tackling larger projects.

[Placeholder] Beach Car Game was where I committed to process-first development. Writing the tutorial on paper before touching Unity forced clarity about what the game actually needed to teach — and revealed several mechanics I'd planned that were redundant or confusing.

[Placeholder] Pop-Off! originated from a question: what happens when you apply the tension structure of a battle-royale to a casual party game? The concept emerged from analyzing what creates pressure in competitive games and how that pressure can be made legible to non-competitive players.

[Placeholder] I documented the genre analysis process — mapping the mechanics of both parent genres, identifying overlaps and conflicts, and finding the design space where a mashup could be coherent rather than chaotic.

[Placeholder] On Pop-Off! I contributed the core concept framing and the initial design document. I also handled [placeholder role description] during development. The game was built collaboratively with a [placeholder team size] team.

[Placeholder] The hardest part of Pop-Off! was keeping the genre mashup from becoming incoherent. Every mechanic had to earn its place by serving both the casual accessibility goal and the competitive tension goal simultaneously. Some mechanics we designed failed this test and were cut.