← Back to Cyra
AgentCyra

Skill · Version 1.0.0

PlayCanvas input, camera and UI

Coordinates camera control, object picking and interface input within an embedded game. It handles canvas coordinates, focus loss and readable UI independently of the internal rendering resolution.

playcanvas-input-camera-ui

See how it helps

When is it useful?

Use when resizing or UI overlays make world selection unreliable.

What does it help you do?

  • Maps devices to actions and canvas-relative positions.
  • Handles pointer capture, focus loss and interface input ownership.
  • Separates UI readability from internal rendering resolution.

Try asking this

Embed our 3D room-design game beside a product panel. Drag furniture with the camera zoomed, open the panel and switch tabs while holding a key. Selection must stay under the pointer, panel clicks must not move furniture and movement must stop on focus loss.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

PlayCanvas — input camera ui

Use when implementing PlayCanvas camera motion, picking, touch, UI or controller intent.

Version and project gate

Inspect Engine version, Engine-only versus hosted Editor workflow, ESM versus classic scripts, build/export process, asset IDs and tags, render backend, script attributes and target browser requirements. Do not assume a paid Editor service is required for Engine-only work. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.

Work

Map input devices to game actions and coordinate spaces. Define pointer capture, focus loss and UI capture. Use canvas-relative picking and align camera/physics ownership. Keep screen-space UI readability separate from internal render resolution.

Deliver

A usable input/camera/UI slice with documented capture and resize behavior. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

A fullscreen canvas assumption breaks when embedded; touch gestures can conflict with page scrolling.

Acceptance scenario

Resize the host, rotate a mobile viewport, lose focus during movement and tap UI over a pickable world object. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.

Scope and sources

This skill belongs to Cyra. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.

Included files 1

  • SKILL.md