From workflows
to worlds.

What I built

• A table-anchored workspace with animated paper-boat instructions and hand-joint recording and replay.
• Interactive teaching models for engines, turbines, gears, brakes, pumps, cams, belts, and crank mechanisms.
• Lesson authoring with written steps, video timestamps, fingertip-placed arrows, and importable lesson files.
• Voice commands, offline narration, and an experimental iPhone-to-Apple Watch haptic relay.

The idea behind it

Watching someone do a task is different from understanding where your own hands should go. GhostHands explores that gap by putting the demonstration where the work happens.

My contribution

Built with Ethan Holm at SASEHacks. My work centered on the native spatial workspace, interaction, learning tools, mechanical labs, and companion-device experiments.

What I built

• A themed three-dimensional CRT menu and equipment console, designed for mixed reality.
• Physical, look-and-pinch, and hybrid controls with adjustable interaction settings.
• Placement and seated/reclined calibration, spatial audio, and revised pause and return flows.
• Iterations on the lift, crank, keyboard interactions, cables, collision, lighting, and lifecycle recovery.

The idea behind it

A port becomes interesting when the original interaction is rethought for the device. Here, the challenge was making machinery feel usable with bare hands while preserving the game's atmosphere.

My contribution

Native adaptation, spatial interface, control design, and integration work. Original Crank It! by James Dornan and Mike Klubnika; original game content retains its creators’ authorship.

What I built

• An operations overview connecting the client pipeline, daily priorities, and financial reporting.
• Connections for supported email, calendar, billing, hosting, and AI services.
• A contextual copilot with review and confirmation around sensitive actions.
• A separate public demo using synthetic business records, plus a guided installation path.

The idea behind it

Running a small business often means constantly switching between disconnected tools. The console gives the operator one place to regain context and decide what needs attention.

My contribution

Product design, application development, integrations, public demo, and the installation experience.

What I built

• A web study workspace and a native Vision Pro prototype with connected, movable source panes.
• Code imports, dependency tracing, expandable readers, and grounded explanations.
• Surround layouts, panel grips, resizing, and experiments with room-aware placement.
• Learning flows for exploring, tracing, comparing, explaining, and pinning evidence.

The idea behind it

Some ideas are easier to understand when their relationships stay visible. POLY asks what learning looks like when the room becomes the workspace.

My contribution

Technical prototype and native Vision Pro development within a five-person OU project team.

What I built

• A combined native experience for workshop, passthrough, hand fitting, and HUD experiments.
• Hand calibration, articulated armor placement, and rigid/flexible material experiments.
• Movable spatial panels, palm-based interaction, floor placement, and spatial sound.

The idea behind it

This project is a test bed for interfaces that live around the body: what should follow your hands, what should stay in the room, and what should stay in view?

My contribution

Native application, interaction experiments, hand calibration, rendering integration, and iteration from headset feedback.

What I built

• A purpose-built maintenance application with authenticated access and role-aware views.
• Structured equipment and service records, reporting, and data-driven assistant experiments.
• A workflow shaped around actual maintenance-entry requirements rather than a generic dashboard.

The idea behind it

The useful system is the one that fits the daily user's work. This build focused on getting the maintenance workflow right before expanding the platform.

My contribution

Application design, implementation, database and authentication integration, and prototype iteration.

What I built

• A command center for units, stays, finance, settings, and automation history.
• Integration adapters for payments, smart locks, thermostats, banking, and messaging.
• Check-in/checkout logic, overlap checks, local-time scheduling, and a contextual assistant.

The idea behind it

A rental workflow crosses both software and the physical world. The interesting engineering is making those transitions explicit, recoverable, and visible.

My contribution

Application, interaction design, automation engine, integration architecture, and reliability work.

What I built

• An order-to-fulfillment workflow linking WooCommerce orders with UPS shipping.
• Automation around the repeated steps of preparing and processing outgoing orders.
• A companion order-management interface with an open-order queue, shipment tracking, and links to customer organizations.

The idea behind it

Re-entering the same information across systems creates work without adding value. This project connected the tools around the actual fulfillment process.

My contribution

Shipping-service integration and operational workflow implementation, plus order-management interface development.

What I built

• Firmware and interface work around an Arduino Opta-based controller.
• A fleet dashboard for telemetry, cycle history, device configuration, and diagnostic views.
• Customer-portal and assistant experiments grounded in device records and manuals.

The idea behind it

Useful device software connects three perspectives: the controller's state, the service team's diagnosis, and the operator's next action.

My contribution

Firmware port, dashboard and portal development, and device-to-cloud integration experiments.

What I built

• A TypeScript engine for amortization, cash-flow projections, coverage ratios, and stress scenarios.
• A workspace for inspecting a deal and its assumptions.
• Narrative generation grounded in computed results, with a deterministic fallback.

The idea behind it

An explanation is more useful when the numbers can be traced back to explicit calculations. The prototype separates calculation from prose generation.

My contribution

Financial-engine prototype, interface, and narrative integration.

What I built

• An on-device progressive web app with runner timing and roster tools.
• Shareable roster links and files, plus printable PDF results.
• A compact, precision-instrument interface with stable, readable time displays.

The idea behind it

A tool used beside a race should work where the race happens, even without a reliable connection.

My contribution

Product design, offline application, roster sharing, and PDF generation.

What I built

• A Web Audio synthesis engine with multiple engine presets and per-cylinder firing behavior.
• GPS-driven input experiments, audio limiting, and a responsive visual HUD.
• A self-contained application with an offline render harness for checking audio behavior.

The idea behind it

Sound design becomes a systems problem when the sound has to respond continuously to changing input.

My contribution

Application design, audio synthesis, browser interface, and signal-validation tooling.

What I built

• Hand-only locomotion, aiming, jumping, and a physical axe interaction mode.
• Immersive rendering, positional audio, campaign saves, and a three-dimensional map viewer.
• Room Hunt experiments using scanned spaces for encounters and pickups.

The idea behind it

The port explores how established game mechanics translate to hands, head movement, and the room around the player.

My contribution

Native adaptation, hand controls, spatial menus, room-play experiments, and testing. Original engine and LibreQuake content retain their upstream authorship.

What I built

• A minimal icon-based launch interface for integrated experiences.
• Lifecycle integration across different native and game-engine components.
• Shared attention to exit gestures, resource boundaries, saves, and return-to-menu behavior.

The idea behind it

Integration is its own piece of engineering: several experiences need to coexist without leaving stale scenes, windows, audio, or input behind.

My contribution

Host application and integration work across the spatial project collection.

What I built

• Native immersive rendering and a spatial menu.
• Reclined calibration, gaze-and-pinch confirmation, and revised gameplay controls.
• Work on startup, scene loading, original-content integration, and menu lifecycle.

The idea behind it

When the expected posture changes, the interface has to change with it. This project explores interaction and orientation from a bed or reclined position.

My contribution

Native port and interface adaptation. The original game's story, scenes, and creative assets are not my original work.

What I built

• A native Godot/visionOS runtime path with hand input and spatial menus.
• Locomotion, aim/fire, scope controls, pickup/drop-off, and story transitions.
• Tracking-loss input release, pause, replay, and host integration hooks.

The idea behind it

The challenge is to preserve a game's sequence and atmosphere while replacing desktop input with spatial interaction.

My contribution

Native adaptation and controls; original game by KitsuKell.

What I built

• A native GZDoom-to-visionOS runtime with stereo rendering and original audio integration.
• Hand-driven combat, locomotion, inventory, crafting, journal, and save/load work.
• A spatial map-case console and recovery paths for interrupted or failed sessions.

The idea behind it

Getting a world to render is only the start. The project focused on preserving the supporting systems that make a long-form game playable.

My contribution

Runtime port, spatial interface, control mapping, and targeted local verification. Original game, engine, and assets retain their upstream authorship.

What I built

• Vision Pro integration experiments for an existing Godot game codebase.
• Spatial menu and presentation work within the wider Development project.

The idea behind it

A tabletop game provides a concrete setting for testing where a spatial interface should sit and how a player should interact with it.

My contribution

Port and interface experimentation. Based on OpenBuckshotRoulette by 1503Dev; original Buckshot Roulette by Mike Klubnika.

What I built

• A structured world specification and native RealityKit scene architecture.
• Procedural pipelines for vegetation, environments, creatures, and ambient sound.
• Behavior models and validation tooling to keep generated content within explicit contracts.

The idea behind it

Generated worlds need more than a compelling prompt. The project explores the structure, asset pipeline, and behavior rules that make a requested environment coherent.

My contribution

Application architecture, procedural asset tooling, and world-generation experiments.

What I built

• A campus world with mapped exterior buildings and enterable landmark interiors.
• Story and encounter flows, inventory and weapons, voiced scenes, and adjustable audio.
• Save/checkpoint behavior, map navigation, difficulty settings, and a packaged desktop build.

The idea behind it

This project combines world-building with the practical systems behind a playable game: progression, readable objectives, recoverable sessions, and a coherent sense of place.

My contribution

Game implementation, campus-world assembly, interface, and iterative playability work.

What I built

• A responsive single-page website with an automotive visual identity.
• Service sections, a gallery, location information, and a quote-composer flow.
• Keyboard, mobile, security-header, and interaction refinements.

The idea behind it

The design aims to let the craftsmanship carry the page, with the interface giving the work room to speak.

My contribution

Website design and implementation as a prospect concept.

What I built

• A monochrome visual system with architectural typography, restrained motion, and responsive layouts.
• Service and product pages, contact flows, and a dedicated portfolio.
• Performance-minded static pages and consistent navigation across the personal site.

The idea behind it

A business website should make the work understandable and make the next step obvious.

My contribution

Design, development, content, and ongoing iteration.

What I built

• Email-watch and action-item tooling.
• Context-aware drafting and follow-up workflows.
• Integration experiments connecting the inbox with an operations workspace.

The idea behind it

The value of an agent is often in remembering the small things reliably, then giving the operator enough context to make the decision.

My contribution

Workflow design, integrations, and internal tooling.

What I built

• Static-site and full-stack application starters with shared design and security conventions.
• Onboarding forms, client setup guides, invoice tooling, and reusable delivery workflows.
• Project checks and integration patterns that reduce repeated setup work.

The idea behind it

Good foundations let the next project spend more time on the client's actual problem.

My contribution

Tooling, templates, workflow design, and ongoing refinement.