From Zero to Claude Code in 19 Minutes (no code)
A 19-minute hands-on walkthrough that takes a complete beginner from zero to a live deployed web app using only natural language.
June 15thAn 84-minute, screen-share walkthrough that takes a v0 template from an empty folder to a live, custom-domain site indexed on Google, Bing, and Yandex — entirely through plain-English prompts.
Once you wire Claude Code into the command-line tools for your host, your domain, and your search consoles, building and ranking a website stops being a coding job and becomes a sequence of plain-English prompts.
The site is built by handing Claude Code a downloaded v0.dev template and the target offer, then prompting it to rebuild the pages around that offer rather than writing any code. The author swaps the hero image for a free stock background video, replaces stock photos with relevant ones, and runs the open-source claude-seo skill for three successive audits, staying deliberately skeptical and re-auditing before and after deployment. Deployment uses the Railway CLI so Claude can ship the site itself; the .md domain is connected through Cloudflare nameservers and DNS records, and the Google Cloud CLI lets Claude verify the property, submit the sitemap, and trigger indexing across Google, Bing, and Yandex. The lesson: the initial CLI-and-credential setup is the only hard part, after which updates and indexing become one-prompt operations.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →
Empty folder to live, indexed site — no designers, agencies, or developers. Lists the full pipeline: niche, audience, template, build, SEO, deploy, index.

Pick the offer (here, a 'Claude Ads' skill) and identify exactly who it's for before touching anything.

Browse v0.dev landing-page templates, pick the Sakura-tree design, download it as a ZIP, and drop it into a fresh folder.

Open Claude Code in the folder; prompt it in plan mode (max effort) to read the repo and template and build home/features/installs/docs pages around the offer.

Claude reports four pages built with content in lib/content; run the dev server to review the first version live.

Replace the Sakura background with a free Pixabay video (play once, freeze on last frame) and swap tree photos for relevant Pexels images, asking Claude to compress and follow best practices.

Install the claude-seo skill, then run a full audit via /seo with subagents in plan mode: sitemap, schema, pages, images, AI-search readiness.

Shows the prior claude-seo.md site at 11,000 clicks / 343,000 impressions in ~3 months off one backlink, and a 98-99 PageSpeed score as the target.

Distrust the agent's 'all done' report; prompt a second full pre-deploy audit with web research, surfacing a claim-vs-reality table of real fixes.

Sign up for Railway ($5/mo for custom domains), install the Railway CLI by prompt, authorize via browser OAuth, and let Claude create the project and deploy.

Next.js build compiles clean, routes pre-render, the image ships, and Claude generates the public railway.app domain — the site is live in under five minutes of deploy time.

Connect the purchased claude-ads.md domain: add the site to Cloudflare, create CNAME and TXT records from Claude's instructions, and point the registrar's nameservers at Cloudflare.

While DNS propagates, install the Google Cloud CLI and prepare Search Console access so indexing can later run from prompts.

Two hours later the custom domain resolves to the site; run a post-domain SEO audit and add the www record with Cloudflare proxy hardening.

Final desktop/mobile PageSpeed pass reaches 100/96/96/100 and then near-perfect mobile after fixes — the agent fixes whatever is red from a pasted screenshot.

Authorize the Google Cloud CLI via OAuth, create the project and service account, enable the APIs, verify the domain by TXT, submit the sitemap, and notify the Indexing API for all routes.

Index on Bing and Yandex via IndexNow (a key file at the root, no API), then manually request indexing for the handful of important pages because manual submission has higher priority.

Replace the v0 favicon with a generated logo and set up an Obsidian 'website brain' (the claude-obsidian skill) so the agent keeps page plans and PageSpeed data as a growing vault.

Recaps the full pipeline: ~10 prompts, ~8 hours of Claude time, ~1 hour of human time, from empty folder to a ranked, indexed site; subscribe CTA.
The build itself is the easy half; the durable win is connecting Claude Code to your host, domain, and search-console CLIs so every future update and index request is a single sentence.
“Today, we go from an empty folder to a live published website with Claude Code. No designers, no agencies, no developers.”
“You don't need any coding knowledge — you just need English. This is the new coding language.”
“It already has over 11,000 clicks and over 343,000 impressions in three months off a single backlink.”
“We don't believe everything AI says — that's why I ran another full audit before deployment.”
“One hour of my time, eight hours of Claude's time, and we have a fully developed, ready-to-rank website indexed on Google.”
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The promise is stated in the first eight seconds with no preamble: empty folder to live, indexed website, no designers, no agencies, no developers. What follows is the unedited 84-minute reality of that claim — the parts that take one prompt, and the parts that still make you copy-paste a nameserver into a registrar by hand.
The eight-stage spine the whole video follows, stated up front and then executed in order.
The phased prompt pack behind the /seo commands — each phase is a checkpointed command you can run in sequence and stop before hosting.
Audit before deploy, again after deploy, and again after the domain connects. Distrust the agent's 'done' and re-run; every pass finds real fixes via a claim-vs-reality table.
“Thank you so much for watching this long video. Make sure you subscribe and like if you found it useful. Hydrate and keep on building.”
Soft, end-of-video subscribe ask after delivering the full build; the real lead magnet is the prompt pack and skills linked in the description, not a hard mid-roll pitch.
00:00
01:50
02:37
03:41
04:44
05:47
06:50
07:53
08:54
09:53
11:03
12:06
12:40
14:12
15:15
16:06
17:22
18:25
19:28
20:06
21:22
22:11
23:21
24:44
25:34
26:50
27:53
28:56
30:00
31:26
32:13
33:09
34:12
35:15
36:19
37:22
38:25
39:28
40:31
41:34
42:38
44:06
44:44
45:27
46:26
48:10
48:57
50:00
51:03
51:39
52:44
54:17
55:01
56:19
57:22
58:41
59:28
60:55
61:35
62:31
63:28
64:44
65:23
66:50
67:40
68:49
70:25
70:35
72:06
73:08
73:53
74:49
76:18
77:22
78:03
78:57
80:31
81:06
82:13
83:21A 19-minute hands-on walkthrough that takes a complete beginner from zero to a live deployed web app using only natural language.
June 15thA 68-minute screen-share where Cole Medin walks through the five-part system that turns prompting-and-praying into directing your coding agent.
June 18thA two-hour livestream that turns the year's biggest AI buzzword into a working autonomous agent you can ship this week.
June 19thHow xAI’s self-describing Agent Instructions let a vibe-coder ship a page-navigating website voice assistant in a single Replit session.
June 17thA 25-minute case for letting agents run their own loops — and how one 2:29 AM prompt produced four merged PRs by morning.
June 18thA plain-English field guide to every loop type — heartbeat, cron, hook, and goal — with two live builds in Claude Code and Codex.
June 17th