asc-shots-pipeline

Automate iOS screenshot pipelines across simulators with Xcode, AXe, and framing.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-shots-pipeline-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-shots-pipeline
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-shots-pipeline
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-shots-pipeline-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex, multi-step process of capturing, framing, and uploading iOS screenshots across simulators using Xcode CLI tools, AXe, and the Go-based framing pipeline to ensure consistent results.

Core Features & Use Cases

  • Automate the full screenshot workflow: build/run on a simulator, drive the UI with AXe, frame images, and optionally upload results.
  • Support plan- and settings-driven capture with JSON configuration, device discovery, and deterministic framing.
  • Use cases include creating screenshot pipelines for multiple locales, per-device framing, and batch uploads from framed outputs.

Quick Start

Configure your project with a settings JSON, then run the sequence to build, capture, frame, and optionally upload screenshots.

Frequently Asked Questions about asc-shots-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the iOS screenshot pipeline from capture to upload?

You can automate the iOS screenshot pipeline by coordinating Xcode build/run, AXe UI actions, multi-device framing, and batch uploads across locales using JSON configuration and simulator-based workflows.

What is the best way to frame iOS simulator screenshots for multiple locales?

Framing iOS simulator screenshots is handled through a Go-based framing pipeline that supports plan-driven capture, multi-device framing, and deterministic outputs across multiple locales.

Can I use Xcode CLI tools to drive simulator UI actions for screenshot capture?

Yes, Xcode CLI tools are used to build and run the app on a simulator, while AXe drives the UI actions to capture screenshots in a plan-driven, automated workflow.

How does plan-driven screenshot capture work with AXe and JSON configuration?

Plan-driven capture works by using a JSON settings file to configure device discovery and UI actions, allowing AXe to deterministically execute capture sequences across simulators.

Do I need YAML frontmatter to automate batch screenshot uploads across locales?

Yes, YAML frontmatter is a strict requirement for the automation pipeline to process and execute batch uploads of framed screenshots across different locales.

Are there limitations when using simulator-based workflows for iOS screenshot automation?

Simulator-based workflows depend on Xcode CLI and AXe, requiring optional dependencies and assets to be tracked for extensibility, which may limit physical device capture scenarios.