• QUIET ENGINESstash
Browse
  • lLibrary Home
Library
  • pPrompts
    • sStack
    AboutPrivacyReport
    QE-0047-A·————-——-——T——:——:——
    Owner
    • QUIET ENGINESstash
    Browse
    • lLibrary Home
    Library
    • pPrompts
      • 1Counsel
      • 2Design
      • 3Dev
      • 4DJ
      • 5Image
      • 6Paper
      • 7PStack
      • 8suffixes
      • 9Worlds
      • Writing
    • sStack
    AboutPrivacyReport
    1. Library
    Authenticate. Currently visitorVisitorAuthenticate
    • QUIET ENGINESstash
    Browse
    • lLibrary Home
    Library
    • pPrompts
    AboutPrivacyReport
    1
    Counsel
  • 2Design
  • 3Dev
  • 4DJ
  • 5Image
  • 6Paper
  • 7PStack
  • 8suffixes
  • 9Worlds
  • Writing
  • sStack
  • Prompts

    Break-it lead: 5 parallel adversarial testers

    Updated Oct 25, 2026

    Act as my break-it lead. Start the app, then spin up 5 subagents in parallel, each trying to break it a different way:

    1. The chaos user: double clicks, the back button mid-checkout, refreshing during a save, 10 tabs open at once
    2. The weird input user: emoji names, 5,000-character fields, pasted spreadsheets, wrong formats, empty submits
    3. The slow user: a throttled network, timeouts, a flaky connection, a phone-size screen
    4. The sneaky user: other people's IDs in the URL, edited requests, skipped steps, expired links
    5. The first-timer: no instructions, wrong turns, gives up the moment something is confusing Each one logs every bug with exact steps to reproduce, what they expected, what happened, and a severity. Then merge everything into one list sorted by severity, fix the critical bugs, and re-run those tests to prove they're fixed.