g2-events-input

Route G2 device input events and audio PCM streams via the Even Hub SDK.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill g2-events-input
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: g2-events-input
Source: https://github.com/kyle-deprow/ai_scaffolding/tree/main/skills/g2-events-input
Command: npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill g2-events-input

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handling G2 AR input involves capturing and routing events from the R1 ring and temple gestures, synchronizing audio input, and maintaining reliable lifecycle awareness for interactive experiences.

Core Features & Use Cases

  • Event listening via onEvenHubEvent and OsEventTypeList to drive UI and hardware interactions.
  • Accurate event routing with isEventCapture-based containment for list, text, and system events, plus baseline support for simulator quirks.
  • Audio PCM capture management, including microphone opening/closing and foreground/background lifecycle handling.
  • Debugging and validation workflows for event routing, boundary events, and device status callbacks.

Quick Start

Register a bridge listener for onEvenHubEvent and begin handling input events, audio frames, and device status callbacks immediately after startup.

Frequently Asked Questions about g2-events-input

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture and route AR input events from G2 devices using the Event Hub SDK?

To capture AR input events from G2 devices, subscribe to the bridge.onEvenHubEvent listener and use OsEventTypeList values to filter and route R1 ring and temple gestures to drive interactive UI and hardware experiences.

Does onEvenHubEvent support audio PCM stream capture and microphone lifecycle management?

Audio PCM stream capture is fully supported through onEvenHubEvent, allowing you to manage microphone opening and closing operations while maintaining reliable audio frame synchronization during foreground and background lifecycle states.

How do I handle event capture boundaries for list and text events in G2 AR applications?

Event capture boundaries for list and text events are handled using isEventCapture-based containment logic, which accurately routes system events while accounting for known simulator quirks during debugging and validation workflows.

What is the best way to manage foreground and background lifecycle states during G2 AR event routing?

Managing foreground and background lifecycle states during G2 AR event routing requires subscribing to device status callbacks via onEvenHubEvent and applying appropriate event throttling to maintain reliable input handling across state transitions.

Why does my G2 AR input event routing fail to trigger UI interactions on the simulator?

G2 AR input event routing fails on the simulator due to known simulator quirks affecting isEventCapture-based containment, requiring specific baseline support adjustments to correctly process list, text, and system events.

Can I use the Event Hub SDK to throttle excessive AR input events from R1 ring gestures?

Throttling excessive AR input events from R1 ring gestures is supported by the Event Hub SDK, allowing you to apply rate limiting within your onEvenHubEvent subscription to prevent input flooding during interactive experiences.