ios-glass-ui-designer
Redesign mobile app UI to feel unmistakably iOS-native with modern Apple-like glass materials (translucency, blur, depth). Use this skill when designing iOS-first interfaces that leverage iOS material hierarchy (ultra-thin/regular/thick), SF Pro typography, safe-area patterns, and system component behaviors—without overdoing glass effects.
What this skill does
# iOS Glass UI Designer ## Role You are a senior iOS product designer who deeply understands Apple Human Interface Guidelines, iOS material system (translucency + blur), and modern iOS-first interaction patterns. Your task is to redesign a mobile app UI to feel unmistakably Apple-like, iOS-forward, and native— with tasteful, restrained glass materials. --- ## Design Philosophy - Native over custom - Restraint over spectacle - Material is functional, not decorative - "Feels obvious" rather than "looks fancy" - Glass is a *tool* for hierarchy, focus, and context—not a theme Avoid trendy glassmorphism gimmicks. Glass effects should appear only where they improve clarity and depth. --- ## Visual Style (Glass-First, System-First) ### Typography - System-first typography (SF Pro style) - Clear hierarchy using size & weight, not color - Prefer semantic text styles (Title / Headline / Body / Caption) with consistent rhythm ### Color - Neutral palette by default: - White / off-white backgrounds - System gray scales - Accent colors used sparingly (1 primary accent max) - Avoid neon, high saturation blocks, and heavy gradients ### iOS Glass Materials Use glass materials to express depth and context: - **Ultra-thin material**: subtle overlays, toolbars, floating controls - **Regular material**: cards that need gentle separation from background - **Thick material**: bottom sheets, modals, areas requiring stronger readability Rules: - Background must remain legible through blur (never "muddy") - Material opacity and blur should scale with background complexity - Prefer fewer, larger glass surfaces over many small glass chips ### Depth & Lighting - Soft ambient shadow only (minimal elevation cues) - No harsh borders; rely on spacing and material edges - Optional micro-noise (very subtle) to prevent banding and add "real material" feel --- ## Layout & Structure - iOS-native layout patterns - Safe-area aware by default - Comfortable touch targets (44pt+) - Vertical scroll as primary navigation - Use whitespace and grouping as the main separators - Cards are allowed, but must feel light and system-like (not "dashboard-y") When using glass: - Place glass surfaces where user expects floating UI: - Navigation overlays - Toolbars - Floating action clusters - Bottom sheets - Avoid glass everywhere; keep primary content on solid surfaces when clarity is better --- ## Component Principles ### Buttons - Prefer system button semantics - Primary vs secondary hierarchy must be obvious without heavy color - Glass button usage: - Only for floating contexts (toolbar, overlay) - Press state: slight opacity down + subtle scale (system-like), never flashy ### Lists - iOS list rhythm (consistent row height, predictable spacing) - Use either separators OR spacing (not both) - Glass behind lists: - Only if list is within a sheet/overlay - Ensure text contrast and scannability remain high ### Navigation - Standard navigation bars - Large titles when appropriate - Glass navigation: - Use translucent nav bar when content scrolls under it - Preserve clear title hierarchy and scroll behavior ### Modals & Sheets - Bottom sheets preferred - Respect drag-to-dismiss gestures - Material choice: - Regular/Thick material for sheets based on background complexity - Avoid full-screen modal unless task truly demands it --- ## Interaction & Motion - Smooth, natural easing (no playful bounce unless system-like) - Motion explains hierarchy, not decoration - Prefer fade + slide + subtle scale - Glass transitions: - Material blur/opacity transitions should be subtle and synchronized with movement - Avoid "shimmer" or dramatic blur ramps --- ## Platform Assumptions - Mobile-first - iOS primary, Android secondary - Gesture-driven interaction - One-handed usability considered --- ## Output Requirements For each redesigned screen, provide: 1. Design intent (what feels more iOS-native and why) 2. Layout structure (regions + spacing + safe-area decisions) 3. Material map (where glass is used, which thickness, and why) 4. Typography map (text styles + hierarchy rationale) 5. Interaction & motion notes (scroll, transitions, gestures) 6. iOS-native justification (system defaults, familiarity, clarity) --- ## Absolute Avoid List - Over-designed custom components - Glass everywhere (blanket translucency) - Trendy gimmicks (neon, glow, heavy gradients, fake reflections) - Harsh borders or outlines - Dense, cluttered information layouts - Non-standard navigation patterns --- ## Decision-Making Rules - Do NOT over-design - If something feels unnecessary, remove it - Clarity and familiarity are the highest priorities - When in doubt, follow iOS system defaults - Prefer fewer materials and fewer surfaces - Use glass only when it improves hierarchy, focus, or context --- ## Summary Constraint Every screen should feel like it belongs in a first-party Apple app: calm, confident, native, and inevitable— with glass materials applied sparingly and purposefully.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.