Claude can write the code quickly, but it cannot invent a strong offer from vague context. Collect these six inputs first:
brief.md. Put the six inputs above inside it, plus any brand colours, fonts, screenshots, logos, and examples Claude may use.Read brief.md and build a complete responsive landing page for this offer.
Start by summarising the audience, promise, objection, proof, and primary conversion action you found in the brief. Then propose the page structure before writing code.
Build the approved structure with semantic HTML and maintainable CSS. Above the fold, include one outcome-led headline, one supporting paragraph, one primary call-to-action button, and the strongest available proof. Continue with problem, solution, how it works, benefits, proof, objection handling, FAQ, and a final call to action. Keep one primary action throughout the page.
Write specific copy from the source material in brief.md. Do not invent testimonials, statistics, customers, urgency, or guarantees. Mark any genuinely missing proof as a clear placeholder.
Make the page mobile-first, keyboard accessible, fast to load, and visually polished without excessive animation. Use the supplied brand assets. When finished, run the project locally, inspect it at mobile and desktop widths, and list anything that still needs a human decision.
Audit only the first mobile screen of this landing page. A new visitor should understand who it is for, what result it promises, why it is credible, and what to click within five seconds. Give me three headline and subheadline combinations using different angles: outcome, speed, and objection handling. Recommend one, implement it, and keep the primary call to action visible without scrolling.
Review this page as a skeptical first-time visitor arriving from an ad. Identify every vague claim, unanswered objection, distracting link, competing call to action, and form field that is not necessary. Rank the issues by likely conversion impact, then implement the highest-impact fixes without inventing new proof.
Test the landing page at 375px, 768px, and 1440px widths. Check text wrapping, tap-target size, form labels, keyboard navigation, contrast, image sizing, layout shift, and whether the primary call to action remains obvious. Fix every reproducible issue. Then give me a short manual checklist for anything you cannot verify yourself.
Anthropic: Set up Claude Code
Google web.dev: Core Web Vitals
Google PageSpeed Insights