mobile-hybrid-auditlisted

Audit and fix web projects for pixel-perfect mobile experience as PWA, Capacitor app, or hybrid. Use this skill whenever the user mentions mobile audit, mobile-ready, mobile responsive, PWA, Progressive Web App, Capacitor, hybrid app, mobile app from web, iOS WebView, Android WebView, safe areas, notch handling, edge-to-edge, mobile keyboard issues, splash screen, status bar, mobile viewport, app store readiness, or asks to "make this work on mobile", "prepare for iOS/Android", "ship as a mobile app", "fix mobile bugs", "audit my PWA", or any request involving turning a web app into a mobile-grade experience. Also trigger when the user shows symptoms like content under the notch, footer hidden by keyboard, splash screen stuck, status bar overlap, 100vh issues, or input zoom on iOS.
kachouri/mobile-hybrid-audit · ★ 0 · Web & Frontend · score 72

Install: claude install-skill kachouri/mobile-hybrid-audit

# Mobile Hybrid Pixel-Perfect Audit & Fix This skill audits and fixes web projects to deliver a production-grade mobile experience as PWA, Capacitor app, or both. The goal is a native-feeling app that is stable, responsive, safe-area aware, keyboard-friendly, with a clean splash and status bar, and installable as a PWA — without breaking existing styling or features. ## When to use Trigger this skill when the user wants to: - Audit an existing web app for mobile readiness - Fix specific mobile bugs (notch overlap, keyboard, scroll, viewport) - Add or improve PWA support (manifest, service worker, install) - Add or improve Capacitor wrapping (iOS/Android) - Prepare a project for App Store / Play Store submission - Migrate from web-only to hybrid mobile ## When NOT to use - Building a brand new app from scratch with a full visual redesign — this skill preserves existing design, it doesn't reinvent it - Pure native development (Swift, Kotlin) — Capacitor only - Pure CI/CD pipelines — use a dedicated Capacitor CI/CD skill - Backend / API work - React Native or Flutter projects — this skill is web-based hybrid only ## Working principles 1. **Read before editing.** Always inspect the current state of a file before modifying it. Preserve existing styles and conventions. 2. **Minimal but robust changes.** Improve what exists; don't duplicate or rewrite wholesale. 3. **Justify every change.** The final report must list each modification with reasoning. 4. **Detect, then act.**