Prompt · Beginner

Prompt for a responsive business landing page

Generate an original, responsive one-page business site with honest content boundaries and a staged inspection checklist.

Author: Editorial team
Reviewer: Publication review pending
Review tier: 180-day

Version 1.0.0 · complete-websites

Variables

[BUSINESS_NAME] · Business name: The real public name of the business. Required.
[AUDIENCE] · Audience: The people the page should help. Required.
[PRIMARY_ACTION] · Primary action: The one honest action visitors should take. Required.

Expected output

Assumptions
File Tree
Html
Css
Optional Javascript
Audit

Common failures

Invented trust claims
Generic copy
Hidden mobile navigation

Compatible modes: Chat, Agent, Ide Assistant

Act as an experienced front-end developer and patient code reviewer.

Plan and build an original responsive landing page for [BUSINESS_NAME].
The audience is [AUDIENCE]. The primary action is “[PRIMARY_ACTION]”.

Before code, list missing facts, assumptions, the content hierarchy, reusable
components, and the file tree. Use semantic HTML, mobile-first CSS, and minimal
vanilla JavaScript only when native HTML cannot provide the behavior.

Include a concise header, hero, services or features, proof supplied by me,
about context, an honest action section, and footer. Do not invent business
facts, testimonials, ratings, awards, addresses, prices, or guarantees.

Meet WCAG 2.2 AA fundamentals, visible keyboard focus, reduced motion, and
reflow at 320px and 200% zoom. Keep navigation and essential content usable
without JavaScript. Use no framework, tracking script, icon package, or
external form service.

Return separate HTML and CSS files, any justified JavaScript, an assumptions
list, and a self-review covering semantics, keyboard behavior, responsive
layout, performance, crawlability, privacy, and maintainability.

What it builds

A focused landing page for a real business. The prompt forbids invented experience, ratings, addresses, testimonials, urgency, and working-form claims.

Complete prompt

Act as an experienced front-end developer and patient code reviewer.

Plan and build an original responsive landing page for [BUSINESS_NAME].
The audience is [AUDIENCE]. The primary action is “[PRIMARY_ACTION]”.

Before code, list missing facts, assumptions, the content hierarchy, reusable
components, and the file tree. Use semantic HTML, mobile-first CSS, and minimal
vanilla JavaScript only when native HTML cannot provide the behavior.

Include a concise header, hero, services or features, proof supplied by me,
about context, an honest action section, and footer. Do not invent business
facts, testimonials, ratings, awards, addresses, prices, or guarantees.

Meet WCAG 2.2 AA fundamentals, visible keyboard focus, reduced motion, and
reflow at 320px and 200% zoom. Keep navigation and essential content usable
without JavaScript. Use no framework, tracking script, icon package, or
external form service.

Return separate HTML and CSS files, any justified JavaScript, an assumptions
list, and a self-review covering semantics, keyboard behavior, responsive
layout, performance, crawlability, privacy, and maintainability.

Common AI mistakes

Look for invented social proof, an oversized decorative hero, button-styled links with unclear destinations, and a form that claims to send without an endpoint.

Verification checklist

Confirm every fact, tab through the page, test narrow and zoomed layouts, disable scripts, and inspect the final file tree for unnecessary dependencies.

Follow-up prompts

Ask the assistant to audit only the responsive behavior, then only the semantic outline. Require corrected files rather than a vague score.