ios-developer
Build Native iOS Apps With Swift
Native iOS development requires platform knowledge across UI, data, security, testing, and App Store release work. This skill gives Claude, Codex, and Claude Code focused guidance for Swift-first iOS implementation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ios-developer" from https://skillstore.io/skills/sickn33-ios-developer.md and its manifest at https://skillstore.io/api/skills/sickn33-ios-developer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ios-developer". Build a SwiftUI profile editor with local persistence.
Expected outcome:
A feature plan covering screens, view models, SwiftData storage, validation states, accessibility labels, unit tests, and UI test coverage.
Using "ios-developer". Migrate an old UIKit settings screen to SwiftUI.
Expected outcome:
A migration strategy with wrapper boundaries, navigation changes, state ownership, rollout steps, regression tests, and fallback handling.
Using "ios-developer". Prepare my app for TestFlight and App Store review.
Expected outcome:
A release checklist covering signing, build configuration, privacy labels, screenshots, crash reporting, beta feedback, metadata, and review guideline risks.
Security Audit
SafeThe static command-execution finding is a false positive caused by Markdown inline code around a resource path. The system reconnaissance finding is also a false positive because the cited line only describes UIKit integration capabilities. No prompt injection, data exfiltration intent, or unsafe operational behavior was found in SKILL.md.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-ios-developer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-ios-developer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-ios-developer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-ios-developer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-ios-developer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). ios-developer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-ios-developer/audits/4BibTeX citation
@techreport{sickn33-sickn33-ios-developer-2026,
author = {sickn33},
title = {ios-developer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-ios-developer/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ios-developer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-ios-developer/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-ios-developer:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create a SwiftUI Feature
Design a new iOS screen with state management, navigation, error handling, accessibility, and tests.
Modernize a Legacy Module
Plan a safe migration from UIKit or older Swift patterns toward SwiftUI, Combine, and modular architecture.
Prepare for App Store Release
Review privacy, performance, metadata, TestFlight, screenshots, and App Store review risks before submission.
Try These Prompts
Plan an iOS feature for [feature goal]. Use SwiftUI where appropriate. Include data flow, screens, accessibility, testing, and App Store concerns.
Review this iOS architecture: [paste summary]. Recommend SwiftUI state management, navigation, dependency injection, persistence, and test improvements.
Design a secure iOS API integration for [service]. Cover URLSession, Codable models, authentication storage, retries, offline behavior, privacy, and tests.
Audit this iOS release plan: [paste details]. Check performance, accessibility, privacy labels, App Store review risks, TestFlight, crash reporting, and rollback planning.
Best Practices
- Share the target iOS version, Xcode version, current architecture, and important dependencies before asking for implementation guidance.
- Ask for accessibility, privacy, error handling, and test coverage with every user-facing feature.
- Validate generated code against Apple documentation and project build settings before release.
Avoid
- Do not request broad rewrites without describing existing modules, risks, and release constraints.
- Do not store tokens, passwords, or personal data outside secure iOS storage mechanisms.
- Do not treat App Store or privacy guidance as legal approval without separate review.