Free Claude Code Website Development Resources

Free, ungated production resources for developers building websites with Claude Code: a CLAUDE.md starter, plus launch, SEO, security and audit checklists.

Everything here is free, ungated, and stays that way. No email required to read any of it. These are the working documents behind the Claude Code guides on this site — the versions I actually open when I am building something rather than writing about it.

Use them in client work. Copy them into your own repository. Adapt them. The only thing asked in return is that you do not repackage and resell them as your own.

The resources

Production CLAUDE.md Starter

A working CLAUDE.md covering project context, architecture boundaries, coding standards, testing, security, SEO, accessibility, deployment, prohibited actions and a definition of done — plus how to tell whether yours is being followed.

Read it
Website Launch Checklist

Eighteen sections between “it looks finished” and “it is live and behaving”: requirements, architecture, responsive, accessibility, technical SEO, structured data, performance, security, forms, commerce, analytics, search engines, deployment and post-launch validation.

Read it
SEO Checklist

Sixteen sections of technical SEO in dependency order, from crawlability through to Search Console, Bing Webmaster Tools and IndexNow. Deliberately limited to things a machine can actually verify.

Read it
Security Checklist

Secrets, headers, input handling, authentication, sessions, authorisation, webhooks, dependencies, CI/CD, production hygiene, logging and privacy — plus a short section on what changes when an assistant can read your repository.

Read it
Website Audit Checklist

For a site that already exists. Fifteen sections of inspection, a severity scale, and a format for writing up findings with evidence attached rather than opinions.

Read it
Sample: Crawlability Audit Workflow

One complete workflow from the SEO & Website Audit Toolkit, reproduced in full: response codes, the soft 404 that returns 200, redirect chains, and whether your content is in the initial HTML at all. Nothing has been cut from it.

Read it
Sample: Landing Page Conversion Audit

One complete workflow from the Conversion & Revenue Optimization Toolkit. It runs in a mode that changes nothing, and every finding carries an honesty label — proven bug, strong heuristic, experiment opportunity, or insufficient data.

Read it
Web Development Failure Library

Twenty ways a site built with an AI coding assistant breaks quietly, each with how to detect it, fix it, and prove the fix worked. Sixteen of them were observed on this site and are labelled as such; the rest are labelled general.

Read it
CLAUDE.md Starter Kit

Four complete CLAUDE.md files — static site, web application, Shopify theme, monorepo package — with a checklist and a licence, as a zip. This one asks for an email address; everything else on this page does not.

Get the kit

On GitHub

The checklists above, plus a CLAUDE.md starter and five installable Claude Code skills, are published together as the Claude Code website starter kit — MIT-licensed, free to use in client work, and easier to clone than to copy out of a web page.

The system applied to a real build

These checklists came out of building this store. The full account — the thirteen-stage workflow, five production failures that every automated check reported as healthy, and the rule that came out of it — is in the Site Builder Stack case study.

Why these are free

Two honest reasons. The first is that the methodology is not the scarce part — assembling it, testing it, and keeping it current is. The Launch System exists for people who would rather have that done than do it. If these checklists answer your question and you never buy anything, that is a fine outcome.

The second is that a resource nobody can link to is not a resource. Gating a checklist behind a form guarantees it never gets cited, recommended, or found. These are meant to be linked to.

How they are maintained

These are versioned in the same repository as the site itself and updated when the underlying tooling changes. If something here is wrong, out of date, or missing, the contact page reaches me directly and I would rather know.

Four interactive tools

These generate something rather than hand you a document. They run entirely in your browser — nothing you type is transmitted anywhere — and none of them asks for an email address before showing a result.

CLAUDE.md Starter Generator — a starting project context file from your real commands and rules
SEO Audit Prompt Generator — an audit prompt scoped to your platform and situation
Website Launch Readiness Score — twenty questions, a score out of 100, a prioritised list
Website Prompt Builder — a structured project prompt with a discovery phase that changes nothing

All four tools

Labs, a weekly challenge, and a place to keep it all

Four practical labs plant a real fault in a fictional clinic's site — a canonical that points at staging, a launch that should hold, a form that only looks like it works, a health report to triage — and ask you to find it from the evidence. The Weekly Website Fix is one fifteen-minute check on your own site every Thursday. Both, and every generator in the guides, save to My Projects, which lives in your browser and nowhere else.

Start from a topic

Each checklist here belongs to a wider topic hub, which collects every guide on that subject with a suggested reading order:

The CLAUDE.md Starter Kit, free

Four working CLAUDE.md files you can drop into a project today, plus the one-page checklist for what belongs in one and how to tell whether yours is actually working.

CLAUDE.md for a static marketing site
CLAUDE.md for a web application, with security and migration rules
CLAUDE.md for a Shopify theme, including the gotchas that cost hours
CLAUDE.md for a shared package in a monorepo
A one-page checklist, and how to test the file is actually working