AGENT SKILL

mobile-app-design

Build high-fidelity mobile app screen prototypes — phone frames, glassmorphism UI, SVG icons, bottom nav, status bars — as HTML/CSS artifacts or Figma references.

License 许可
MIT
最近更新
2026-08-16
Stars
★ 0
Forks
0

01 前言 Front Matter

name
mobile-app-design
author
Hermes Agent
license
MIT
version
1.0.0
metadata
{ "hermes": { "tags": [ "design", "mobile", "app", "prototype", "glassmorphism", "ui", "ux", "figma", "svg", "icons" ], "related_skills": [ "claude-design", "portfolio-website-design", "popular-web-designs" ] } }
platforms
[ "linux", "macos", "windows" ]
description
Build high-fidelity mobile app screen prototypes — phone frames, glassmorphism UI, SVG icons, bottom nav, status bars — as HTML/CSS artifacts or Figma references.

02 资源文件 3

03 SKILL.md 正文

Mobile App Design

Build complete mobile app screen prototypes as high-fidelity HTML/CSS artifacts. Supports glassmorphism, dark themes, SVG icons, animations, and responsive phone frames.

When To Use

Use this skill when the user requests:

  • Mobile app screen designs or mockups
  • App UI prototypes (iOS/Android style)
  • "Build screens for my app" or "design the mobile version"
  • Figma-style mobile designs from code
  • Glassmorphism mobile interfaces
  • Design systems for mobile apps

Do NOT use for:

  • Desktop web pages (use claude-design or portfolio-website-design)
  • Static landing pages (use claude-design)
  • Token spec files (use design-md)

Figma Alternative Workflow

Figma REST API is read-only — you can read files, components, and styles, but cannot create files or add frames/components through the API. Browser automation for Figma is also unreliable (canvas rendering, not DOM).

The practical approach:

  1. Build high-fidelity HTML/CSS prototypes with phone frames
  2. Create a design token spec (colors, typography, spacing)
  3. Deliver both — the HTML serves as pixel-perfect reference for Figma recreation

When the user asks to "use Figma" or "save to Figma":

  • Explain that Figma API is read-only
  • Build the HTML prototype instead
  • Offer to open Figma in browser for manual recreation (if browser tools work)
  • The HTML prototype can also ship as the actual app (React Native Web, Capacitor)

Phone Frame Pattern

Every screen lives inside a phone frame for context:

.phone-frame {
  width: 375px;
  height: 812px;
  border-radius: 44px;
  background: var(--bg-primary);
  border: 3px solid var(--border-glass);
  overflow: hidden;
  position: relative;
  box-shadow: 0 25px 80px rgba(0,0,0,0.6), 0 0 60px rgba(var(--accent-rgb), 0.08);
}

/* Dynamic island / notch */
.phone-frame::before {
  content: '';
  position: absolute;
  top: 0;
  left: 50%;
  transform: translateX(-50%);
  width: 150px;
  height: 30px;
  background: var(--bg-primary);
  border-radius: 0 0 20px 20px;
  z-index: 100;
}

.phone-screen {
  width: 100%;
  height: 100%;
  overflow-y: auto;
  overflow-x: hidden;
  position: relative;
  scrollbar-width: none; /* hide scrollbar */
}

Status Bar

Always include a status bar at the top of each screen:

<div class="status-bar">
  <span>9:41</span>
  <div class="status-bar-right">
    <!-- Signal, WiFi, Battery SVG icons -->
  </div>
</div>
.status-bar {
  display: flex;
  justify-content: space-between;
  align-items: center;
  padding: 14px 28px 8px;
  font-size: 0.6875rem;
  font-weight: 600;
  position: relative;
  z-index: 50;
}

Bottom Navigation

Fixed bottom nav with active state indicator:

<div class="bottom-nav">
  <div class="nav-item active">
    <svg class="icon"><!-- Home SVG --></svg>
    <span class="nav-label">Home</span>
    <div class="nav-indicator"></div>
  </div>
  <!-- More nav items -->
</div>
.bottom-nav {
  position: absolute;
  bottom: 0;
  left: 0;
  right: 0;
  display: flex;
  justify-content: space-around;
  padding: 8px 16px 28px; /* extra bottom padding for safe area */
  background: rgba(10, 15, 13, 0.85);
  backdrop-filter: blur(24px) saturate(1.8);
  border-top: 1px solid var(--border-glass);
  z-index: 90;
}

.nav-indicator {
  width: 20px;
  height: 3px;
  background: var(--accent);
  border-radius: 9999px;
  opacity: 0;
  transform: scaleX(0);
  transition: all 0.35s cubic-bezier(0.34, 1.56, 0.64, 1);
}

.nav-item.active .nav-indicator {
  opacity: 1;
  transform: scaleX(1);
}

SVG Icons (No Emojis)

Always use SVG icons, never emojis. Emojis look unprofessional and render inconsistently across platforms.

Pattern for inline SVG icons:

.icon {
  width: 20px;
  height: 20px;
  fill: none;
  stroke: currentColor;
  stroke-width: 2;
  stroke-linecap: round;
  stroke-linejoin: round;
  flex-shrink: 0;
}
.icon-sm { width: 16px; height: 16px; }
.icon-lg { width: 24px; height: 24px; }
.icon-xl { width: 32px; height: 32px; }

Use Feather Icons or Lucide Icons style (stroke-based, 24x24 viewBox). Common icons needed:

  • Navigation: home, map, package, bell, user
  • Actions: search, filter, plus, edit, trash, check
  • Status: check-circle, alert-triangle, clock, wifi-off
  • Vehicles: truck, navigation, fuel, speedometer
  • Business: bar-chart, file-text, settings, log-out

Glassmorphism Components

Glass Card

.glass-card {
  background: rgba(26, 36, 32, 0.6);
  backdrop-filter: blur(24px) saturate(1.8);
  border: 1px solid rgba(74, 222, 128, 0.12);
  border-radius: 16px;
  padding: 20px;
  box-shadow: 0 8px 32px rgba(0, 0, 0, 0.4);
  transition: all 0.35s cubic-bezier(0.16, 1, 0.3, 1);
}

.glass-card:hover {
  border-color: rgba(74, 222, 128, 0.25);
  transform: translateY(-2px);
}

Glass Input

.input-field {
  width: 100%;
  padding: 16px 20px 16px 48px;
  background: rgba(26, 36, 32, 0.45);
  backdrop-filter: blur(16px);
  border: 1.5px solid rgba(74, 222, 128, 0.12);
  border-radius: 12px;
  color: var(--text-primary);
  font-family: var(--font-family);
  outline: none;
  transition: all 0.35s cubic-bezier(0.16, 1, 0.3, 1);
}

.input-field:focus {
  border-color: var(--accent);
  box-shadow: 0 0 0 3px rgba(var(--accent-rgb), 0.15);
}

Glass Button

.btn-primary {
  background: linear-gradient(135deg, var(--accent), var(--accent-dark));
  color: #fff;
  padding: 16px 32px;
  border-radius: 9999px;
  border: none;
  font-family: var(--font-family);
  font-weight: 600;
  box-shadow: 0 4px 24px rgba(var(--accent-rgb), 0.3);
  transition: all 0.35s cubic-bezier(0.16, 1, 0.3, 1);
}

.btn-primary:hover {
  transform: translateY(-2px);
  box-shadow: 0 8px 32px rgba(var(--accent-rgb), 0.4);
}

Animation Patterns

Staggered Entry

.animate-in {
  animation: fadeInUp 0.6s cubic-bezier(0.16, 1, 0.3, 1) both;
}
.animate-in-delay-1 { animation-delay: 100ms; }
.animate-in-delay-2 { animation-delay: 200ms; }
.animate-in-delay-3 { animation-delay: 300ms; }

@keyframes fadeInUp {
  from { opacity: 0; transform: translateY(24px); }
  to { opacity: 1; transform: translateY(0); }
}

Floating Element

@keyframes float {
  0%, 100% { transform: translateY(0); }
  50% { transform: translateY(-8px); }
}

Pulse Glow (live indicators)

@keyframes pulseGlow {
  0%, 100% { box-shadow: 0 0 20px rgba(var(--accent-rgb), 0.3); }
  50% { box-shadow: 0 0 40px rgba(var(--accent-rgb), 0.6); }
}

Design System Token Pattern

Always define tokens as CSS custom properties at :root:

:root {
  /* Brand */
  --accent: #22c55e;
  --accent-dark: #16a34a;
  --accent-rgb: 34, 197, 94;

  /* Backgrounds */
  --bg-primary: #0a0f0d;
  --bg-secondary: #111916;
  --bg-tertiary: #1a2420;
  --bg-glass: rgba(26, 36, 32, 0.45);

  /* Text */
  --text-primary: #f0fdf4;
  --text-secondary: #a3c4b0;
  --text-muted: #5e7a6a;

  /* Borders */
  --border-glass: rgba(74, 222, 128, 0.12);

  /* Typography */
  --font-family: 'Elms Sans', -apple-system, sans-serif;

  /* Spacing */
  --space-1: 4px;
  --space-2: 8px;
  --space-3: 12px;
  --space-4: 16px;
  --space-5: 20px;
  --space-6: 24px;
  --space-8: 32px;

  /* Radius */
  --radius-sm: 8px;
  --radius-md: 12px;
  --radius-lg: 16px;
  --radius-xl: 24px;
  --radius-full: 9999px;
}

Screen Types

Splash Screen

  • Centered logo with float animation
  • Gradient text for app name
  • Subtle background orbs (blurred circles)
  • Loading indicator

Onboarding

  • Full-width illustration area
  • Step indicator (dots)
  • Clear CTA button
  • Skip option

Login / Register

  • Large greeting text (gradient accent)
  • Glass input fields with animated icons
  • Primary CTA button
  • Social login options
  • Footer link

Dashboard

  • Greeting + avatar header
  • 2x2 stat card grid
  • Quick action grid (4 icons)
  • Map preview or chart
  • List items (vehicles, orders, etc.)

Detail / Tracking

  • Full-screen map or image
  • Floating action buttons (glass)
  • Bottom sheet with handle
  • Stats row
  • Action buttons (Call, Message, etc.)

List / Inventory

  • Search input
  • Horizontal scroll category pills
  • List items with icons, info, and status
  • Stock level bars (green/amber/red)

Settings / Profile

  • Avatar + name + role header
  • Menu items with colored icons
  • Arrow indicators
  • Version footer

Workflow

  1. Understand the brief — what app, what screens, what style
  2. Choose the design system — colors, font, glassmorphism intensity
  3. Define the screen set — which screens to build (typically 6-10)
  4. Build the HTML — single file with all screens in phone frames
  5. Add animations — staggered entry, hover states, micro-interactions
  6. Create token spec — DESIGN-SYSTEM.md with all values
  7. Verify — open in browser, check all screens render correctly

Verification

Before declaring done:

  1. All screens render correctly in phone frames
  2. Animations play smoothly
  3. SVG icons display (no broken images)
  4. Glassmorphism blur works
  5. Text is readable on all backgrounds
  6. Navigation indicators work
  7. Design token spec is complete

Pitfalls

  • Figma REST API is read-only — do not attempt to create files via the API. Build HTML prototypes instead.
  • Figma browser automation fails — canvas rendering prevents DOM-based tools from interacting with Figma.
  • Always use SVG icons, never emojis — emojis render inconsistently and look unprofessional.
  • Test glassmorphism on mobile — backdrop-filter may not work on older Android browsers.
  • Safe area padding — bottom nav needs extra padding (28px+) for devices with home indicators.
  • Don't over-animate — staggered entry is fine, but don't animate every element constantly.
  • Font loading — always include fallback fonts in case Google Fonts fails to load.

04 同仓库更多 Skills