ios_skill
- Swift
56
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill rshankras/claude-code-apple-skills --skill ios- SKILL.md2.3 KB
Overview
This skill reviews SwiftUI code for iOS and watchOS against Apple Human Interface Guidelines, font best practices, Dynamic Type support, and accessibility. It provides concrete findings, line-specific issues, and suggested code fixes to make interfaces more usable, accessible, and platform-appropriate. Use it to validate UI decisions and prioritize developer-facing fixes.
How this skill works
I scan specified SwiftUI view files (or ask you which to review) and compare implementations to HIG checklists, font guidelines, and accessibility rules. The review flags anti-patterns like hardcoded colors, fixed font sizes, missing accessibility labels, and inadequate tap targets, and it produces suggested fixes with short code examples. I prioritize user-facing views and list tests to validate changes on device and simulator.
When to use it
- When you ask for a UI review of SwiftUI views
- When you need HIG compliance verification for iOS or watchOS
- When you want an accessibility audit (VoiceOver, labels, traits)
- When you need font/Dynamic Type checks or typography guidance
- Before submitting a UI-focused app update or App Store review
Best practices
- Prefer semantic Color and system colors (Color(.systemBackground), .label)
- Use system font text styles (e.g., .headline, .body) to enable Dynamic Type
- Ensure tap targets meet platform minimums (44pt iOS, 40pt watchOS)
- Provide accessibilityLabel, accessibilityHint, and appropriate traits for controls
- Avoid fixed frames for text; test layouts at largest Dynamic Type sizes
Example use cases
- Review AddOrUpdateExpenseView.swift for missing tap targets and hardcoded colors
- Audit a watchOS complication view for contrast and legibility
- Check that custom fonts scale with Dynamic Type and fallback to system styles
- Validate navigation patterns and sheet presentations for iPad and watchOS
- Produce a prioritized fix list with code snippets and line references
FAQ
Provide the SwiftUI view files you want reviewed; if you don’t specify, I will ask which views to prioritize or scan recent UI files.
Will you run automated tests?
I analyze code and flag issues; I recommend specific runtime tests (VoiceOver, Dynamic Type, Dark Mode, Accessibility Inspector) to verify fixes on device or simulator.