Skip to content
Back to skills

Ztx4 Interaction System Input Latency Budget

ASecurity

Implement input latency budget for Advanced Interaction System with concrete acceptance gates, responsive/RTL safety, and no MCP. Additive Perfect_AI extension.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
documentationreactspringdocumentation

Works with

  • mcp

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx4-interaction-system-input-latency-budget --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx4 Interaction System Input Latency Budget?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztx4 Interaction System Input Latency Budget
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx4-interaction-system-input-latency-budget/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx4-interaction-system-input-latency-budget)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztx4-interaction-system-input-latency-budget
description: "Implement input latency budget for Advanced Interaction System with concrete acceptance gates, responsive/RTL safety, and no MCP. Additive Perfect_AI extension."
---

# Advanced Interaction System / input-latency-budget

## Precise purpose
Keep interaction handler work low and defer nonessential computation.

## First read
- `$perfect-ai-master` and `$ztx3-nexus-master` remain available; never overwrite or replace them.
- `../../extensions/DEEP-IMPLEMENTATION-v2/references/interaction-system.md` inside the full pack.
- Consult corresponding existing NEXUS handbook at `extensions/handbooks/interaction-system.md`.
- This is a new supplemental Skill, not a claim that third-party software is bundled.

## Input contract
Inputs: pointer/keyboard gestures and interaction/state specification, touch-action, inertial limits.

## Implementation workflow for this technique
1. **Identify specific need:** Keep interaction handler work low and defer nonessential computation.
2. **Baseline:** inspect existing code and record behavior and compatible dependency versions; keep old behavior unchanged.
3. **Build:** Implementation: pointer capture + cancellation, spring integration with bounded dt, accessible semantic buttons and keyboard equivalent; one animation owner.
4. **Technique-specific output:** create a named source module, stylesheet, fixture and test targeting `input-latency-budget` rather than a generic screenshot.
5. **Variations:** desktop / compact container / 320px mobile / Persian RTL / English LTR / reduced motion / blocked external assets.
6. **Measure:** log what runs with concrete outputs, fail gracefully when engine or browser support unavailable.
7. **No regressions:** do not delete, reformat or overwrite unrelated existing application code.

## Technique-specific verification
- Assert: Keep interaction handler work low and defer nonessential computation.
- Tests: pointercancel/Escape/blur, drag beyond bounds, touch no-hover, keyboard, reduced-motion and multi-pointer conflict.
- Keyboard users complete the same interaction.; Pointercancel/Escape/blur reset state without stuck drag.; Effects do not move or hide semantic hit target.

## Deliverables
`implementation-notes.md`, source implementation, relevant fallback source, test fixture, screenshots if browser-run, `verified-results.json` showing passed/failed/unrun.

## Source of truth
- [rive](https://rive.app/docs/runtimes/react/react)
- [wcag](https://www.w3.org/TR/WCAG22/)
- [animejs](https://animejs.com/documentation/)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.