Skip to content
Back to skills

Ztx14 Curated Motion Hover Cross Device

ASecurity

Implement hover affordances with Motion’s gesture recognition or CSS capability queries so touch interactions do not remain in a fake hover state.

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

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx14-curated-motion-hover-cross-device --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx14 Curated Motion Hover Cross Device?

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

Security grade badge for Ztx14 Curated Motion Hover Cross Device
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx14-curated-motion-hover-cross-device/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx14-curated-motion-hover-cross-device)

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: ztx14-curated-motion-hover-cross-device
description: Implement hover affordances with Motion’s gesture recognition or CSS capability queries so touch interactions do not remain in a fake hover state.
---

# Cross-device hover without sticky touch states

> Curated implementation skill. Inspect the installed project and actual component source before changing behavior. Do not assume latest APIs are installed. Preserve unrelated files and existing component ownership.

## Use for
Buttons, cards, labels, and non-essential decorative hover. It is not a replacement for click/tap or keyboard semantics.

## Rules
1. Prefer Motion’s `whileHover`/`hover()` when the interaction should only count as an actual hover gesture. Its hover API is designed to filter emulated touch hover states.
2. For CSS-only effects, scope hover with `@media (hover: hover) and (pointer: fine)`. Provide active, focus-visible, and selected states separately.
3. Do not hide important text, actions, or state exclusively behind hover. A tap target must work without hover.
4. Reset transient visual state on pointer cancel, blur, route transition, and component unmount.
5. Verify keyboard focus, touch tap, pen input, mouse enter/leave, and leaving the browser viewport.

## Acceptance matrix
- Mouse: enter and leave settle without flicker.
- Touch: tap activates the actual action; a stale hover does not persist.
- Keyboard: focus visibly communicates the same actionable affordance.
- Reduced motion: state change remains apparent with minimal movement.

## Primary references
- [motion-hover](https://motion.dev/docs/react-hover-animation)
- [pointer-events](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events)
- [tailwind-responsive](https://tailwindcss.com/docs/responsive-design)
- [reduced-motion](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/%40media/prefers-reduced-motion)

## Completion evidence
- State what was inspected, what changed, and which checks actually ran. Never report unrun tests or unverified browser behavior as passing.

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.