Claude-skill-registry interaction-latency
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/interaction-latency" ~/.claude/skills/majiayu000-claude-skill-registry-interaction-latency && rm -rf "$T"
manifest:
skills/data/interaction-latency/SKILL.mdsource content
Interaction Latency
Time from user tap to action successfully completed.
When to Use
- "Add to cart" button tapped → cart updated
- "Submit" button tapped → form processed
- "Like" button tapped → state changed
- Any tap that triggers async work
Measurement Pattern
TAP → START_SPAN → [async work] → END_SPAN
- Capture tap timestamp
- Start span with operation name
- End span when action confirms success
- Include success/failure outcome
Key Thresholds
| Rating | Duration |
|---|---|
| Good | <300ms |
| Acceptable | <1s |
| Poor | >1s |
Implementation
See
references/ui-performance.md (Entry Point Latency section) for platform-specific code.
Common Mistakes
- Ending span on API call start (not completion)
- Not tracking failure cases
- Missing the tap timestamp (starting late)
Related Skills
- See
for screen-to-screen transitions (vs single-tap actions)skills/navigation-latency - Combine with
for friction detection on key interactionsskills/user-journey-tracking