mobile-first-ui-review
Review and improve mobile-first UI for apps, web products, SaaS, utilities, and games across touch ergonomics, safe areas, navigation, forms, permissions, loading, offline states, and perceived speed. Use when designing or auditing mobile interfaces, responsive mobile views, onboarding screens, purchase flows, settings, or any UI that must feel fast and modern on phones.
Works with
--- name: mobile-first-ui-review description: Review and improve mobile-first UI for apps, web products, SaaS, utilities, and games across touch ergonomics, safe areas, navigation, forms, permissions, loading, offline states, and perceived speed. Use when designing or auditing mobile interfaces, responsive mobile views, onboarding screens, purchase flows, settings, or any UI that must feel fast and modern on phones. license: MIT --- # Mobile First UI Review Use this skill to make mobile experiences feel native, fast, and easy to operate with one hand. ## Workflow 1. Identify the primary mobile job, screen type, and device constraints. 2. Read `references/mobile-ui-rules.md`. 3. Review the UI through hierarchy, reachability, input, feedback, platform chrome, accessibility, and failure states. 4. Separate critical blockers from polish opportunities. 5. Produce a concrete patch plan or review findings with rule IDs. ## When not to use - Do not use for generic advice the base model already handles without this skill's specific artifact contract. ## Guardrails - Do not optimize only for screenshots; optimize the lived touch flow. - Preserve accessibility, reduced motion, dynamic type, safe areas, and keyboard behavior. - Prefer removing friction before adding decoration. ## Output format ```text Surface: Primary mobile job: Critical issues: - <rule id> <issue> -> <fix> Polish opportunities: - <rule id> <detail> -> <fix> Accessibility checks: - Screen reader: - Focus order: - Dynamic type / text scaling: - Motion and animation: Mobile acceptance checks: - <check> ```
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

