mobile-native

Applies CSS and meta-tag fixes that make web apps feel native on mobile devices.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/quanthubbr/tron-claude-config --skill mobile-native-quanthubbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-native
Source: https://github.com/quanthubbr/tron-claude-config/tree/main/managed/skills/emilkowalski/mobile-native
Command: npx skills add https://github.com/quanthubbr/tron-claude-config --skill mobile-native-quanthubbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web apps often feel like websites on phones due to sticky hover states, tap highlight flashes, the 100vh viewport bug, input-triggered page zoom, laggy taps, and content hidden under the notch. This Skill diagnoses and fixes each of these platform-layer issues with targeted CSS declarations and meta tags. ## Core Features & Use Cases - Symptom-to-Fix Mapping: Match visible problems (gray flash on tap, stuck hover, wrong layout height) to exact one-line CSS or HTML fixes. - Baseline Mobile Setup: Ship a correct viewport meta tag, theme-color per color scheme, safe-area padding, and touch-action rules before the first component. - Use Case: You built a PWA with a bottom sheet and carousel, but on a real phone the carousel jitters vertically and the sheet sits under the home indicator. Use this Skill to apply touch-action: pan-y and env(safe-area-inset-bottom) padding. ## Quick Start Ask the AI to review your web app's mobile CSS and fix everything that makes it feel like a website instead of an installed app on a phone.

Frequently Asked Questions about mobile-native

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix hover states stuck after tap on mobile?▼

Wrap every :hover rule in @media (hover: hover) and (pointer: fine) so it only applies to devices with a precise pointing input. Touch users get press feedback through :active styles instead, which work on every input type.

How to stop iOS Safari from zooming into input fields?▼

Set input, textarea, and select font-size to at least 16px, since iOS zooms when focused inputs are smaller. Never use maximum-scale=1 or user-scalable=no, which are accessibility failures.

Why does 100vh break my mobile layout?▼

100vh equals the largest viewport height with browser chrome collapsed, so content overflows when the URL bar is visible. Use 100dvh for app shells that track the visible area and 100svh for heroes that must never be cut off.

How do I handle the iPhone notch and safe areas in CSS?▼

Add viewport-fit=cover to the viewport meta tag so the page paints edge to edge, then pad fixed headers and bottom bars with env(safe-area-inset-top) and env(safe-area-inset-bottom). Without the meta tag, the env() values are all zero.

Can I test mobile touch issues in Chrome device emulation?▼

No. Sticky hover, tap highlight, the click delay, overscroll, safe areas, and the software keyboard only reproduce on real hardware. Connect a phone over USB and use Safari Web Inspector or chrome://inspect for debugging.

When should I not use this mobile web approach?▼

This Skill covers the web platform layer only. For motion design use an animation skill, and for React Native apps use a native-specific skill, since viewport units and meta tags do not apply there.