mobile-image

name	mobile-image
description	Activate when a user requests mobile app screen images, onboarding flows, or multi-screen app concepts as image output — this skill generates premium mobile UI images only, it does not write code.
version	1
category	image-generation
outputs	images

Mobile Image

Purpose

This skill generates premium mobile app screen images and screen-flow sets. Output is always image-only — no SwiftUI, Flutter, React Native, or HTML code. Screens are shown inside a clean phone mockup by default. The goal is to produce believable, app-native screen images that could serve as a design direction or investor-facing concept — not a wireframe collage or template demo.

When to Activate

• User requests mobile app screens, onboarding flows, or multi-screen app concepts
• User wants to visualize a mobile app without building it
• User asks for an app concept, mockup, or design direction
• User describes a mobile use case: onboarding, home dashboard, profile, settings, commerce, etc.

When Not to Activate

• User needs mobile app code (use a code-generation skill)
• User wants a website on mobile (use web-image)
• User wants brand identity images (use brand)
• The request is clearly for a desktop-first interface

Core Principles

1. Platform-native, not website-in-a-phone. Every screen respects mobile UI conventions: safe area awareness, status bar zones, tab bar or navigation bar at the correct position, touch-friendly element sizing. A screen that looks like a shrunk website is a failure.

2. Phone mockup present by default. Show screens inside a clean iPhone-style or Android-style frame unless the user asks for raw screen output. The device frame supports the content — it must not dominate it. Equal, balanced outer margins on all four sides of the canvas.

3. Generate enough screens for the flow. If the user asks for an onboarding flow, generate multiple distinct onboarding screens — not one. If the user asks for an app concept, generate at minimum a home screen plus 2–3 supporting screens. Single-image output for multi-screen requests is a failure.

4. Consistency across all screens. Before generating screen 2+, establish the design bible: device frame style, palette, type system, corner radius, icon style, navigation model. All screens must belong to the same product world.

5. Text must be comfortably readable. No decorative small type. If copy is too small to read at normal viewing size, the design is not finished. Simplify the layout, reduce content, or increase the type scale.

6. Color must be intentional. Every app gets a specific, controlled palette. Avoid: generic purple-blue startup gradients, random bright saturated colors with no relationship, muddy accidental color combinations. The palette should make the app feel distinctive and deliberate.

7. Non-generic art direction is required. Every app category has a default AI look. Push beyond it. A fintech app does not default to dark-blue dashboard with chart spam. A wellness app does not default to pastel gradient cards with leaf icons.

8. Images and texture are design tools. When appropriate, use photography, editorial crops, background imagery with fade treatments, and surface textures (grain, noise, matte paper feel) to make screens feel richer. These must feel intentional.

Configuration

Parameter	Scale	Default
PLATFORM	iOS / Android / cross-platform	iOS
DESIGN_VARIANCE	1–10	8
VISUAL_DENSITY	1–10	3
ART_DIRECTION	1–10	9
TEXTURE_STRENGTH	1–10	7
CONSISTENCY	fixed at 10	10

Workflow

1. Establish platform and context. Determine: iOS-native / Android-native / cross-platform; app category; primary user action on the most important screen.

2. Lock the design bible. Before generating any screen, commit to: device frame style, palette (max 1 accent, controlled background), typography character, corner radius system, icon style, navigation model, surface treatment.

3. Plan the screen set. List all screens to be generated in flow order. Every screen has a reason: what action led here, and what is the primary action available from this screen.

4. Generate screens in flow order. Start with the highest-impact screen. After each screen, verify it belongs to the same design system as the previous screen.

5. Check for mobile-specific issues. After generating: is safe area respected? Is the navigation region clear? Are CTAs large enough to tap comfortably? Is text legible?

6. Generate detail images if needed. If a card, form, or component needs closer inspection, generate a dedicated detail render. Do not crop from an existing screen.

7. Run Quality Gates.

Screen Flow Reference

Build logical progressions, not random screen collections:

• Onboarding → auth → home
• Home → browse → detail
• Profile → settings → edit profile
• Cart → checkout → confirmation
• Dashboard → activity → detail view
• Welcome → permissions → personalized home

Category-Specific Guidance

Category	Priority
Fintech	Trust, calm spacing, clear numbers, restrained accents, no fake chart spam
Health / Fitness	Clean metric hierarchy, motivating without noisy effects, airy spacing
Productivity	List and card discipline, simple navigation, calm density
Social	Profile and feed rhythm, media moments, expressive image direction
Commerce	Browse/detail/cart clarity, strong product imagery, stable card proportions
Wellness	Softer materials, calm type, breathing room, elegant imagery, soft fades

Forbidden Patterns

Visual tells:

• Purple-blue gradient as the entire design identity
• Glass cards floating in space with no visual logic
• Ambient blobs as the only background treatment
• Radius-full on every single element
• Gradient overlay substituting for actual art direction

Layout tells:

• Websites shrunk into phone frames
• Homepage with 12 floating stat widgets
• Cloned onboarding slides — only icon and headline change between slides
• Giant empty card areas with very little content

Copy tells:

• "Elevate your life" / "Unlock your potential" / "Seamless control" / "Transform your day"
• Generic fake app names: Acme, Flowbit, VeloPay, NovaCore, Quantix

UI clutter tells:

• More than 4 pills or chip labels visible simultaneously on one screen
• Fake toggles with no product meaning
• Duplicate navigation elements (tab bar AND hamburger simultaneously)
• Random decorative avatar rows with no product purpose

Device presentation tells:

• Device frame touching the canvas edge
• Different device scales across screens in the same set
• Device frame so thick it dominates the screen content
• Uneven canvas margins around the device

Output Requirements

• At least as many screen images as the user requested
• All screens inside a consistent phone mockup with equal canvas margins
• All visible text legible at normal viewing size
• All screens clearly belonging to the same product (consistent design bible)
• Screen flow is logical — each screen follows naturally from the previous

Quality Gates

• Platform mode selected and applied consistently
• Design bible locked before screen 2 was generated
• All text legible at normal viewing size
• Safe areas respected (status bar, home indicator, navigation bar regions)
• Navigation logic is believable (tab bar, stack, sheet — not random)
• Screen flow is logical from first to last
• All screens use the same device frame style at the same scale
• Device frame has equal canvas margins on all four sides
• Color palette is intentional (not generic gradient or random)
• No generic AI mobile tells present
• First screen is clean and not overcrowded
• No text is decoratively small
• Screen set feels like a real app, not a template demonstration
• Iconography feels intentional (not generic library-default)

Failure Modes

"Website in a phone": Screens show a text-heavy layout without navigation bar, tab bar, or touch-aware structure. Detection: no visible nav bar, no bottom navigation, no safe area awareness. Fix: add native navigation structure and constrain content to mobile-appropriate hierarchy.

"Template sameness": Onboarding screens are the same layout with only icon and headline changes. Detection: 3+ screens with identical structure. Fix: vary composition, image usage, and text balance across screens.

"Inconsistent product": A later screen uses a different palette and corner radius system. Detection: compare palette and radius across all frames. Fix: re-apply the design bible to the drifting screen.

"Tiny text": Labels and body copy are too small to read. Fix: simplify the layout, remove secondary elements, increase type scale. If needed, regenerate the screen.

"Missing mockup": Screens delivered as raw UI without a device frame. Fix: regenerate inside a clean phone mockup with balanced outer margins.

Response Format

Generate screen images directly. Optionally lead with a 5-bullet design brief (platform, visual direction, palette logic, key screens in the set, art direction choice). Do not include post-delivery analysis unless the user asks for it.