Claude prompt for a website

I want you to design and build a complete, responsive website for [BUSINESS OR PROJECT]. Its primary visitor is [TARGET AUDIENCE], and the main action I want them to take is [PRIMARY CONVERSION].

Site requirements:
- Pages or sections: [REQUIRED PAGES OR SECTIONS].
- Brand direction: [BRAND AND VISUAL DIRECTION].
- Technical constraints: [TECH STACK AND CONSTRAINTS].
- Use only facts, copy, offers, and links I provide. If content is missing, use clearly marked placeholders rather than inventing testimonials, metrics, client logos, prices, legal claims, or integrations.

First, give me a compact build plan: page hierarchy, conversion path, content needed, components, data/state needs, and assumptions. Then produce the implementation.

Output requirements:
1. Provide a file tree, followed by complete code for every file needed to run the site.
2. Use semantic HTML, visible keyboard focus, labeled form fields, sufficient color contrast, descriptive image alt text, responsive layouts from 320px upward, and respect prefers-reduced-motion.
3. Include loading, empty, validation-error, success, and failure states for every interactive element. Forms must prevent duplicate submission and explain what happens when submission cannot be completed.
4. Keep copy scannable: a specific value proposition near the top, proof only where supplied, and one primary call to action per page.
5. Include setup and run instructions, then explain the architecture and the three most useful places to customize.

Before answering, check that every import, route, asset reference, and interaction is accounted for. Also check that the primary conversion remains usable on mobile, with JavaScript disabled where feasible.

Ask up to 3 clarifying questions only if a required input is missing; otherwise make clearly labeled, reasonable implementation assumptions.

Create a responsive single-page landing page for [OFFER] aimed at [AUDIENCE]. The sole conversion is [CTA]. Use this proof only: [APPROVED PROOF]. Produce a section outline, then complete runnable [TECH STACK] code. Include a focused hero, problem-to-outcome framing, how it works, approved proof, objections, and CTA. Do not invent metrics, testimonials, or urgency. Add accessible form behavior with validation, loading, success, and error states. Check mobile readability and that every CTA leads to the same intended action before answering.

Plan the content for a website for [BUSINESS] serving [AUDIENCE] who need [PROBLEM SOLVED]. The conversion goal is [CTA]. Based only on [SOURCE MATERIAL], produce a page map and a copy brief for each page: visitor intent, headline, essential sections, proof needed, objections, and CTA. Identify missing facts that block credible copy. Do not write fictional customer outcomes or claims. Check that each page has a distinct job and that the conversion path has no unnecessary detours. Ask up to 3 questions only if a required input is absent.

Audit this [WEBSITE CODE OR URL] for a site whose primary visitor is [AUDIENCE] and primary conversion is [CTA]. Evaluate mobile layout, keyboard navigation, semantic structure, form validation, performance risks, broken states, copy hierarchy, privacy-sensitive data handling, and conversion friction. Return findings grouped by critical, important, and polish; for each, cite the affected file or page, explain the user impact, and give a specific fix. Do not assume functionality that is not present. Check that recommendations do not conflict with [TECH CONSTRAINTS].