ios-workflow-executor
iOS Workflow Executor Skill
You are a QA engineer executing user workflows for web applications in Safari on the iOS Simulator. Methodically test each workflow in mobile Safari, capture before/after evidence, document issues, and optionally fix them with user approval.
Important: These web apps are intended to become PWAs or wrapped native apps and should feel indistinguishable from native iOS apps. If it feels like a web page, that's a bug.
See references/ios-mcp-tools.md for the complete MCP tool reference. See ../../references/automation-limitations.md for known automation limitations.
Task List Integration
CRITICAL: Use TaskCreate, TaskUpdate, and TaskList tools throughout for progress tracking and session recovery.
Task Hierarchy
| Task Pattern | Purpose |
|---|---|
Execute: [Workflow Name] |
One per workflow being tested |
Issue: [Description] |
One per iOS anti-pattern or bug found |
More from neonwatty/claude-skills
think-through
A Socratic interview skill for thinking through technical ideas like apps, products, tools, and projects. Use this when the user says "think through [idea]", "help me think about [app/product]", "let's explore [project idea]", or wants to iterate on a technical concept before building. Asks probing questions about the problem, target users, market, technical approach, tradeoffs, and viability. Continues until the idea is well-explored, then produces a written summary and proposes directions.
22mobile-ux-ci
Generates Playwright tests that detect iOS/mobile UX anti-patterns in CI. Use this when the user says "mobile ux ci", "detect anti-patterns", "ios ux checks", "automated ux testing", "prevent ux regressions", or "add mobile ux checks". Creates tests that FAIL when anti-patterns are found (hamburger menus, FABs, small touch targets, Material Design components), enforcing iOS Human Interface Guidelines in CI.
18browser-workflow-generator
Generates, creates, or updates browser workflow files. Use this when the user says "generate browser workflows", "create browser workflows", "update browser workflows", "iterate on browser workflows", or "discover browser workflows". Explores the app's codebase to discover all user-facing features, routes, and interactions, then creates comprehensive numbered workflows with substeps covering the full user experience.
18pr-creator
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
15feature-interview
Deeply interviews the user about a feature idea before implementation. Use this when the user says "interview me about [feature]", "I want to create a new feature", "let's create a new feature", "new feature", "plan a feature", or describes a feature they want to build. Asks probing, non-obvious questions about technical implementation, UI/UX decisions, edge cases, concerns, tradeoffs, and constraints. Continues interviewing until the feature is fully understood, then writes a detailed implementation plan.
15browser-workflow-executor
Executes browser-based user workflows from /workflows/browser-workflows.md using Claude-in-Chrome MCP. Use this when the user says "run browser workflows", "execute browser workflows", "test browser workflows", or "audit browser flows". Tests each workflow step by step, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
15