Skip to main content
skill CX Codex

ios-design-consultant — Claude Code skill: setup and features

ios-design-consultant is a Claude Code skill that advises on iOS visual hierarchy and screen layouts using Liquid Glass principles before implementation, without writing code.

MIT 224 installs ★ 359 updated 2026-09-26

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Prisma-Labs-Dev/apple-skills --skill ios-design-consultant -a claude-code
Open on GitHub

What ios-design-consultant does

This skill acts as an interface reviewer for iOS applications, guiding developers through layout choices before implementation starts. It checks element placement against Apple Human Interface Guidelines and the Liquid Glass visual language, aiming for polish that fits Apple Design Award standards.

The underlying decision model strictly separates layers: navigation items and controls live on the glass surface, while app data stays underneath. The assistant assesses task flows to pick between modal sheets and full-screen presentations, flagging anti-patterns such as colored glass layers or crowded tab bars.

Guidance focuses entirely on layout theory and design principles, so the skill deliberately omits executable UI code.

What it helps with

  • Decide proper placement for action buttons and toolbar controls
  • Choose between a modal sheet detent and full-screen navigation
  • Verify layout compliance with Human Interface Guidelines
  • Eliminate visual clutter caused by excessive glass materials

Example prompts for the agent

  • Where should I place the primary save action on my profile editing screen?
  • Should this account settings menu use a modal sheet or navigate full screen?
  • Are three floating action buttons too much glass for a single content view?

How to install ios-design-consultant

1Skills CLI (Vercel)

npx skills add Prisma-Labs-Dev/apple-skills --skill ios-design-consultant -a claude-code

2Manually: put the files in place

~/.claude/skills/ios-design-consultant/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ios-design-consultant/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ios-design-consultant

How to install ios-design-consultant in Claude Code?

Run npx skills add Prisma-Labs-Dev/apple-skills --skill ios-design-consultant -a claude-code in your terminal.

What does ios-design-consultant do?

It advises on visual hierarchy, navigation structures, and interface decisions following Apple platform rules.

Does this skill output SwiftUI code?

No, it delivers UX rationale and design advice; for actual Swift implementation, it suggests using /ios-ui-craft or /ios-liquid-glass.

Source text

SKILL.md · MIT
---
name: ios-design-consultant
user-invocable: true
description: 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.
---

# 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

1. **Answer the design question directly** — Give a clear recommendation
2. **Explain the rationale** — Why this choice aligns with Apple guidelines
3. **Reference the principle** — Which HIG/Liquid Glass concept applies
4. **Offer alternatives** — When multiple valid approaches exist
5. **Flag anti-patterns** — If their current approach has issues

## Decision Framework

When consulted on design decisions:

### Positioning Decisions
1. Is it a control or content? (Controls → glass layer, Content → beneath)
2. What's its importance? (Primary → prominent position)
3. What's the user's task flow? (Match the natural reading order)
4. Is it destructive? (Keep away from primary actions, require confirmation)

### Glass Decisions
1. Is it navigation or a control? → Use glass
2. Is it content? → Don't use glass
3. Does it float over media? → Use `.clear` glass
4. Is it a content container? → Use standard materials or nothing

### Color Decisions
1. Is it in the glass layer? → Use color sparingly (accent for primary actions only)
2. Is it in the content layer? → Express brand here
3. Is it a status indicator? → Color appropriate
4. Default → Keep monochromatic in glass

### Sheet vs Full-Screen
1. Quick task, same context? → Sheet
2. New context, deep navigation? → Full screen
3. Complex editing with hierarchy? → Full screen
4. Preferences/settings? → Usually sheet

## Required Reading

**Skill-specific docs (in this folder):**

- `docs/liquid-glass-philosophy.md` — Core vision and principles
- `docs/hig-layout.md` — Positioning, hierarchy, spacing, safe areas
- `docs/hig-materials.md` — Glass variants, when to use each
- `docs/hig-color.md` — Color strategy for Liquid Glass era
- `docs/positioning-guide.md` — Tab bars, toolbars, sheets, controls
- `docs/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:
1. Can any be consolidated into a toolbar?
2. Are they all needed simultaneously?
3. 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?":

1. **Delight**: Add surprise moments that reward exploration
2. **Innovation**: Use platform tech in unexpected ways
3. **Interaction**: Remove every ounce of friction
4. **Inclusivity**: Built for everyone from day one
5. **Impact**: Solve a real problem
6. **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-craft` skill or `/ios-liquid-glass` for 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."

© Prisma-Labs-Dev · MIT · Prisma-Labs-Dev/apple-skills

Similar skills

All skills for Design →

From the same set30

The whole set →
tipkit Apple TipKit API reference for Claude Code and coding agents. Helps configure contextual tips, the Tip protocol, and TipView. CX Codex +1 560installs guide-swift-concurrency guide-swift-concurrency guides AI agents through reviewing and writing concurrent Swift 6.2 code under strict concurrency checks. It flags actor reentrancy bugs, unsafe tasks, and GCD patterns. CX Codex +1 539installs guide-swiftdata guide-swiftdata — a skill for writing, reviewing and debugging SwiftData code: safe predicates, autosave rules and CloudKit constraints. CX Codex +1 538installs guide-swift-testing guide-swift-testing provides patterns and review rules for Swift Testing. Helps write and audit test suites targeting Swift 6.2 concurrency. CX Codex +1 534installs guide-swiftui-charts guide-swiftui-charts — a guide skill covering Swift Charts patterns: marks, axes, selection, styling, composition, Chart3D and accessibility. Useful when you build or rework charts in SwiftUI. CX Codex +1 533installs core-animation core-animation — a skill for Claude Code, Cursor, Codex, and other agents: a local QuartzCore reference covering CALayer, CAAnimation, CASpringAnimation, CATransaction, and around twenty more classes. CX Codex +1 508installs guide-swiftui-animations guide-swiftui-animations — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that supplies SwiftUI animation patterns to the agent. Activates when building animations, transitions, or motion in SwiftUI views. CX Codex +1 350installs ios-ui-craft ios-ui-craft builds production-grade SwiftUI screens and components aligned with Apple Design Award aesthetics and screenshot verification. CX Codex +1 184installs

Project sponsors

Companies that keep this analytics open