VibeRPGSimulator

Reproduce a reported error

Hunter · Testing and debugging3 spells in orderProposed, not testedUnrated

Play the combo

Foe: Flaky Wisp, a failing or flaky test.

Foes

  • Flaky Wisp

Party · Context

  • HunterYour agent100/100

  1. Flaky Wisp

    The Flaky Wisp blocks the way.

    What really happensIt stands for a failing or flaky test.

    Hunter: Context 100/100.

  2. Flicker

    The Flaky Wisp uses Flicker.

    What really happensA flaky test passes on one run and fails on the next.

    Hunter takes 8. Hunter: Context 92/100.

  3. Sentry MCP

    An orb that pulls live Sentry issues into the fight.

    What really happensPulls the reported errors, traces and project context from Sentry.

    Flaky Wisp takes 33.

  4. Flicker

    The Flaky Wisp uses Flicker.

    Hunter takes 8. Hunter: Context 84/100.

  5. Superpowers Systematic Debugging

    A scroll that bars fixes until the hero has a root cause.

    What really happensGathers evidence and reproduces the failure to find the root cause before any fix.

    Flaky Wisp takes 33.

  6. Flicker

    The Flaky Wisp uses Flicker.

    Hunter takes 8. Hunter: Context 76/100.

  7. Microsoft Playwright MCP

    An orb that opens a live browser so the hero can click through your app.

    What really happensRuns the same browser flow again after the fix to confirm it works.

    Flaky Wisp takes 34. Flaky Wisp falls.

  8. Victory

    The Flaky Wisp falls.

    What really happensTie the reported errors to a browser flow you can repeat, find the root cause, then run the same flow again after the fix.

Cast order

  1. Sentry MCP

    Pulls the reported errors, traces and project context from Sentry.

  2. Superpowers Systematic Debugging

    Gathers evidence and reproduces the failure to find the root cause before any fix.

  3. Microsoft Playwright MCP

    Runs the same browser flow again after the fix to confirm it works.

Why it works

Tie the reported errors to a browser flow you can repeat, find the root cause, then run the same flow again after the fix.

Records

Seen together0sessions containing every step
In this order0sessions with matching first-use order
Test recoveries0 of 0sessions with a failing test

Curator's machine: macOS 27.0.1 · Apple Silicon (arm64), read when these stats were published. Harness versions installed then: Codex 0.154.0, Claude Code 2.1.282, OMP 18.8.3. Session logs do not record the OS.

Co-occurrence and order describe the logs; they do not show that this combo caused an outcome.

Learn the spells

  1. 1. Sentry MCP

    Claude Code

    claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}

    Codex

    codex mcp add sentry --url https://mcp.sentry.dev/mcp

  2. 2. Superpowers Systematic Debugging

    Claude Code

    /plugin install superpowers@claude-plugins-official

    Codex

    /plugins

  3. 3. Microsoft Playwright MCP

    Claude Code

    claude mcp add playwright npx @playwright/mcp@latest

    Codex

    codex mcp add playwright npx "@playwright/mcp@latest"