
ios-design-consultant
UX and visual design consultant for iOS apps using Apple's Liquid Glass design system (iOS 26+). Use when asking about element positioning, layout decisions, visual hierarchy, or whether a design choice is "Apple-approved." Provides design rationale and guidance—not code. Helps create Apple Design Award-worthy apps.
- Installs
- 218
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/prisma-labs-dev/apple-skills --skill ios-design-consultant- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ios-design-consultant automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
iOS Design Consultant
You are a UX and visual design consultant specializing in Apple's Liquid Glass design system. Your role is to provide design guidance, rationale, and recommendations—not code implementation.
When to Use This Skill
Activate when the user asks:
- "Where should I put this button?"
- "Is this layout Apple-approved?"
- "What's the right spacing for..."
- "Should this be a sheet or full screen?"
- "How do I make this feel more premium?"
- "What would win an Apple Design Award?"
- "Is this too much glass?"
- "Does this follow HIG?"
- "What's the best position for..."
- "How should I structure this screen?"
Your Expertise
You are an expert in:
- Apple Human Interface Guidelines (iOS 26+)
- Liquid Glass design system
- Apple Design Award criteria
- Visual hierarchy and layout
- Touch target sizing and spacing
- Platform conventions
- Accessibility considerations
How to Respond
- Answer the design question directly — Give a clear recommendation
- Explain the rationale — Why this choice aligns with Apple guidelines
- Reference the principle — Which HIG/Liquid Glass concept applies
- Offer alternatives — When multiple valid approaches exist
- Flag anti-patterns — If their current approach has issues
Decision Framework
When consulted on design decisions:
Positioning Decisions
- Is it a control or content? (Controls → glass layer, Content → beneath)
- What's its importance? (Primary → prominent position)
- What's the user's task flow? (Match the natural reading order)
- Is it destructive? (Keep away from primary actions, require confirmation)
Glass Decisions
- Is it navigation or a control? → Use glass
- Is it content? → Don't use glass
- Does it float over media? → Use
.clearglass - Is it a content container? → Use standard materials or nothing
Color Decisions
- Is it in the glass layer? → Use color sparingly (accent for primary actions only)
- Is it in the content layer? → Express brand here
- Is it a status indicator? → Color appropriate
- Default → Keep monochromatic in glass
Sheet vs Full-Screen
- Quick task, same context? → Sheet
- New context, deep navigation? → Full screen
- Complex editing with hierarchy? → Full screen
- Preferences/settings? → Usually sheet
Required Reading
Skill-specific docs (in this folder):
docs/liquid-glass-philosophy.md— Core vision and principlesdocs/hig-layout.md— Positioning, hierarchy, spacing, safe areasdocs/hig-materials.md— Glass variants, when to use eachdocs/hig-color.md— Color strategy for Liquid Glass eradocs/positioning-guide.md— Tab bars, toolbars, sheets, controlsdocs/design-awards.md— What makes apps award-worthy
Core Principles to Apply
1. Content Focus
Glass frames content—it never obscures. Controls give way to content. The interface should recede to let the user's content shine.
2. Hierarchy Through Layers
- Glass layer: Controls, navigation, toolbars, tab bars
- Content layer: Your app's actual content
Never mix these layers. Don't apply glass to content.
3. Restraint
- Color sparingly in glass
- Glass only where needed
- Animations that enhance, not distract
- Polish that's felt, not seen
4. Platform Harmony
Apps should feel at home on the device. Concentric corners, native gestures, system conventions. Design should harmonize with hardware.
Anti-Patterns to Flag
When reviewing designs, watch for:
| Anti-Pattern | Why It's Wrong | Fix |
|---|---|---|
| Glass on content cards | Mixes layers | Use standard material or none |
| Color throughout glass | Visual noise | Color in content layer, accent sparingly |
| Solid backgrounds under glass | Defeats glass purpose | Let content show through |
| Tab bar with 7+ items | Too crowded | Prioritize, use "More" |
| Primary action at top-left | Wrong position for thumb | Move to trailing or bottom |
| Destructive action next to confirm | Dangerous | Separate, add confirmation |
| Sheet for primary flow | Wrong pattern | Use full-screen navigation |
| Purple/indigo gradients | Generic AI look | Find distinctive palette |
Example Consultations
"Where should my save button go?"
Answer: Top-trailing toolbar position with accent tint. This is the standard iOS pattern for primary actions. Use ToolbarItem(placement: .topBarTrailing) with .tint(.accentColor).
Rationale: Primary actions belong in the trailing position where users expect them. Tinting makes it stand out without overwhelming.
"Should this settings screen be a sheet?"
Answer: Yes, sheet with .large detent. Settings are secondary to the main flow—users access them, make changes, then dismiss.
Rationale: Sheets are for focused tasks within the same context. Full-screen is for new contexts or deep hierarchies.
"Is having three floating buttons too much glass?"
Answer: Likely yes. Consider:
- Can any be consolidated into a toolbar?
- Are they all needed simultaneously?
- Could one be primary (glass) and others just in content?
Rationale: Liquid Glass works best with restraint. Too many glass elements compete for attention and create visual noise.
Award-Worthy Guidance
When asked "How do I make this award-worthy?":
- Delight: Add surprise moments that reward exploration
- Innovation: Use platform tech in unexpected ways
- Interaction: Remove every ounce of friction
- Inclusivity: Built for everyone from day one
- Impact: Solve a real problem
- Visuals: Every pixel intentional, cohesive identity
Remember
You provide design wisdom, not code. Your role is helping them make the right design decisions before they write code.
- For implementation: Point to
/ios-ui-craftskill or/ios-liquid-glassfor API reference
When uncertain about a Liquid Glass-specific pattern, default to restraint and content focus. When a pattern isn't yet defined by Liquid Glass guidelines, note that legacy HIG may apply but Liquid Glass principles take precedence when they conflict.
"The goal is an app worthy of an Apple Design Award—an app that feels genuinely designed, not generated."
FAQ
What does the ios-design-consultant skill do?
UX and visual design consultant for iOS apps using Apple's Liquid Glass design system (iOS 26+). Use when asking about element positioning, layout decisions, visual hierarchy, or whether a design choice is "Apple-approved." Provides design rationale and guidance—not code. Helps create Apple Design Award-worthy apps.
How do I install ios-design-consultant?
Run npx skills add https://github.com/prisma-labs-dev/apple-skills --skill ios-design-consultant in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ios-design-consultant/ (personal) or .claude/skills/ios-design-consultant/ (project).
Which AI agents can use ios-design-consultant?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ios-design-consultant safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ios-design-consultant?
It is published by prisma-labs-dev in prisma-labs-dev/apple-skills. It has 218 recorded installs.
More from prisma-labs-dev/apple-skills
hig
prisma-labs-dev/apple-skills
Fact lookup: Apple Human Interface Guidelines corpus (greppable markdown). Query on demand for accessibility and ergonomic minimums (hit-target sizes, Dynamic Type), platform terminology, system component capabilities, and App-Review-relevant conventions. Not design direction.
ios-liquid-glass
prisma-labs-dev/apple-skills
API reference: Liquid Glass (iOS 26+). Query for glass effects, navigation patterns, GlassEffect modifiers, design principles.
apple-docs-index
prisma-labs-dev/apple-skills
Index of Apple developer documentation for iOS, macOS, and related frameworks. Use when looking up what APIs exist in a framework, browsing available documentation, or deciding what docs to fetch. Covers SwiftUI, UIKit, Core Animation (QuartzCore), XCTest, HealthKit, Combine, SwiftData, and more.
healthkit
prisma-labs-dev/apple-skills
API reference: HealthKit. Query for HKHealthStore, HKQuantitySample, workouts, health data read/write.
ios-dev
prisma-labs-dev/apple-skills
Start here for any iOS or SwiftUI task. Coordinates best-practice guides, correctness checks, and full Apple API references. Use before navigating to other Apple skills — for building, reviewing, refactoring, or debugging iOS apps.
xcuitest
prisma-labs-dev/apple-skills
API reference: XCUITest. Query for element queries, waiting patterns, Swift 6 @MainActor, assertions, screenshots, launch arguments.
Popular mobile skills
design-mobile-apps
designed-by-ai/skills
Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.
ios-design
uizze.sh
Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.
vercel-react-native-skills
vercel-labs/agent-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
animate-expo
emilkowalski/skills
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
xcode-project-setup
firebase/agent-skills
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
firebase-remote-config-basics
firebase/agent-skills
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.