Claude Code prompt for an agency landing page

Using Claude Code in this repo's terminal, build a one-page agency site for a project management SaaS that leads with shipped work, aimed at engineering managers at startups. Create the files, run the dev server yourself to inspect the result, and commit once the checks pass.

Files: one page entry plus a sections/ folder containing Hero, CaseWall, Services, Process, Ethos, and Contact. Match the project's existing structure if there is one; otherwise scaffold the lightest static setup you can serve locally.

Section spec:
1. Hero — split layout: left, a claim naming a project management SaaS's specialty and the change it produces for clients; right, a stacked list of 3 proof stats (projects shipped, sectors served, years running).
2. CaseWall — a masonry-style wall of 6 case tiles at two sizes (2 large, 4 standard); every tile carries a project name, sector tag, and outcome line. No empty tiles.
3. Services — 5 offerings as horizontally scrolling cards on desktop; each card holds the service plus 3 concrete deliverables.
4. Process — a 4-row table: phase, duration, what happens, what the client gets.
5. Ethos — 2 short paragraphs of working principles, with team names and roles set small beneath.
6. Contact — a heading derived from the specialty ("Have a [x] problem?"), a direct email, and the CTA button.

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: 128px between sections on desktop, 72px on mobile; halve those values for spacing inside a section.
- The service cards must be swipeable on touch, and the CaseWall reflows to a single column under 640px.

The primary call to action is "start a free trial", used on the hero and the Contact button only. Infer case-tile copy from a project management SaaS's field; placeholder text like "Coming soon" is not acceptable.

Then close the loop: start the dev server, confirm the page renders at desktop width and at 375px, count the six tiles and both CTA instances, fix anything that fails, and commit with a message describing the page. Report the commands you ran and what you verified.