Use this skill for agent-driven screenshot workflows where the app is built and launched with Xcode CLI tools, UI is driven with AXe, and screenshots are uploaded with asc.
Fetches asc-shots-pipeline from rudrankriyam/asc-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/asc-shots-pipeline
Restart Cursor to activate asc-shots-pipeline. Access via /asc-shots-pipeline in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Use this skill for agent-driven screenshot workflows where the app is built and launched with Xcode CLI tools, UI is driven with AXe, and screenshots are uploaded with asc.
Current scope
Implemented now: build/run, AXe plan capture, frame composition, and upload.
Device discovery is built-in via asc screenshots list-frame-devices.
Local screenshot automation commands are experimental in asc cli.
Framing is pinned to Koubou 0.18.1 for deterministic output.
Always confirm exact flags with --help before running commands.
Re-check command paths with asc screenshots --help because screenshot commands are evolving quickly.
Keep outputs deterministic: default to JSON for machine steps.
Prefer asc screenshots list-frame-devices --output json before selecting a frame device.
Ensure screenshot files exist before upload.
Use explicit long flags (--app, --output, --version-localization, etc.).
Treat screenshot-local automation as experimental and call it out in user-facing handoff notes.
If framing fails with a version error, re-install pinned Koubou: pip install koubou==0.18.1.
If framing fails because device frames are missing, run kou setup-frames once with network access.
6) Multi-locale capture (optional)
Do not use xcrun simctl launch ... -e AppleLanguages for localization.
-e is an environment variable pattern and does not reliably switch app language.
For this pipeline, use simulator-wide locale defaults per UDID. This works with
asc screenshots capture, which relaunches the app internally.
# Map each locale to a dedicated simulator UDID.# (Create these simulators once with `xcrun simctl create`.)declare-ALOCALE_UDID=(["en-US"]="UDID_EN_US"["de-DE"]="UDID_DE_DE"["fr-FR"]="UDID_FR_FR"["ja-JP"]="UDID_JA_JP")set_simulator_locale(){localUDID="$1"localLOCALE="$2"# e.g. de-DElocalLANG="${LOCALE%%-*}"# delocalAPPLE_LOCALE="${LOCALE/-/_}"# de_DE xcrun simctl boot "$UDID"||true xcrun simctl spawn "$UDID" defaults write NSGlobalDomain AppleLanguages -array"$LANG" xcrun simctl spawn "$UDID" defaults write NSGlobalDomain AppleLocale -string"$APPLE_LOCALE"}forLOCALEin"${!LOCALE_UDID[@]}";doUDID="${LOCALE_UDID[$LOCALE]}"echo"Capturing $LOCALE on $UDID..." set_simulator_locale "$UDID""$LOCALE" xcrun simctl terminate "$UDID""com.example.app"||true asc screenshots capture \ --bundle-id "com.example.app"\--name"home"\--udid"$UDID"\ --output-dir "./screenshots/raw/$LOCALE"\--output json
done
If you launch manually (outside asc screenshots capture), use app launch arguments:
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
