ios-polish

Apply a structured polish pass to iOS/SwiftUI views for HIG compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill ios-polish-elvinouyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-polish
Source: https://github.com/ElvinOuyang/claude-skill-collection/tree/main/plugins/ios-dev-toolkit/skills/ios-polish
Command: npx skills add https://github.com/ElvinOuyang/claude-skill-collection --skill ios-polish-elvinouyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill fixes the “looks off” quality gaps in iOS/SwiftUI interfaces so your screens feel crafted, not merely functional.

Core Features & Use Cases

  • Systematic iOS UI polish across spacing, typography, color, hierarchy, motion, iconography, and interaction feedback.
  • Native UX validation via the “Squint Test” and “Native Test” to catch web-like UI patterns and broken visual hierarchy.
  • Production readiness improvements including empty/loading/error states and platform-convention (HIG) compliance.

Quick Start

Run a final polish pass on iOS/SwiftUI screen code you’re about to ship and focus on spacing, typography, color semantics, accessibility, and HIG compliance.

Frequently Asked Questions about ios-polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I polish a SwiftUI view to feel Apple-quality before shipping?

Polishing a SwiftUI view involves a structured pass over spacing, typography, color hierarchy, motion, and interactions. Apply Dynamic Type text styles, tinted neutrals for dark mode, spring-based motion with Reduce Motion handling, and 44x44pt touch targets with accessibility labels.

Why does my iOS screen look off even though the functionality works?

Your iOS screen likely looks off due to web-like UI patterns and broken visual hierarchy. A native UX validation using the Squint Test catches these gaps, targeting missing empty, loading, and error states required for complete HIG compliance.

What's the best way to ensure my SwiftUI app supports Dynamic Type and dark mode?

The best way to ensure Dynamic Type and dark mode support is applying semantic iOS conventions. Use Dynamic Type text styles for typography and tinted neutrals for color semantics, guaranteeing proper rendering and accessibility across system appearance settings.

Can I use this to fix missing empty, loading, and error states in my SwiftUI app?

Yes, you can fix missing empty, loading, and error states during production readiness improvements. This enforces complete platform-convention HIG state coverage across your SwiftUI screens, ensuring all user interface states are properly handled.

Does iOS UI polish require adding accessibility labels and Reduce Motion handling?

Yes, iOS UI polish requires adding accessibility labels and Reduce Motion handling. You must implement 44x44pt touch targets with accessibility labels and spring-based motion that properly responds to the Reduce Motion accessibility setting.