agentleFS
mirzaaghazadehmirzaaghazadeh/iwsdk-webxr-skills/skills/iwsdk-official/iwsdk-ray/SKILL.md

iwsdk-ray

Skill1 starsChanged 32 days agoMITView on GitHub

Verify ray clicks, UIKit selections, and DistanceGrabbable interactions with emulated XR controllers. Use for pointing, selecting, pressing spatial UI, or moving an object through a distance grab.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check XR session state and enter only when inactive.

    line 14
  2. Distinctive:

    Use an explicit select-value press/release only when the task needs to inspect the held interval.

    line 32
  3. Very specific:

    Check movementMode before deciding whether the object should remain remote or move toward the hand.

    line 45
  4. Very specific:

    When the request names an artifact path, save it directly with npx @iwsdk/cli browser screenshot --output-file <path>.

    line 63
  5. Distinctive:

    Stop when the real input and resulting named state are proven, leaving all buttons released.

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IWSDK Ray Interaction

Choose one interaction branch from measured target components. Ray clicks and distance grabs share aiming but not input duration or movement behavior.

Locate and aim once

  1. Check XR session state and enter only when inactive.
  2. Find the named entity or runtime-named UIKit control, then query its components and transform. For UIKit, prefer the live name assigned through requireElementById; use a project test hook only when no addressable runtime target exists.
  3. Aim the requested controller with xr look-at. Do not translate the controller toward a ray target.

Select exactly one branch

Click or UIKit button

For RayInteractable, Pressed, or a UIKit control, use one normal select:

npx @iwsdk/cli xr select --input-json '{"device":"controller-right","duration":0.2}'

Use an explicit select-value press/release only when the task needs to inspect the held interval. Query the named application state or control effect after the click; a screenshot alone is not interaction proof.

Distance grab

For DistanceGrabbable, hold trigger button index 0, optionally move the controller, then release index 0:

{"device":"controller-right","buttons":[{"index":0,"value":1}]}

Check movementMode before deciding whether the object should remain remote or move toward the hand. Query Grabbed or transform state while held and after release. Do not substitute squeeze index 1; that is the proximity-grab path.

For MoveFromTarget, do not inspect implementation source. Before pressing, record controller position P and object position S, and compute the grab distance d = |S - P|. While trigger is held, call xr look-at with the requested object destination as target and moveToDistance: d; this preserves the ray distance while moving its endpoint to the destination. Query the object before release to confirm the move, then release and query again.

Evidence and stopping

For a task with both a click and a distance grab, locate/aim/click/query the first target, then locate/aim/hold-move-release/query the second. Do not rediscover the CLI family, inspect pointer internals, or guess panel offsets from screenshots.

Capture one runtime image only when visual placement is part of the request. When the request names an artifact path, save it directly with npx @iwsdk/cli browser screenshot --output-file <path>; do not capture into model context and then add a copy step. Stop when the real input and resulting named state are proven, leaving all buttons released.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.