Before building the landing page, create a separate project folder and add a CLAUDE.md file. This file gives Claude Code persistent context about the project, its goals, structure, and development conventions.

Claude reads CLAUDE.md when a new session begins. This removes the need to repeat the same instructions in every conversation and helps Claude make decisions that remain consistent with the project.

Creating an Effective CLAUDE.md File

A CLAUDE.md file does not require a fixed structure. It should be short, clear, and easy to update. Markdown headings and bullet points work well for documenting:

• The project goal
• The target audience
• The technology stack
• The repository structure
• Build and test commands
• Important coding conventions

Claude can also search its documentation for current recommendations before creating the file.

Choosing Where to Store It

A CLAUDE.md file can provide different levels of context depending on its location:

• Home directory: instructions shared across projects
• Project root: context for the entire repository
• Child directory: instructions for a specific part of the project

For example, the root file can describe the complete outreach system, while a file inside the landing-page folder can contain instructions specific to the website.

Preparing the Landing Page

Claude may ask clarifying questions before creating the project files. In this example, the landing page uses Next.js and Tailwind CSS.

Once the folder and context file are ready, Claude can scaffold the application and create an initial design from an uploaded reference image. It can identify elements such as:

• Colors and typography
• Service cards
• Case studies
• Testimonials
• Contact forms
• Footers

The first version will usually require refinement. Additional business context and feedback can then be provided through an iterative process until the content and design match the intended result.