Menu
Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | browser-screenshot-diff |
| description | Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification |
| argument-hint | <session-id-a> <session-id-b> [--threshold <0..1>] [--mode pixel|dom|both] |
| allowed-tools | mcp__claude-flow__browser_eval Bash Read Write |
Compare two recorded sessions step-by-step. Pairs each step in session A to the same step-id in session B, diffs the captured screenshot and accessibility snapshot, reports the first divergence and an aggregate similarity score.
browser-replay run matches the parent session within tolerance.npx -y ruvector@0.2.25 rvf status <session-id-a>.rvf
npx -y ruvector@0.2.25 rvf status <session-id-b>.rvf
trajectory.ndjson. Build a step-id → (screenshot_path, snapshot_path) map for each.step-id. Steps that exist on only one side are flagged as unmatched and contribute to the divergence score.--mode pixel|both): compare the two PNGs at each step. Report mse, psnr, and the bounding box of the largest diff cluster. Threshold default 0.02 (2% of pixels).--mode dom|both): compare the accessibility snapshots node-by-node. Report added / removed / changed nodes with their accessible names.findings.md under a fresh RVF container so the diff itself is replayable.browser-sessions under both source ids' tags so future searches surface "ran a diff against session X".browser_screenshot_diff MCP tool is not planned (ADR-0001 §7); the skill operates against locally-saved RVF artifacts and uses browser_eval only for live verification.Run one tick of the sales business-pod (ADR-164 §4.1, Phase 2). Loads templates/sales.json, validates it against the pod-schema, resolves agents against ruflo's agent registry, reserves budget via the Phase-2 file-based stub ledger (atomic SQLite tracker is Phase 3 per ADR-164.1), constructs per-agent dry-run prompts, posts a summary envelope to room "sales" via the federation_bbs_publish JSONL backing store, and emits a structured {podName, tickId, agentsRan, totalUsd, envelopeId, status} line for /loop ingestion. Dry-run by default; --live is reserved for Phase 3.
Run full security scans on the codebase using Ruflo security tools. Use when reviewing PRs for security regressions, auditing auth/input-handling code, before production deploys, or when the user asks for a security check at quick/standard/deep depth.
Initialize a multi-agent swarm with anti-drift configuration. Use when starting a complex multi-file task that needs 3+ coordinated agents (feature implementation, refactor across modules, security audit). Skip for single-file edits or quick questions.
Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement
Scaffold a new Claude Code plugin with proper directory structure, plugin.json, skills, commands, and agents
Scan project dependencies for known vulnerabilities and CVEs. Use when auditing third-party packages, before releases, after `npm install`/lockfile changes, or when investigating reported CVE advisories.