🦉Sherlock Bones — Educational Dissection Game

The problem

The team needed gameplay systems and content tooling that let designers quickly prototype new skeletons and puzzles without touching code, while keeping the experience polished and kid-friendly.

The approach

Within the Unity/C# codebase I focused on systems that took the friction out of content creation — data-driven puzzle definitions, reusable gameplay components, and the small UX details that made interactions feel right on a tablet. Working alongside designers and artists made tight iteration loops a priority.

Implementation highlights

• Gameplay components that designers configured via inspector data instead of code.
• Polished touch-input handling tuned for younger players.
• Cross-functional collaboration with designers, artists, and audio.

Outcome & lessons

Sherlock Bones shipped on the App Store and is still live. Beyond the credit, this was where I learned how content-driven design and engineer/designer collaboration really work in production game development.