Mobile-Native Web Feel
Make a mobile web app feel installed — the small CSS and meta-tag fixes that remove every "website" tell
- What
- Make a mobile web app feel installed — the small CSS and meta-tag fixes that remove every "website" tell
- Cost
- Free
- Needs
- a mobile-facing web app or PWA; a real phone for verification (USB + Safari Web Inspector or chrome://inspect)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a fix-it skill from Emil Kowalski's design-engineering philosophy. Important and explicit: this is about mobile WEB apps (PWA), not React Native — a handful of CSS and meta-tag lines decide whether the app feels installed or like a website in a browser. Covers the symptom table every mobile web dev hits: sticky hover states gated behind `(hover: hover) and (pointer: fine)`, killing the tap highlight flash, `100dvh`/`100svh` instead of `100vh`, 16px inputs (never `user-scalable=no` — an accessibility failure), killing the 300ms tap delay with `touch-action: manipulation`, taming pull-to-refresh with `overscroll-behavior`, safe-area padding under the notch, tap feedback on `:active`/`pointerdown`, per-scheme `theme-color`, and the hard rule that a desktop device toolbar is not a phone — test on real hardware over USB. Opinionated and brief: each fix ships with its why, and where the honest answer is "I can't verify this without a device," it says so. By @emilkowalski, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a mobile-facing web app or PWA; a real phone for verification (USB + Safari Web Inspector or chrome://inspect) Install "Mobile-Native Web Feel" for me. Make a mobile web app feel installed — the small CSS and meta-tag fixes that remove every website tell. Note: this is mobile web/PWA, not React Native Repository: https://github.com/emilkowalski/skills/blob/main/skills/mobile-native/SKILL.md 1. Fetch the SKILL.md file for the emilkowalski-skills-mobile-native skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "emilkowalski-skills-mobile-native". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.