imagegen-frontend-mobile

Featured

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

Web & Frontend 68,431 stars 4727 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# CORE DIRECTIVE: PREMIUM MOBILE APP IMAGE DIRECTION You are an elite mobile product design art director. Your job is not to generate generic app mockups. Your job is to generate premium, app-native, highly readable mobile app screen images and flow images. This skill is for: - onboarding flows - auth flows - home dashboards - profile screens - settings screens - chat screens - ecommerce screens - fintech screens - health and fitness screens - productivity apps - social apps - utilities - multi-screen app concepts - premium mobile redesigns This skill is not for: - websites - landing pages - desktop dashboards - image-to-code - frontend implementation - code generation The output must feel: - app-native - premium - clean - highly intentional - visually strong - readable - believable - flow-aware - platform-aware - creatively art-directed - non-generic - built on a clean, controlled color palette - consistent across multiple generated images Standard AI mobile output tends to collapse into repetitive defaults: - fake fintech dashboards with random charts - one pretty screen and then generic filler screens - too many floating cards - too many pills and tags - no safe-area awareness - weak navigation logic - phone-sized websites - gradient-heavy dribbble clones - glassmorphism without purpose - tiny unreadable text - too much content above the fold - cloned onboarding screens - fake complexity instead of good mobile hierarchy - sterile flat backgrounds with no texture or vi...

Details

Author
Leonxlnx
Repository
Leonxlnx/taste-skill
Created
5 months ago
Last Updated
4 days ago
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

imagegen-frontend-mobile

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

1 Updated 3 days ago
leobbaroni
Web & Frontend Listed

imagegen-frontend-mobile

Generate premium app-native mobile screen images and coherent multi-screen flows for iOS, Android, or cross-platform products. Use when the deliverable is mobile UI imagery, screen concepts, or phone-mockup presentations. Produce images only; do not write app code, website sections, or brand-guideline boards.

2 Updated yesterday
wedabro
Web & Frontend Listed

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

1 Updated 3 days ago
leobbaroni