Turn a Figma design or screenshot into a working prototype

Recreate the attached design as a working, responsive web prototype in Bolt.new. Match it closely — this is a fidelity exercise, not "get the general idea across."

DESIGN SOURCE
a Figma file link with 4 frames: Landing, Pricing, Login, and Dashboard, all at desktop 1440px width

WHAT'S ACTUALLY IN THE DESIGN
The design shows Landing, Pricing, Login, and Dashboard, each at one desktop breakpoint only. Treat anything not shown in it as genuinely unspecified — do not invent a mobile layout, an empty state, or a hover state that isn't visible in the source and present it as if it came from the design; build only what's shown, and flag every gap you had to fill in separately from the parts that are a direct match.

FIDELITY RULES
Match spacing, type scale, and color as closely as the source allows — primary #1A73E8, text #1F2937, background #F9FAFB — pulled directly from the Figma inspector panel if you have exact hex values, use them exactly; if you're estimating from a screenshot, say which values are estimates rather than presenting a guessed color as if it were specified. Match the actual layout structure — if the design uses a 12-column grid with specific gutters, build that grid, don't approximate it with a generic flex layout that happens to look similar at one viewport width and diverges at others. Reproduce real component states shown in the source (a button's hover or disabled state, an input's error state) exactly as shown — if the source only shows one state of a given element, note that as a gap rather than inventing the other states from a generic design-system instinct.

RESPONSIVE BEHAVIOR
The source is a single static Figma frame at 1440px, which by definition only shows one breakpoint. For breakpoints not shown at all, apply these explicit rules rather than guessing: stack any multi-column section to a single column below 768px, keep the nav collapsing into a hamburger menu below 900px. State plainly, screen by screen, what you had to decide for a breakpoint the source didn't cover, so it's clear which parts of the responsive behavior are a real match to a design decision and which are your own reasonable default.

INTERACTIVITY
Login should navigate to Dashboard on submit with any input; Pricing CTA buttons should scroll to or navigate to Login Anything clickable in the design that doesn't have a defined destination in this brief should navigate somewhere plausible within the prototype rather than being a dead link — but note every destination you had to invent so it can be corrected.

CONSTRAINTS
Use React with Tailwind CSS. Keep the DOM structure reasonably semantic — real headings, real button and link elements — rather than a wall of generic divs with inline styles, since a prototype this close to final should be able to become production code with normal cleanup, not a full rewrite. Name the actual font family if it's identifiable in the source, or say explicitly that you substituted a close system-font equivalent because the real one couldn't be confirmed from a static image alone.