
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
Pre-submission compliance scanner for Apple App Store. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, Expo) to identify potential App Store rejection risks before submission. Triggers on tasks involving app review preparation, compliance checking, App Store submission readiness, or when a user asks about App Store guidelines.
MCP dev-first mobile loop for reliable screenshot-observe-action execution, grounded interactions, and conversion of successful exploratory paths into tests.
Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessions.
Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
Analyze failed Revyl test, workflow, and device-session reports via CLI to classify real bugs, flaky tests, infra issues, setup failures, or test-design improvements.
Flutter leaf recipe for test-only auth bypass deep links using Revyl launch variables.
Set up test-only auth bypass for Revyl runs across Expo, React Native, native iOS, native Android, and Flutter apps.
Native Android leaf recipe for test-only auth bypass deep links using Revyl launch intent extras.
Generic CLI-first Revyl dev loop for hot reload, rebuild-loop, and device exploration.
Expo and Expo Router leaf recipe for test-only auth bypass deep links using Revyl launch variables.
React Native bare leaf recipe for test-only auth bypass deep links using Revyl launch variables.
Base CLI skill for Revyl command-driven workflows. Use when users want shell-command setup, execution, test authoring, or run triage without MCP tool calls.
Native iOS leaf recipe for test-only auth bypass deep links using Revyl launch arguments.
Base MCP skill for Revyl tool-call orchestration. Use when users want direct MCP execution instead of shell commands.
Analyze failed Revyl MCP test executions and classify them as real bugs, flaky tests, infra issues, or test-design improvements.