Simple explanation
Welcome to Day 14. Week 2 Build Day. Two weeks ago you had never opened Claude Code. Today you are going to build something that actually works for real visitors — using every skill from the last 14 days. Your Week 2 toolkit: ✓ CLAUDE.md giving Claude permanent project memory — Day 8 ✓ Specific color codes, fonts and rules in CLAUDE.md — Day 9 ✓ Slash commands for faster sessions — Day 10 ✓ @ mentions pointing directly at files — Day 11 ✓ Multi-clauding running two sessions at once — Day 12 ✓ Recovery process for when things go wrong — Day 13 Today's build: a complete lead capture page This is a real thing your site needs. A page that collects email addresses from visitors who are not ready to join the full challenge yet. It has three parts: a short form with one email field, a submit button, and a thank you message that appears after submission.
What to do
Follow these steps in order. Step 1 — Update your CLAUDE.md Open your CLAUDE.md file. Update the Current Goal section: "Building a lead capture page at /subscribe. One email field. Submit button. Thank you message on success. Must match existing site design exactly." Step 2 — Create two branches In GitHub Desktop create: Branch 1: "day-14-subscribe-page" Branch 2: "day-14-thank-you-content" Step 3 — Session 1 — build the page Open Claude Code. Turn on Auto Mode. Use this prompt: "Following all rules in CLAUDE.md — build a new page at /subscribe with: a heading that says 'Get the free lessons delivered to your inbox', a subheading that says 'Practical tips for non-developers. New lesson every few days. Free forever.', one email input field with placeholder text 'Your email address', one submit button that says 'Send me the lessons', and a thank you message that appears after submission saying 'You are in. First lesson on its way.' Connect to the existing email subscription system already on the site. Do not change any other page." Step 4 — Session 2 — write headline variations Open a second Claude Code window in parallel. Type: "Write three alternative headline options for the subscribe page. Each one should speak directly to a non-technical founder who is curious but not yet ready to commit to the full 5-day challenge. Warm and encouraging tone. Plain English. No jargon." Step 5 — Review both results Check the subscribe page works in your browser. Submit a test email — does the thank you message appear? Read the three headline options. Pick the one that feels most human. Use @ to update the headline: "@src/pages/subscribe.js update the heading to say [your chosen headline]" Step 6 — Run /review Type /review and ask Claude Code to check the page for any obvious problems before you consider it done. Step 7 — Merge to main When you are happy — merge both branches back to main. You have just completed Week 2. You now build with memory, shortcuts, parallel sessions, and a safety net. That is a completely different level from where you were 7 days ago. Week 3 starts tomorrow. You will learn power user moves — Skills, sub-agents, loops, and how to build your own personal workflow that makes every future session faster than the last.
Copy-paste prompt
Following all rules in CLAUDE.md — build a new page at /subscribe with: a heading that says "Get the free lessons delivered to your inbox", a subheading that says "Practical tips for non-developers. New lesson every few days. Free forever.", one email input field with placeholder "Your email address", one submit button that says "Send me the lessons", and a thank you message that says "You are in. First lesson on its way." Connect to the existing email subscription system. Do not change any other page.
Course note
Key takeaway
Branch first. Update CLAUDE.md with the current goal. Two sessions running in parallel. @ mentions for precision. /review before merging. That is the complete Week 2 workflow — and you just used all of it.