What is pn-spatial-ux-patterns?

A guide to designing interfaces for augmented, virtual, and extended reality, where controls and content are placed in three-dimensional space. It covers depth, scale, comfort, interaction zones, and readable text.

Use it to design headset or WebXR menus, 3D panels, hand-tracking controls, gaze interactions, and immersive layouts for devices such as Quest, Vision Pro, or HoloLens.

It helps prevent awkward or uncomfortable interfaces by placing controls at usable distances and adapting designs to the user's device and posture.

pn-spatial-ux-patterns — Skill for Cursor by perniemann/pnCore

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add perniemann/pnCore --skill pn-spatial-ux-patterns

Clone the repo

git clone --depth 1 https://github.com/perniemann/pnCore

Made for: Cursor.

Or install pn-core, the plugin that ships this one along with the rest of its 133 skills, 19 commands, 9 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/perniemann/pncore/pn-spatial-ux-patterns/github.svg)](https://agentmods.dev/skills/perniemann/pncore/pn-spatial-ux-patterns)

Your own site

<a href="https://agentmods.dev/skills/perniemann/pncore/pn-spatial-ux-patterns"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-spatial-ux-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/perniemann/pncore/pn-spatial-ux-patterns"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-spatial-ux-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,028 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.01028
Opus 5.5	$0.00016	$0.00411
Sonnet 5.5	$0.00008	$0.00206
Haiku 4.5	$0.00004	$0.00103

Measured 2mo ago against content hash 9811d6f2ecdd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pn-spatial-ux-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/pn-core-mcp/content/skills/gamedev/pn-spatial-ux-patterns/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spatial UX patterns

When to use

AR/VR/XR interface design.
Spatial interaction patterns.
3D UI placement, depth, layout.
Immersive UX for headsets and spatial displays.

Workflow

Context: Platform (Quest 3, Vision Pro, HoloLens, browser WebXR), use case, user posture (seated, standing, walking).
Architecture: UI placement, depth layers, interaction zones.
Patterns: Apply the patterns documented below for menus, controls, and feedback in 3D space.
Document: Specs for implementation.

Depth layers

Organize UI and world content into three depth zones:

Zone	Distance	Use
Near	< 0.5 m	Direct manipulation, hand tracking menus, pinch targets
Mid	0.5 – 2 m	Primary content panels, action buttons, gaze-and-commit controls
Far	> 2 m	Ambient information, world labels, navigation waypoints

Never place interactive elements closer than ~0.4 m — creates eye strain and missed tracking.
Never use a far-zone element for a critical action; bring it to mid-zone when interaction is needed.
Use depth cues (subtle shadow, scale-at-distance, opacity falloff) to reinforce layer hierarchy.

Ergonomic gaze angles

Keep interactive content within the comfortable gaze cone:

Horizontal: ±35° from forward axis (Quest 3 / Vision Pro recommendation)
Vertical: −20° (below horizon) to +10° (above horizon) — users rest gaze slightly below horizontal
Avoid placing primary actions at extreme angles; use anchor points that follow the user's head rotation lazily (lag = 0.2–0.3 s) to keep content in zone without snapping.

Interaction zones and input models

Zone	Distance	Primary input
Direct touch	< 0.5 m	Hand-tracking: pinch, poke, palm
Ray cast / point	0.5 – 2 m	Gaze + commit, controller ray, vision OS eye + hand
Voice / ambient	> 2 m	Voice commands, passive awareness

For Quest 3 / Vision Pro: implement at minimum ray-cast + pinch. Hand tracking is the primary modality; controller as fallback.
For WebXR (browser): use XRSession select event for primary action; selectstart/selectend for hold. Support both controller (XRInputSource.targetRayMode = 'tracked-pointer') and gaze ('gaze').
Provide visual feedback on hover/proximity (highlight, scale pulse) within 0.1 s of gaze entry — response latency above 150 ms feels broken in XR.

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 93 lines · 40 tokens per session scan A 9811d6f2ecdd

Subscribe to this mod's changes

pn-spatial-ux-patterns is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,028 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Design and UX Game development LLM TypeScript agents cursor mcp plugin

pn-spatial-ux-patterns next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pn-spatial-ux-patternsperniemann/pnCore	Skill	0	5d ago	MIT	A	40	Cursor
design-to-codeyonatangross/orchestkit	Skill	299	yesterday	MIT	A	54	Claude Code
design-shipyonatangross/orchestkit	Skill	299	yesterday	MIT	A	50	Claude Code
design-system-tokensyonatangross/orchestkit	Skill	299	yesterday	MIT	A	38	Claude Code
figma-design-handoffyonatangross/orchestkit	Skill	299	yesterday	MIT	A	76	Claude Code
mcp-visual-outputyonatangross/orchestkit	Skill	299	yesterday	MIT	A	48	Claude Code
taiyi-diagram-archDong90/oh-my-taiyiforge	Skill	852	25d ago	MIT	A	48	Claude Code, Codex