Index of every page on this site: llms.txt
All skills
Run it yourself

Comprehensive iOS development guidance including Swift best practices, SwiftUI patterns, UI/UX review against HIG, and app planning. Use for iOS code review, best practices, accessibility audits, or planning new iOS apps.

  • 38 files
  • 442.3 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/ios

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈57 tokens for metadata: the name and description. ≈814 when used: this file. ≈112k more on demand in 37 files.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈239 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

iOS Development Expert

Comprehensive guidance for iOS app development. This skill aggregates specialized modules for different aspects of iOS development.

When This Skill Activates

Use this skill when the user:

  • Asks about iOS development best practices
  • Wants code review for iOS/Swift projects
  • Needs UI/UX review against Human Interface Guidelines
  • Wants accessibility audit for iOS apps
  • Is planning a new iOS app
  • Needs help with SwiftUI patterns for iOS
  • Asks about navigation architecture (NavigationStack, NavigationSplitView, TabView)
  • Wants to run/launch the app in the Simulator or screenshot it to verify a change

Available Modules

Read relevant module files based on the user's needs:

coding-best-practices/

Swift code quality and modern idioms for iOS.

  • Modern Swift patterns and idioms
  • Architecture patterns (MVVM, Clean Architecture)
  • Code quality standards
  • Performance optimization

ui-review/

UI/UX review against Apple HIG.

  • Human Interface Guidelines compliance
  • Font usage and Dynamic Type support
  • Accessibility review (VoiceOver, color contrast)
  • SwiftUI best practices for iOS/watchOS

accessibility-audit/

Structured accessibility audit workflow (advisory).

  • Automated XCUITest audits (performAccessibilityAudit) + CI patterns
  • Accessibility Inspector workflow
  • Manual VoiceOver / Voice Control / Dynamic Type passes per common task
  • App Store Accessibility Nutrition Label evaluation + declaration

navigation-patterns/

SwiftUI navigation architecture patterns.

  • NavigationStack, NavigationLink, navigationDestination
  • NavigationSplitView (two/three column, iPad/macOS)
  • TabView (iOS 18 customizable tabs, sidebar mode)
  • Programmatic navigation (NavigationPath, pop-to-root, state restoration)
  • Navigation transitions (zoom, custom animations)

app-planner/

iOS app planning and analysis.

  • New app concept to architecture
  • Existing app audits
  • Tech stack evaluation
  • Product planning guidance

run-simulator/

Build, install, launch, and screenshot the app in the Simulator to verify a change visually (operational — uses Bash, not just guidance).

  • Discover scheme + an available simulator (no hardcoded device names)
  • Build for the simulator and resolve the .app + bundle id
  • Boot, install, launch, then screenshot and read back a small thumbnail
  • Navigate to the changed screen via deep link or the AXe accessibility tree (tap by id / label / exact point) — never by guessing from screenshots

run-device/

Run an app on a physical iPhone/iPad from the CLI (no Xcode GUI).

  • Build + code-sign for a device with xcodebuild -allowProvisioningUpdates
  • Install and launch via devicectl
  • Screenshot on hardware via libimobiledevice
  • Device prerequisites (Developer Mode, pairing) and signing gotchas

How to Use

  1. Identify user's need from their question
  2. Read relevant module files from subdirectories
  3. Apply the guidance to their specific context
  4. Reference Apple HIG documentation when needed

Example Workflow

User asks for UI review:

  1. Read ui-review/SKILL.md for the full review process
  2. Check their SwiftUI code against HIG
  3. Verify accessibility compliance
  4. Report findings with specific recommendations

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago
What it can do
Reads files Network
last_verified
2026-07-16
review_by
2027-06-22
os_version
iOS 27 / macOS 27
All 4 allowed tools
ReadGlobGrepWebFetch

README badge

README badge for rshankras/claude-code-apple-skills/ios