Let me read the full plan and the current project files to begin implementation.

Good - I have a solid grasp of the project. The starter has all the dependencies I need: react-hook-form, zod, date-fns, react-day-picker, sonner, and all the shadcn/ui primitives. Let me check the existing UI components and then generate design inspiration.

Excellent design inspiration. Now let me check existing shadcn components and set up the task list.

Let me check the read-only examples for useful shadcn component references:

Good. Now let me set up the task list and start building. This is a large project with distinct systems.

Let me start with Task 1: Theme, Layout, Navbar & Footer. First, I'll generate the headshot for Marcus, set up the theme, and create foundational files in parallel.

Now let me set up the complete theme system, data layer, types, and core components. I'll do this in parallel:

Now let me update the layout with proper fonts/metadata and create the navbar and footer:

Task 1 complete. Moving to Task 2: Hero Section.

Hero section complete with split layout, headshot, trust badges, stats, and mobile-stacking. Moving to Task 3.

Features, Pricing, and Case Studies sections are done. Moving to Task 4.

Testimonials, FAQ, and CTA sections complete. Moving to the booking modal -- the most complex component.

Now let me create the main booking modal wrapper that orchestrates all 3 steps, then assemble the full page.

Now let me create a shared booking context/provider so any CTA button across the page can trigger the modal, then assemble the final page.

Now let me move to the final task -- assembling the page and wiring everything together.

Now I need to read the existing section components to understand their export signatures, then assemble the page. Let me verify the exports quickly:

I see the issue -- several components take onBookingClick as a prop, while my booking modal uses a context-based useBooking hook. The step components also use different prop names (onNext vs onComplete). I need to align these. Let me check the actual interfaces:

I can see the prop interface mismatches between the booking modal and the step components. Let me also read the remaining files I need:

Now I can see all the interface mismatches. Here's what needs to be fixed:

1. StepOne: uses onNext but modal passes onComplete, uses BookingFormData as type (but that only has name/email/phone, no date/time). Also uses export default but modal imports as named { StepOne }.
2. StepTwo: uses onNext(date, time) but modal passes onComplete({date, time}). Uses export default but modal imports as named.
3. StepThree: uses selectedDate, selectedTime, onConfirm props separately but modal passes formData (with date/time inside) and onComplete.
4. Availability: has saveBookingToStorage but modal calls saveBooking.
5. BookingFormData type: doesn't include date and time, but the modal sets them on formData.

Let me fix all these mismatches. I need to update the types, the step components, and the availability module:

Now add the saveBooking function to availability.ts:

Now fix StepOne -- change from default export and onNext to named export and onComplete:

Now fix StepTwo -- named export, onComplete({date, time}) signature, and support defaultDate/defaultTime:

Now fix StepThree to accept formData (with date/time inside) and onComplete:

Now let me also read the remaining section components to confirm they work correctly, and then assemble the page:

Good -- all the section components and data look solid. The components that take onBookingClick props (Hero, Navbar, Pricing, CTA) need to receive it from the page, which will get the function from the useBooking context hook. Now let me read the layout and footer to check for the Toaster/Sonner setup, then assemble the page:

Everything looks good -- layout has Toaster, CSS has the full theme. Now let me assemble the main page and read the footer for completeness:

Everything looks great. Now let me write the main page that ties all sections together with the BookingProvider context:

Now let me verify the Dialog component exists in the project since the booking modal depends on it:

The dialog component file doesn't exist but the @radix-ui/react-dialog dependency is installed. I need to create the Dialog UI component. Let me also check what other UI components are available:

All the UI components exist -- the dialog component is at components/ui/dialog.tsx. The glob was just having timing issues earlier. Everything is in place. Now let me mark all tasks as done:

The full landing page for Marcus Chen Mortgage Advice is now built. Here's what was implemented across all 6 tasks:

Theme & Layout: Custom Deep Navy/Slate/Gold/Cream color system via CSS custom properties and Tailwind v4 tokens, Inter + Playfair Display fonts, smooth scroll, and full SEO metadata with structured data for Scottish mortgage search.

Sections: Split-hero with generated headshot and trust badges (FCA Regulated, Whole of Market, Scottish Market Expert) that stacks vertically on mobile; 3 feature cards; 3-tier pricing table; 3 illustrative case studies (Edinburgh first-time buyer, Glasgow investor, St Andrews retiree); auto-rotating testimonial carousel with 5 clients; 7-question FAQ accordion; and a final CTA section.

Booking Modal: Full 3-step flow -- Step 1 collects name/email/phone with Zod validation and UK phone regex; Step 2 shows a calendar (Monday-Saturday, 9AM-5PM UK time, next-afternoon-onwards rule) with hourly time slots; Step 3 shows a summary with GDPR consent checkbox. All data persists in localStorage, enforces 1 booking per email per day, and logs confirmation to the console. Modal state is resumable if closed mid-flow.

Accessibility: WCAG AAA intent with semantic HTML, ARIA labels, skip-to-content link, proper focus management, keyboard navigation, and screen reader support throughout.