Stats
Actions
Tags
From soloflow
Runs standalone visual verification for mobile apps using Maestro (MCP/CLI fallback) and web apps using Playwright MCP on specified screen or feature.
How this command is triggered — by the user, by Claude, or both
Slash command
/soloflow:verify <screen or feature to verify>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /soloflow:verify You are running standalone visual verification. The user wants to visually check a screen or feature without running the full workflow. The target to verify is: **$ARGUMENTS** ## Step 0: Check initialization If `.soloflow/` does not exist, report: "SoloFlow not initialized. Run `/soloflow:init` first." and stop. ## Step 1: Check Availability Pick a mobile path **once** per the **Path Selection** recipe in `skills/visual-verify/SKILL.md`, then probe web. **For mobile verification (MCP preferred, CLI fallback):** 1. **Probe MCP.** Call `mcp__maestro__list_devices`. I...
You are running standalone visual verification. The user wants to visually check a screen or feature without running the full workflow.
The target to verify is: $ARGUMENTS
If .soloflow/ does not exist, report: "SoloFlow not initialized. Run /soloflow:init first." and stop.
Pick a mobile path once per the Path Selection recipe in skills/visual-verify/SKILL.md, then probe web.
For mobile verification (MCP preferred, CLI fallback):
mcp__maestro__list_devices. If it returns a result, set USE_MAESTRO_MCP=true. If the tool is unbound or the call errors, continue.which maestro via Bash. If not found AND MCP probe failed, report: "Maestro is not available via MCP or CLI. Install the CLI with: curl -Ls 'https://get.maestro.mobile.dev' | bash, or register the MCP server with: claude mcp add --scope user maestro maestro mcp."IOS=$(xcrun simctl list devices booted 2>/dev/null | grep -c Booted || true)
AND=$(adb devices 2>/dev/null | awk '$2=="device"' | wc -l | tr -d ' ' || true)
open -a Simulator (iOS) or emulator -avd <name> (Android)." (MCP's start_device can also boot one for you if you prefer — but the user likely wants an explicit choice.)For web verification:
which npx via Bash.If neither mobile nor web tooling is available, report this to the user and stop.
maestro/, .maestro/, test/maestro/ that match the targetStay on the path chosen in Step 1. See skills/visual-verify/SKILL.md for exact tool signatures and command patterns.
MCP path:
mcp__maestro__run_flow_files(device_id, flow_files=[<path>]) and report the per-step results.launchApp + tapOn / inputText) and call mcp__maestro__run_flow(device_id, flow_yaml=<body>).mcp__maestro__inspect_view_hierarchy(device_id) to check element presence and layout (CSV, ~50 tokens).mcp__maestro__take_screenshot(device_id) only if visual appearance needs checking (limit to 3).CLI path:
maestro test <flow.yaml> via Bash and report the exit code + any failing-step output.appId from verification.visual_mobile_app_id or existing flows.launchApp + tapOn / inputText) to /tmp/sf-maestro-*.yaml, run maestro test, remove the file.maestro hierarchy to check element presence and layout (~200–600 tokens plain text).sips -Z 1400, limit to 3):
xcrun simctl io booted screenshot <path>adb exec-out screencap -p > <path>If relevant to the target:
Output a visual verification report:
## Visual Verification Report
- **Target:** {what was verified}
- **Method:** Maestro | Playwright | Both
### Results
- {check 1}: PASS | FAIL — {evidence}
- {check 2}: PASS | FAIL — {evidence}
### Screenshots
- {description of each screenshot taken, if any}
### Issues Found
- {any problems discovered, or "None"}
npx claudepluginhub kesteva/soloflow --plugin soloflow-dev/verifyPerforms visual verification of UI changes by taking Playwright screenshots of a target URL or component, then reports differences and displays screenshots.
/f5-test-e2eRuns end-to-end and visual regression tests with Playwright via subcommands like journey, critical, page, smoke, visual. Produces step-by-step reports with assertions, screenshots, and videos.
/test-web-uiRuns automated web UI testing: visual snapshots, functional flows, accessibility audits (WCAG), and performance analysis (Lighthouse/Core Web Vitals) on app URL/path.
/testuifExecutes intelligent regression testing between Flask and React V2 frontends using Playwright MCP, generating matrix reports, screenshots, and PR documentation.
/verifyVerifies frontend changes against acceptance criteria using browser agents to check UI and functionality compliance.
/maestro-testgenGenerates UI regression tests from natural language or git diff, creates manual test cases and executable Maestro YAML flows, runs them on an online device, and produces HTML reports with screenshots.