Prompts that
actually build.

A landing page for a family-run bakery in Ghent: hero with a photo-style background and the opening hours, a section with our five best breads and prices, customer quotes, a map placeholder and a contact form. Warm, rustic, cream and dark brown.

Why it works: Names the business, the sections in order and a palette — the three things a model otherwise invents.

A launch page for an app that turns voice notes into meeting summaries. Big headline, one-sentence explanation, an animated demo area, three benefits, an email waitlist form with a success message, and an FAQ. Dark mode, electric blue accent.

Why it works: One goal (the waitlist) and an explicit success state, so the form is not left dangling.

A SaaS analytics dashboard: left sidebar with Overview, Customers, Revenue and Settings. Overview shows four KPI cards, a 12-month revenue line chart and a table of recent signups with search and sorting. Use realistic sample data. Clean, neutral, compact.

Why it works: Realistic sample data makes every screen reviewable before a backend exists.

Add a Settings page with tabs for Profile, Notifications and Billing. Each tab has a form with validation, a Save button that is disabled until something changes, and a toast when saved.

Why it works: Describes behaviour (disabled until changed, toast on save), not just layout.

A webshop for handmade ceramics: product grid with filters for colour and price, product detail page with image gallery and quantity selector, a cart drawer that updates totals, and a checkout page with shipping form. Minimal, earthy tones.

Why it works: Lists the four screens every shop needs and the interactions on each.

An internal inventory tool: products with name, SKU, location and stock. Highlight anything under 10 in stock, allow add and edit in a side panel, filter by location, and export the current view to CSV.

Why it works: Specifies the fields and the rule (under 10) instead of "manage inventory".

An approval queue for expense requests: a list with requester, amount, category and status; managers can approve or reject with a comment; approved items move to a separate tab; show totals per month.

Why it works: States the roles and the state changes — the core of any workflow tool.

A portfolio for a product designer: a 3D animated hero, a grid of six projects that open into case-study pages with problem, process and outcome, an about section and a contact form. Use @aurora for the background.

Why it works: The @ reference pulls a ready-made effect from the Vantix library instead of improvising one.

When I click "Book" with an empty email field, the page goes blank. Expected: an inline error under the email field and the button stays enabled. Fix only this; do not change the layout.

Why it works: Symptom, expected behaviour and a boundary ("fix only this") — the three parts of a good bug report.

Make every page work at 375px wide: stack the columns, turn the sidebar into a bottom tab bar, keep buttons at least 44px tall, and make tables scroll horizontally instead of overflowing.

Why it works: Gives a width to test against and concrete rules, not "make it mobile friendly".

Keep the content but improve the design: a consistent 8px spacing scale, one accent colour, larger headings with tighter letter-spacing, and fewer borders. Do not add new sections.

Why it works: A design brief with constraints stops the model from redesigning everything.