Bad Vibes

Owner submission preview

Give testers one job. Make it count.

A good test brief is small enough to finish over coffee and specific enough to tell you what broke.

Preview only: this form stays in page memory. It does not submit, publish, upload, or save anything. Refreshing clears it.

First, make sure this belongs here.

You must own or control the app. The test path must be public, low stakes, and usable without payment, credentials, sensitive information, or consequential forms.

Read all rules

Nothing leaves this page

Build your test brief

01 The project

The name people will see on the project card. 60 characters maximum.

No login walls, payment steps, or private preview links.

Tell a curious stranger what it does in 140 characters or fewer.

For example: “Roommates who share groceries.”

Up to three comma-separated tools, such as Bolt, Supabase, Claude.

02 The test mission

Ask for one observable task, not “tell me what you think.” 240 characters maximum.

Name the visible end state so testers know whether they completed it.

How long should it take?

Keep the first mission short.

What can people use?

Choose at least one supported device.

What kind of feedback helps most?

Choose one or two. A narrower request gets better feedback.

A little context is helpful. A preemptive essay is not.

Ask one playful, specific question about the build, not the builder.

Roast level

Tone changes. The rule does not: roast the build, never the builder.

03 Permission and boundaries

All five are required before a future listing could be published.

There is no publish action in this prototype.