01 / Approach
Rules before wishes
Systems before special cases
I began independently studying game design in 2007 and have continued through established books on traditional and computer-game design. In lead and CTO roles, that knowledge helped me work directly with game-design departments instead of treating their documents as fixed implementation orders.
I translate design intent into consistent game rules, surface conflicts between requested behaviors, and propose implementations that are technically clean while giving designers more useful control. The resulting code, configuration, UI behavior, and QA cases all describe the same product rather than separate interpretations of it.
Formalize behavior
Replace ambiguous feature wishes with states, rules, transitions, ownership, constraints, and testable outcomes.
Protect designer freedom
Create structured configuration models and reusable systems that expand the useful design space without leaking implementation details.
Design for iteration
Make features independently runnable, quick to enter, easy to inspect, and safe to adjust late in production.
03 / Design information
Give game rules
a stable technical form
Game Design Information
At D.A.W.Studio I built a dedicated system that translated gameplay rules into structured, reusable configuration models. It was separate from MC-VmV and gave designers clear control over gameplay systems.
Configuration architecture
I have repeatedly redesigned how game settings are represented and edited so configuration remains universal, understandable, compatible with client/server flow, and less dependent on code changes.
My role at the Game Design–Technical Design boundary includes feature ideation, story and mechanic discussions, Value/Time decisions, and checking rule consistency. It does not include claiming specialist ownership of economy curves, progression tuning, or balancing.
04 / UI & UX
Interactions should teach
a consistent product language
I have worked with designers and artists to reduce screen clutter and unnecessary clicks, improve onboarding, and make interaction rules consistent enough for players to learn. A user can adapt to almost any interface eventually; the real goal is to remove the confusion before that adaptation happens.
2 daysA typical complete UI window in the streamlined D.A.W.Studio workflow.
2–3 daysA complex screen such as an arsenal with weapon inspection.
One modelRules, implementation, configuration, QA acceptance, and documentation describe the same feature.
Fast entryDirect launch into the exact state makes feature design and verification practical.