메뉴
Everything needed to submit your app to TestFlight and the App Store. Covers bundle ID, icons, screenshots, metadata, TestFlight distribution, and App Store submission. Use this skill when your app passes device testing and you're ready to ship. This is the final phase.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage Claude Code context windows, resume work across sessions, and maintain continuity when your Mac restarts or sessions expire. Use this skill when starting a new session on an existing project, when context feels stale, or when Claude Code starts making mistakes it shouldn't. Prevents the "Claude forgot everything" problem.
Safe patterns for Claude Code interacting with Xcode projects. Covers .pbxproj protection (critical), XcodeBuildMCP build/test patterns, the RenderPreview visual feedback loop, and when to use terminal Claude Code vs Xcode's built-in Claude Agent. Use this skill throughout the entire build process. The .pbxproj rule alone prevents hours of wasted debugging.
Git conventions for parallel Claude Code workstreams in Conductor. Covers branching strategy, merge order, conflict prevention, shared file protection, and the checkpoint pattern. Use this skill throughout the build phase, especially when running multiple Conductor workspaces. Prevents the merge conflicts and corrupted state that kill momentum.
Test every screen in BOTH light and dark mode every iteration. The most common iOS legibility bugs only show in one mode, including a specific class of vibrancy-on-pastel-tint failures that produce illegible labels on glass buttons. Use this skill alongside polish-and-refinement during the polish phase, and as a checklist any time you change colors, tints, or glass surfaces.
How strokes, anti-aliasing, and pixel boundaries actually behave in SwiftUI Canvas and Shape rendering. Covers stroke centering, inset-vs-outset, anti-alias-induced flicker on animating strokes, and 1pt vs 0.5pt strokes on retina displays. Use this skill for any app that draws on a grid or canvas — pattern designers, illustration tools, charting, finger-paint, whiteboards, image editors, gauge / dial UIs.
How to actually prove a UI change works before claiming it does. Covers AX-coordinate snapshots over screenshots, tap-by-label over coordinates, simulator state resets between iterations, and the build → screenshot → AX → math-check loop. Use this skill alongside testing-strategy whenever you're verifying a UI fix on simulator. Required reading before claiming any visual fix is "done."
| name | app-store-prep |
| description | Everything needed to submit your app to TestFlight and the App Store. Covers bundle ID, icons, screenshots, metadata, TestFlight distribution, and App Store submission. Use this skill when your app passes device testing and you're ready to ship. This is the final phase. |
Your app works. It's tested. Now ship it.
Tell Claude Code:
Configure the Xcode project for release:
- Bundle identifier: com.[yourname].[appname]
- Display name: [App Name]
- Version: 1.0.0
- Build: 1
- Deployment target: iOS [version]
- Supported orientations: Portrait (or specify)
- Supported devices: iPhone (or iPhone + iPad)
- Add the app icon to Assets.xcassets/AppIcon
- Ensure all required Info.plist entries are present
You need a single 1024x1024px PNG (no transparency, no rounded corners, the system adds those). Design this in Figma or your preferred tool.
Tell Claude Code:
Add the app icon from [path or describe where it is].
Verify it's configured correctly in the asset catalog.
If your app uses any of these, you need usage description strings:
Tell Claude Code:
Add the following privacy usage descriptions to Info.plist:
- [List only the ones your app actually uses]
Use clear, user-friendly language that explains why the app needs access.
In Xcode:
Tell Claude to help you draft these:
Write App Store metadata for [App Name]:
- Subtitle (30 characters max): catchy one-liner
- Description (4000 characters max): what the app does,
key features, who it's for
- Keywords (100 characters max, comma-separated):
search terms people would use to find this app
- What's New (for updates): brief changelog
- Category: [primary] and [secondary]
- Content Rating: fill out the questionnaire honestly
You need screenshots from:
Fastest method: Run the app in the simulator at each required size. Take screenshots with Cmd+S. No fancy frames needed for v1.
Better method: Take simulator screenshots, then use a tool to add device frames and marketing text. This can be done in Figma.
You need 3-10 screenshots per device size. Show:
Required even for free apps with no data collection.
Help me draft a simple privacy policy for [App Name].
The app [does / does not] collect user data.
The app [does / does not] use analytics.
Data is stored [locally on device only / in iCloud].
Host this on a simple webpage (GitHub Pages, Notion public page, or your personal site). You need the URL for App Store Connect.
In App Store Connect:
| Temptation | Why It Fails |
|---|---|
| Skipping TestFlight and going straight to App Store | You miss real-world testing with actual users |
| Using placeholder screenshots | Apple will reject you |
| Writing a novel for the description | Nobody reads it. Be concise |
| Submitting with known bugs "to fix later" | Reviewers will find them and reject you |
| Forgetting the privacy policy | Instant rejection |
Ready to submit when:
2-3 hours for the full submission process (configuration, screenshots, metadata, upload). Plus 24-48 hours for Apple review.