enhance-readmelisted

> ### Which enhance skill? (surface router) > > | Your surface | Use | > |:-------------|:----| > | **Web** product page / dashboard — composition, hierarchy, spacing, motion | `enhance-web-ui` | > | **Web** product page — UX heuristics, flows, data wiring | `enhance-web-ux` | > | **Web** landing / marketing / portfolio (greenfield, anti-slop) | `enhance-web-landing` | > | **Web** existing site upgrade (audit-first, preserve behavior) | `enhance-web-redesign` | > | **Web** 3D / WebGL / cinematic scroll on an existing site (audit-first) | `enhance-web-web3d` | > | **React Native** screen (Expo / bare) | `mobile-rn-screen` | > | **Capacitor / hybrid** shell (one web app shipped to iOS + Android) | `enhance-capacitor-ui` (axis architecture first) → then the web or rn skill | > | Repo **README** showcase | `enhance-readme` | > > **You are here: `enhance-readme`.** Native iOS/Android (SwiftUI / Compose, no web layer) is out of scope for all of these — use Apple HIG / Material directly. # Enhance README Add a theme-aware hero image and a tour grid to a project's README so the repo advertises itself visually instead of being a wall of text. ## Critical Rules > **Use the live production URL when one exists.** It shows real data, no dev banners, and matches what visitors will see if they click through. > **Always capture both dark AND light mode** for any image that goes in the hero. GitHub renders the README in both themes; broken contrast on one of them looks worse than no imag