Ship the Surface

Everything a stranger finds when they go looking. Site first, then every profile that points at it. The live half is judgement; the rest is skill files you run.

Five-minute setup

Do this before the session starts, or in the first ten minutes while the framing happens. Nothing here is required to attend.

1. Have an agent installed

   Claude Code, the Codex extension, or whatever you already run. Every skill file below is plain markdown with frontmatter — it works in anything that reads a skills directory.

2. Get the skills

   Download this session's bundle and unzip it at the root of your project. It writes into .claude/skills/ and nothing else.

   unzip -o zero-to-launch-05-marketing-site.zip -d .

3. Not sure which skill you need?

   Run /ask-santos and describe the problem in your own words. It names one skill, says why that one, and tells you what comes after it. You don't have to learn the catalogue.

4. Point it at a real product

   An idea in a notes app counts. The skills read your repo, your site and your README before asking you anything, so run them from inside the project rather than a blank folder.

5. Make somewhere to put the output

   The template repo already has the folders. If you're working in your own project, a docs/gtm/ directory is fine — the skills write markdown, they don't care where.

The steps

1. 01

   Plan the structure before you write a line

   /site-structure

   Sections, the order they go in, and what each one has to accomplish before it earns a scroll.

   Done looks like: You can say what job every section does. Anything without a job gets cut.

2. 02

   Make the hero your one-liner

   /landing-copy

   Straight from session 04. If the positioning doesn't survive contact with the page, the positioning was the problem — not the page.

   Done looks like: The hero says what it is and who it's for, above the fold, without scrolling.

3. 03

   Cut to one CTA

   Five competing calls to action is the same as none. Pick the one thing you want a stranger to do and delete the rest.

   Done looks like: One primary button, repeated. Everything else is a link.

4. 04

   Scaffold and deploy

   /site-scaffold

   The Next.js boilerplate lands here — routing, metadata, sections. Deployed the same night is the target, on a real URL.

   Done looks like: A URL you can send someone.

5. 05

   Make links preview properly

   /og-image

   Every share you get for the next ten weeks runs through this. Ten minutes, permanently.

   Done looks like: Paste the URL into Discord and it looks deliberate.

6. 06

   Run the performance pass

   /perf-pass

   Core Web Vitals, but only the fixes that move the number. Skip the ones that don't.

   Done looks like: You know your LCP and it isn't embarrassing.

7. 07

   Work backwards to the content plan

   /content-map

   From what your ICP searches for to the first twenty pages. Then /programmatic-pages for the templated set, /article-draft for the ones that need a human.

   Done looks like: Twenty page titles, each tied to something a real person types into a search box.

8. 08

   Read your own profiles cold

   /social-audit

   Eight or so places a stranger lands. Most of the damage is a stale bio and a banner from two products ago.

   Done looks like: A list of what contradicts the positioning, per platform.

9. 09

   Fix them one at a time

   /social-profile

   Handle, bio, banner, pinned post, links, and the one line that has to match the site hero. One platform per run — each reads differently.

   Done looks like: Every profile says the same thing in that platform's shape.

What you leave with

05-site/ — structure.md, copy.md applied to the real page, a deployed URL in scaffold.md, perf.md, content-map.md, and social-profiles.md.

If you get stuck

Site looks fine and says nothing? That's a positioning problem wearing a design costume. Session 04 output, then come back.

Or ask in Discord — mentors are in there between Wednesdays, and everyone else's work in progress is too.