mcpbeat

Ios Development

rshankras/ios-development

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.

112k tokens
context cost
the whole folder, loaded on every use
38
files
instructions only
0
copies elsewhere
how many repositories repackaged it
585
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/rshankras/claude-code-apple-skills --skill ios-development

The instruction itself

12 sections, as written by the author

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

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 it back
  • Drive navigation / deep links to reach the changed screen

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

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

Example Workflow

User asks for UI review:

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

How to use it

Copy the folder

Take rshankras/ios-development from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.