website
Build a Next.js marketing website from scratch
A structured prompt for generating a complete multi-section marketing website in Next.js, with responsive layout, accessibility and a clear file structure.
Who should use this
Is this prompt for you?
- Founders or freelancers who need a first working version of a marketing site
- Developers who want a well-organized Next.js starting point instead of a blank repo
- Anyone who has a product idea in mind but no existing design or component library
The prompt
Copy this prompt
Prompt
You are helping me build a marketing website using Next.js (App Router), TypeScript and Tailwind CSS. Context: - Product/company: [describe your product in 2-3 sentences] - Target audience: [who the site is for] - Primary goal of the site: [e.g. get sign-ups, book demos, sell a product] - Tone/style: [e.g. minimal and technical, warm and friendly, bold and playful] Build the following pages/sections as a single-page marketing site: 1. A header with logo placeholder, nav links (Home, Features, Pricing, FAQ, Contact) and a primary CTA button 2. A hero section with a headline, subheadline, primary + secondary CTA, and a placeholder for a product screenshot 3. A "logos" or social proof strip (use neutral placeholder text, not fake company names) 4. A features section with 3-6 feature cards (icon, title, 1-2 sentence description) 5. A "how it works" section with 3-4 numbered steps 6. A pricing section with 2-3 tiers (use realistic but clearly placeholder pricing) 7. An FAQ section with 5-6 questions using a native <details> accordion (no extra JS library) 8. A final call-to-action band 9. A footer with nav groups and legal links Requirements: - Use semantic HTML (header, nav, main, section, footer) and one <h1> on the page - Every image needs meaningful alt text; every interactive element must be keyboard accessible - Fully responsive: mobile-first, test the breakpoints you use (sm/md/lg) - Use CSS variables or a small design-tokens file for color and spacing, not hardcoded hex values scattered everywhere - Do not fabricate statistics, testimonials, or customer logos — use clearly labeled placeholder content I can replace - After generating the code, explain the file structure you created and why you split components the way you did - List any follow-up decisions I need to make (real copy, real images, analytics, domain, deployment)
Works well with Claude Code, Cursor, OpenAI Codex and Gemini.
How to use it
Getting the best result
- 1Fill in the bracketed context (product, audience, goal, tone) before sending the prompt
- 2Paste it into Claude Code, Cursor, or Codex inside an empty or existing Next.js project
- 3Review the generated file structure explanation before accepting all files
- 4Ask targeted follow-ups for one section at a time (e.g. "now refine the pricing section copy") rather than regenerating everything
Expected result
What you should get back
- A working Next.js project with a componentized single-page site (Header, Hero, Features, Pricing, Faq, Footer, etc.)
- Responsive layout that holds up on mobile, tablet and desktop breakpoints
- A short written explanation of the file/component structure and next steps
- Placeholder content clearly marked so you know what to replace before launch
Tips
Get more out of this prompt
- Give the AI real brand words (tone, 2-3 competitor names, a tagline you like) — vague prompts produce generic output
- Ask it to generate one section at a time if the first pass feels overwhelming to review
- Request a components/ folder structure explicitly if you want each section as its own file rather than one giant page.tsx
Common mistakes
What to watch out for
- Not specifying the audience or tone, resulting in generic SaaS boilerplate copy
- Accepting fabricated testimonials or customer logos without checking — always ask for placeholders instead
- Skipping the accessibility requirement, then having to retrofit alt text and keyboard support later
Related prompts
Keep going
website
Write conversion-focused landing page copy from a product brief
Generates specific, conversion-oriented landing page copy grounded in your actual product details, avoiding generic SaaS-template language.
Copy promptseoAudit and optimize a page's on-page SEO
Runs a structured on-page SEO audit of a real page and produces specific, implementable fixes rather than generic SEO advice.
Copy promptuiDesign and build an accessible, reusable UI component
Gets an AI to design a UI component's full set of states and variants up front, then implement it accessibly, instead of building only the happy-path visual state.
Copy promptReady to put this prompt to work?
Pair it with an AI coding tool and a real project, then ship something this week.