What Makes a Good Prompt

A great prompt on Webbin is one that someone else can pick up, use immediately, and get a consistently good result. Here's what that looks like in practice.

Be specific, not vague

Vague prompts produce unpredictable results. The more precisely you describe what you want — format, tone, length, constraints — the more reliably the prompt works.

Too vague:

Design a landing page for a SaaS product.

Better:

Design a landing page using a structured SaaS design system built around modular
cards and grid layouts. The goal is to create an interface that feels scalable,
professional, and product-focused rather than marketing-heavy. Use soft shadows,
subtle borders, and generous internal spacing. Typography should be modern and
neutral — emphasise hierarchy through weight and size, not decorative styles.
Avoid flashy effects or excessive colour. The result should feel like a
well-designed product system, similar to modern developer platforms and
enterprise interfaces.

Include output format instructions

Tell the model exactly how you want the output structured — bullet points, markdown, JSON, plain text, a specific length.

One job per prompt

Prompts that try to do too many things at once rarely work well. If you find yourself writing "and also...", consider splitting it into two prompts.

What gets rejected

• Prompts that are too generic to be useful
• Duplicates of prompts already in the library
• Anything harmful, deceptive, or that violates the guidelines
• Prompts with no clear use case or audience