Claude Code prompt for a SaaS landing page

Work in this repository from the terminal and ship a landing page for a project management SaaS. The reader is engineering managers at startups — every line of copy should survive the test "would they say this to a colleague?"

Plan of work: inspect the project to confirm the framework and dev-server command, create the page plus one file per section, run the dev server, check your work against the list below, then commit.

Build these sections in order:
1. Navigation — slim sticky bar: logo left, links center, CTA right.
2. Hero — H1 states the end result a project management SaaS delivers in under 60 characters; subhead gives the mechanism in one sentence; CTA plus a muted secondary action.
3. Credibility row — three short proof statements (a metric, a customer count, an integration count) separated by dividers, not a logo wall.
4. Features — three blocks, each headed by something engineering managers at startups can now stop doing, followed by a two-sentence explanation.
5. Screenshot panel — dashboard image inside window-chrome framing, caption underneath.
6. Pricing teaser — one card with the entry price and a bullet list, plus a comparison link.
7. FAQ — five question/answer pairs in semantic markup; source the questions from real pre-purchase doubts.
8. Closing CTA and a compact footer.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Rules:
- One spacing scale only; section padding 6rem on desktop, 4rem on mobile; a consistent container width throughout.
- Mobile-first: write the stacked layout first, add desktop columns at 768px and up.

The primary call to action is "start a free trial" in the nav, hero, and closing section — one shared button component, three usages.

Verification loop: start the dev server, fetch the page or screenshot it, and confirm: it renders with no hydration or console errors; the three CTA usages come from one component; headings step down h1, h2, h3 without skips; the layout holds at 375px. Fix anything that fails, re-check, then commit with a message describing the page structure.