Quest Flow
Quest givers, triggers, gates, markers, and progression rules.
Additional portfolio context
Extra systems, workflow, and technical notes.
This page is for the deeper material that does not need to crowd the main portfolio: design preferences, workflow habits, technical focus, and the kind of systems work I like doing.
Technical focus
Systems I like building.
I like the backend side of gameplay: rules, state, content flow, and tools that make a project easier to reason about.
Data Assets
Designer-editable content that reduces one-off code changes.
Runtime State
Save/load and restoration paths that keep player progress reliable.
Tools
Small utilities and UI that remove repeated friction from workflows.
Workflow
How I approach build work.
I usually start by making the system understandable, then make it configurable, then make it hard to misuse.
Document the flow
Expose useful controls
Prefer reusable pieces
Test the real workflow
Make state visible
Keep designers moving
Reduce repeated setup
Build for debugging
Contact
Want the practical version?
The main portfolio has the project cards. This page is the extra context for how I think about systems, tooling, and team support.