iOS Marketing Capture

Install

npx skillfoxx add skills/ios-marketing-capture

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a claude-code -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a cursor -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a github-copilot -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a codex -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a gemini-cli -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a cline -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a roo -y

npx skills add parthjadhav/ios-marketing-capture --skill ios-marketing-capture -a opencode -y

npx skills add ParthJadhav/ios-marketing-capture

This is third-party code. Review the repository files before installing.

What it does

The skill walks the agent through building a marketing screenshot capture system inside a SwiftUI app itself, without a separate UI test target. It adds a DEBUG-gated capture file to the main target, seeds demo data so screens look populated, and a step-based coordinator visits each screen and snapshots the full window including the status bar and presented sheets. Isolated components such as cards, widgets and charts are rendered through ImageRenderer at 3x scale with transparency around the rounded corners. A script builds the app once and relaunches it per locale via AppleLanguages arguments, sorting the PNGs into per-locale folders. Guidance for eleven real capture bugs found during development is baked in, so the agent avoids them on its own.

Who it is for. For SwiftUI iOS developers and indie authors who need App Store screenshots of their app in several languages.

Example request

Capture marketing screenshots of my app across all locales and render the cards and widgets as separate PNGs

Limitations

The skill targets SwiftUI and needs Xcode 16+, an iOS 17+ deployment target for ImageRenderer and @Observable, and a simulator matching your iOS version; the script uses Python 3 for JSON parsing. It adds DEBUG-gated capture code to your main target and edits a few files such as ContentView. It is the capture step: composing App Store pages with device frames and headlines is the author's separate skill.

How to disable. Remove the skill directory from ~/.claude/skills/ios-marketing-capture or the project's .claude/skills. Delete the added MarketingCapture.swift and the target edits by hand; they are DEBUG-gated and never ship to production.

Security check

• Adds code to your main target and edits some project files
• Runs Xcode builds and simulator commands on your machine

README in short

The README describes an AI agent skill that automates marketing screenshot capture for a SwiftUI app. The approach is in-app: capture runs from the app itself under a DEBUG flag, with no UI test target, seeding demo data, walking screens through a coordinator and rendering isolated elements via ImageRenderer. Install via npx skills or by cloning into the skills directory; the skill then triggers on request and asks about screens, elements, locales, device and data. It gives example prompts, the generated file layout, the per-locale output structure and a table of eleven common capture bugs. It needs Xcode 16+, iOS 17+ and Python 3, under the MIT license.

SKILL.md

---
name: ios-marketing-capture
description: Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget renders, App Store assets, fastlane-alternative, simctl screenshots.
---

# iOS Marketing Capture

## Overview

Automate reproducible marketing screenshot capture for a SwiftUI iOS app across multiple locales, with two parallel output streams:

1. Full-screen captures — every marketing-relevant screen, with deterministic seeded data, real status bar / safe-area chrome
2. Element captures — isolated renders of specific components (cards, widgets, charts) at any scale, with natural background inside rounded corners and transparency outside

This skill is the capture step. If the user also wants Apple-style marketing pages composited around the shots (device mockups, headlines, gradients), combine with the app-store-screenshots skill as a post-processing step.

## Core Approach

In-app capture mode, not XCUITest. This is a hard decision that trades off against Fastlane snapshot / XCUITest conventions, and it wins for almost every real project.

Related