developing-ios-apps

Develops iOS/macOS apps with XcodeGen, SwiftUI, and SPM, including Apple Developer signing, notarization, and CI/CD pipelines. Use when building iOS/macOS apps, fixing Xcode build failures, deploying to real devices, or configuring CI/CD signing. Triggers on XcodeGen project.yml, SPM dependency issues, code signing errors (Error -25294, keychain mismatch, adhoc fallback, EMFILE, notarization credential conflict), "Library not loaded @rpath", Electron @electron/osx-sign / @electron/notarize, notarytool, or certificate/provisioning problems.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a strong, highly actionable iOS/macOS development reference with excellent progressive disclosure via verified bundle files. Its main weakness is redundancy between the Critical Warnings table and the detailed later sections, plus a few destructive commands that could use explicit validation steps.

Suggestions

Dedupe the Critical Warnings table against the SPM and Code Signing sections: keep the table as a quick index with anchor links instead of restating the EMFILE, teamId, adhoc-fallback, and @rpath details in two places.

Add an explicit validation or rollback step for destructive commands, e.g. verify `pkill -9 Xcode` succeeded and confirm the DerivedData path before `rm -rf`, and note how to undo the global git proxy setting.

Consider moving the large osxSign TypeScript block and the full code-signing secrets tables into references/apple-codesign-notarize.md (already linked) to tighten the SKILL.md overview further.

Dimension	Reasoning	Score
Conciseness	The body is well-structured with tables and code, but several issues are stated twice — the @rpath, EMFILE, teamId, and adhoc-fallback items appear both in the Critical Warnings table and again verbatim in the SPM and Code Signing sections — which is more than minor trimming.	3 / 5
Actionability	Copy-paste-ready project.yml, concrete xcodebuild/security/codesign commands, and WRONG-vs-CORRECT Swift patterns directly cover the common cases with executable guidance.	5 / 5
Workflow Clarity	Key fragile workflows have explicit checkpoints (the 5-step signing checklist, fail-fast three-layer defense, 'Verify signing' command, numbered SPM embed fix), but a few destructive commands such as `pkill -9 Xcode && rm -rf DerivedData` and global git proxy config lack explicit validation or rollback guidance.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep links to five real reference files (all verified present), each labeled both inline and in a Resources section, with no nested references.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete capabilities, gives explicit 'Use when' and 'Triggers on' guidance, and uses highly distinctive error-string and tool-name triggers that a user would naturally encounter. It uses correct third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Names the domain and a comprehensive set of concrete capabilities — 'Develops iOS/macOS apps with XcodeGen, SwiftUI, and SPM, including Apple Developer signing, notarization, and CI/CD pipelines' — with multiple specific actions rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both 'what' (develops/signs/notarizes iOS/macOS apps with the named toolchain) and 'when' via an explicit 'Use when...' clause plus a 'Triggers on...' enumeration with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including user-facing phrases ('Xcode build failures', 'deploying to real devices'), specific error strings ('Library not loaded @rpath', 'Error -25294'), and tool names (notarytool, @electron/osx-sign).	5 / 5
Distinctiveness Conflict Risk	A clear iOS/macOS XcodeGen niche with distinctive triggers (specific error codes, Electron signing tools, notarytool) makes conflict with unrelated skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: daymade/claude-code-skills
Path: iOS-APP-developer/SKILL.md
Commit: b8556f2

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.