Resources

Building the thing is half of it. This is the other half: the repos, servers and services that get a solo build finished, live, and found.

Get found: SEO and AI visibility

Open the SEO section →

Ranking in Google is only half the game now. The other half is showing up when someone asks ChatGPT or an AI Overview. Here is how to do both, built on the method we use across our own sites.

Starters and boilerplates

Skip the first 2,000 lines. These give you auth, billing, and a deploy target on day one.

create-next-apprepoThe official Next.js starter. What most AI builders generate on top of.
shadcn/uirepoCopy-paste components you own outright. Why a lot of AI-built apps look decent.
Supabase starterrepoAuth, Postgres, and row-level security wired up. A solo builder's back end.

MCP servers

Model Context Protocol servers let an AI agent act on real systems while you build. The useful ones for a solo project.

Supabase MCPmcpLet the agent create tables, apply migrations, and read logs against your project.
Vercel MCPmcpDeploy, read build logs, and manage domains without leaving the agent.
GitHub MCPmcpPRs, issues, and repo actions from inside the build loop.

Deploy and infrastructure

Get it live and keep the running cost near zero. The parts a side project actually needs.

VercelservicePush to git, get a URL. The reason a lot of side projects have no deploy docs.
CloudflareserviceDNS, a generous free tier, and a proxy that absorbs a launch-day traffic spike.
ResendserviceTransactional email with a free tier that covers most projects for their whole life.

Guides

All guides →

Building a directory site with Claude Code
Choosing a domain for a side project
Deploying to Vercel: the parts that catch people out
Getting your first 100 users on your own
Programmatic SEO for side projects
Supabase auth for a solo builder