Guides I've written for founders and people building software. Most are a PDF you can read in one sitting, some are web pages, and every one is free for the price of an email.
Browse the shelf all you like. The first guide you open asks for your email. That's the price of admission: one email, once, and every guide here is yours, on the web or as a PDF. It's also how you hear when the next one lands.
Newest first. Click a row for the full entry, read any guide right here on the web, or grab the PDF to keep.
Claude writes and reviews about 90% of the code behind Claude Code. The team doesn’t get away with that by telling the AI to be more careful. They make it prove its work. Here are ten checks to steal from them: make it use the product like a customer, throw thousands of weird inputs at it, compare the old version with the new one, get a second AI to review it, run a separate security check, run tests and the build before every commit, stop after three failed fixes, turn repeat bugs into rules, never let it edit the test to pass, and put more human eyes on riskier changes. Each one has what Anthropic does and a prompt to paste, plus a rules file that puts all ten in your CLAUDE.md.
Checks, each with a prompt to paste.
Failed fixes, then the AI stops and asks a human.
Rules file that puts all ten in your CLAUDE.md.
You don’t need to be a software engineer to vibe code. But you can steal decades of lessons from the people who already made all the mistakes, and they gave them silly names. YAGNI: don’t build it until somebody needs it. DRY: write it once, use it everywhere. KISS: the boring version is usually the right one. Then five more that save you once you have real users: SRP, Separation of Concerns, Single Source of Truth, Test-Driven Development and the Principle of Least Astonishment. For each one: where it came from, what it looks like when Claude or Cursor breaks it (microservices for your zero customers, 14 files to add a button), the signs you’re breaking it, and a prompt to paste so it doesn’t. Plus eight honorable mentions, a rules file that puts all eight in your CLAUDE.md, and an audit prompt that grades the app you’ve already built.
Prompts to paste into Claude Code or Cursor, one per rule.
Honorable mentions, from WET to Chesterton’s Fence.
Rules file and one audit prompt for the app you’ve already built.
Most solo founders don’t fail because the code was bad. They fail in the first few months, before anyone’s paid, making the same eight mistakes, and every one feels like progress at the time. Asking friends and family. Never reaching out to a stranger. Asking “would you pay for this?” and believing the yes. Turning discovery calls into demos. Building every feature a customer asks for, when customers know their problem, not the fix. Running on free tiers that sleep, so beta testers think it’s broken. No plan for how anyone will hear about it. And growing a product nobody’s pulling for. For each one: how to tell you’re making it and what to do instead. Plus a channel-by-channel guide to distribution, twelve questions that get the truth on a discovery call (the magic wand, what they’d make go away, the most frustrating part), a self-check that scores you, and a prompt that reviews your call notes.
Questions to ask on a discovery call instead.
Distribution channels, and when each one fits.
Prompt that reviews your call notes for the mistakes.
Most people spend PTO one day at a time. Put each day next to a weekend or a holiday and it pulls those days in with it. In 2027, 14 PTO days get you 46 days off across 11 breaks: six 4-day weekends off Monday holidays, three 3-day weekends in the months with none, nine days in a row at Thanksgiving for four PTO days, and Christmas Friday to Monday. The exact dates to request, a calendar for every month, a file that adds all 11 breaks to your calendar, what to change if your company skips Columbus Day or gives you the day after Thanksgiving, and a prompt that plans your own year for any number of days.
Breaks, one in every month but March.
Of the 46 are weekends and holidays you already had.
Days in a row at Thanksgiving, for four PTO days.
Most bad prompts look the same: a page of steps, a wall of rules in capital letters, no picture of what good looks like, and no way to tell if it worked. Better prompts are shorter and have four parts. A goal, not the steps, because today’s models think before they answer and your steps cap them at your plan. A few hard rules with reasons, not a rulebook, because “never” really does mean never. Examples of good and bad output, each with one line on why. And a test, so it checks its own work before you do. Backed by Anthropic’s own prompting guides, with what’s different about Fable 5.2 (finish the task, say who owns the code, prune old rules) and Opus 5.5 (effort is the dial, explore first, name how it stops early), plus a template to copy.
Models, Fable 5.2 and Opus 5.5, and what to do differently for each.
Tips, each tied to what Anthropic’s own guides found.
Template to copy, with the pink bits to fill in.
AI has made it ridiculously cheap to build software. It hasn’t made it cheap to own. The moment 30 people depend on the app you vibe coded, you’re running a software company. Ten reasons to build and ten reasons to buy, none of them “it’s cheaper”: seat pricing that decides who sees the data, AI agents that need your data, the builder who leaves and the builder who can’t, offboarding, due diligence and more. Plus the three kinds of software and which way each leans, the option most companies miss (buy the core, build the edges), a 25-point checklist that scores whether you’re ready to own what you built, and a prompt that makes the call with you.
Kinds of software, and which way each one leans.
Checks to run before anyone depends on what you built.
Prompt that interviews you, then makes the call.
If you’ve ever told Claude Code “don’t ask again,” you might be leaking your passwords. It saves the command you approved to .claude/settings.local.json, secrets and all, and researchers just found 1,122 of those files on public GitHub holding 1,379 secrets: database passwords, SSH logins, GitHub and AWS keys. One company confirmed its key was still live. Where the file lives and why it leaks, six checks that take about five minutes, the one line for your .gitignore, how to rotate each kind of key and what to check after, and a prompt for Cloudflare’s security audit skill that checks your agent settings while it audits the rest.
Secrets in them: database passwords, SSH logins, GitHub and AWS keys.
Checks to run, about five minutes per project.
Kinds of secret, with where to rotate each and what to check after.
You don't need complicated infrastructure to build a serious software company. This is the exact stack I'd use if I started again tomorrow: TypeScript and Next.js on Vercel, Supabase and Prisma, Stripe, S3, SendGrid, Twilio, PostHog, Datadog, and Claude Code in Conductor to build it. What each one does in plain English, why I pick it, what I'd skip (Express, Kubernetes, Clerk, Redis on day one), and how to set it up. Plus structured logging, the security holes AI apps ship with, backups you've actually restored, a starter prompt, security and launch checklists, and a Day 0 / 30 / 90 roadmap.
Kubernetes clusters. Vercel runs it, you sell.
Checklists: before real customer data, and before launch.
Prompt that lays the foundation in Claude Code.
I was copying numbers out of the Instagram app by hand and still couldn’t tell which hooks worked, so I built a private dashboard. It pulls every post’s real stats from Meta’s API, transcribes every reel on my laptop with Whisper, has Claude label each hook, scores every post against my others and shows which hook types and topics win. The whole build: the stack (Next.js, TypeScript, Vercel, Neon), getting a Meta token two ways, every number Instagram gives you, the score and what I learned tuning it, and a prompt that builds your own from an empty folder.
A score for every post, against your own others of the same format.
Prompt that builds the whole thing from an empty folder.
Tools in the stack. Five are free; the sixth is your Claude plan.
Ten repos from GitHub's trending lists the week of November 3, none of them in Vol. 1 or my Top 11 skill repos. Audit your SEO, test your checkout in plain English, give your agent a memory, run it from your phone, dictate instead of typing, scrape competitor prices, remake a video's style, hand off the sales and finance work, ship a landing page that doesn't look AI-made, and prototype a physical product. Each one comes with my notes, the install command and one thing to try this week.
Trending lists read: GitHub's weekly, daily and monthly, and Trendshift's.
Email unlocks this and every other guide on the shelf.
Every repo is open source.
Nobody wants to be sold to by a stranger. Almost everybody likes being asked for advice. Ten ways for a solo founder to start a conversation with the people they want as customers, from replying to a complaint and spotting a job post to the veteran ask, the screen share and the trade show floor. Each one comes with where to find the people for B2B and B2C, and a script for both. Then the searches that find people mid-complaint, the questions that get the truth once they reply, and the loop back that turns advice into a first customer.
Scripts to copy, one B2B and one B2C for each.
Loop-back messages that turn advice into customers.
Free. Copy a script and send it today.
An AI company just left 17.6 million files, including 144,000 private chat logs, in a public storage bucket. Nobody hacked them; one setting was wrong. AI-built apps ship with the same holes over and over: public buckets, Row Level Security turned off, records anyone can open by changing the ID in the URL, secret keys in the browser, routes with no auth check, no rate limits. The ten to check before launch, five bonus ones, how to test each in a few minutes, where to click in AWS, Supabase and Firebase, and a prompt that has Claude Code rank them in your own codebase before it changes a line.
Bonus checks: webhooks, uploads, prompt injection, packages and debug mode.
Prompt that finds and ranks them in your codebase.
Free. Copy the prompt and go.
AI writes code that works on twelve rows of test data. Then real customers show up and the page takes ten seconds. The same dozen mistakes cause most of it: N+1 queries, missing indexes, await in a loop, request waterfalls, one giant serial job, no caching. What each one looks like, how to spot it, the fix, and a prompt that has Claude Code rank them in your own codebase before it changes a line.
Free ways to measure before you guess.
Prompt that finds and ranks them in your codebase.
Free. Copy the prompt and go.
Nine repos from GitHub's trending lists the week of October 22, picked for what they do for a company of one: take apart a feature in someone else's app, audit your security, dub your demo, render a launch video, run agents in parallel, drive your business apps, and ship the Android version. Each one comes with my notes, the install command and one thing to try this week.
Weekly trending lists read: GitHub's and Trendshift's.
Email unlocks this and every other guide on the shelf.
Every repo is open source.
Cutroom is the editor I built to cut my own Reels. It transcribes your take, cuts the pauses, filler and retakes, and adds titles, captions and animations in your brand. You leave notes on shots and Claude Code makes the changes, all on your Mac. It's an early, hands-on project, not a one-click app, so this walkthrough starts with who it's for and who it isn't. Then the install, your first edit from raw take to finished video, your own colors and fonts, ten things that go wrong and how to fix them, and how to make it yours.
Steps from raw take to finished Reel.
Things that trip people up, and the fix for each.
Cutroom is free. You need Claude Code and a Mac.
If a new model drops next month, does your startup get better or worse? Five businesses I'd build that get better: portable AI memory, agent security audits, agent-ready data, AI insurance evaluations and an industry data marketplace. For each one: who pays, the first version I'd build, how I'd get customers, why smarter AI helps, and what could kill it. Plus four questions to run your own idea through.
Covered in the video. The other three are only here.
Questions to test any AI startup, including yours.
Test: does the next model make you better or worse?
Is Agentic is a free tool from Vercel and Ora that scores how ready your website is for AI agents. It scored davecto.com 75/100, flagged five issues including a missing privacy page, and generated a prompt to fix them all. I pasted it into Claude Code, merged one PR and rescanned at 100. What it checks, what it found, how to run it on your own site, and what a perfect score doesn't mean.
Issues flagged, from Markdown support to a missing privacy page.
Fix prompt, generated for you, ready to paste.
Free, no signup.
Ponytail promises leaner code, fewer tokens and less overengineering. I ran Claude Opus 5.5 with and without it. The session used about 14% less context, but the code wasn't meaningfully cleaner or easier to maintain. What it is, what I measured, what I didn't, and the few cases where it's worth installing.
Fewer tokens in context, from 127.3k to 110k.
Run of each. A quick test, not a benchmark.
GitHub stars.
Your coding agent talks too much and reads too much, and you pay for both. Caveman started as a joke skill that makes Claude Code answer like a caveman. Version 4.0 also shrinks logs, JSON and test output before the model reads them. What the six parts do, which install fits you, and the honest numbers to check first.
Fewer input tokens per Claude Code session, by the maintainer’s benchmark.
Coding agents it works with, including Claude Code, Codex and Gemini CLI.
Apache-2.0, runs on your machine.
You built the app in a weekend. Then the App Store asks for a privacy policy, a partner wants an NDA and your first business customer wants a contract. A startup law firm has put 12 of its templates on GitHub, free under CC0, in markdown your agent can fill in. Which ones you need, four prompts to paste, and what to check before you publish.
Attorney-drafted templates, from terms of use to a HIPAA BAA.
Founder jobs, each with a prompt you can paste.
CC0. No attribution needed.
The best research for a solo founder is in conversations: Reddit threads, X replies, YouTube reviews. Your agent can't get to most of them without logins, paid APIs or a tool for each site. Agent Reach sets all of that up for free in one line. What it is, four jobs it's good at with prompts to paste, and how to install it.
Platforms, including Reddit, X, YouTube, LinkedIn and Instagram.
Research jobs, each with a prompt you can paste.
No API fees. MIT licensed.
Ask an agent to build a feature with no brand guide and you get the average of the internet, a little different every time. A Taste Index fixes that: rules in Markdown, tokens in CSS, motion in JavaScript, and one page that shows it all. What goes in each file, the two I use for this site, and the prompt that builds one from any website.
Prompt that builds one from any website you point it at.
Real examples, the two styles this site is built in.
Free. Copy the prompt and go.
Your agent's context window fills up with log files, browser snapshots and API responses, then forgets what it was doing when the conversation compacts. Context Mode sandboxes the raw output, lets only the answer through, and remembers your session. What it is, who it's for, and the two commands to install it.
GitHub stars.
Coding agents it works with, including Claude Code, Codex and Cursor.
Free, and runs on your machine.
Nine things I'd hand anyone building a company alone: three Paul Graham essays, the Four Fits, cohort retention, the four kinds of moat, the product death cycle, a founder coach's guide to your own head, and The Mom Test. Each one comes with my notes and one thing to try this week.
By Paul Graham.
Email unlocks this and every other guide on the shelf.
What any of it costs.
Start with the name brand’s free tier. If your usage fits under it, use the paid tool and skip self-hosting, because your time costs more than a free plan. Open source wins on day one in only two situations, and this guide names both, tool by tool, with the usage or the bill that should trigger a switch.
Categories where I’d skip the name brand entirely and start on the alternative.
The monthly VPS bill behind every “free” self-hosted tool. It’s never the expensive part.
Typeform responses per month on the free plan. That’s the shape of a free tier that can’t run a business.
“Don't screw around with the database. Just use Supabase. If you can't afford Supabase's free tier, something has gone wrong.”From Entry 02 · Backend, Database & Auth
Jev doesn’t write for you. You hand it context and a set of options, and it hands back a classification, a score, or a probability. That’s a narrower product than a chatbot, and the narrowness is the entire opportunity. Eleven places I’d look, and four questions that generate more of them than any list.
Sampled review becomes complete review. That change, not the model, is what customers buy.
A probability instead of a verdict. Thresholds are how software acts on uncertainty without a human in every loop.
Jev-Ultrafast’s second act: decisions that become clicks, on the thousands of sites that never shipped an API.
“If the expensive part of your product is producing the word yes, you don’t have a language problem. You have a pricing problem, and pricing problems are the ones that turn into companies.”From The Guide
/brag is an open-source Claude Code skill that reads your project’s actual code, writes a storyboard, scores it, renders an MP4, and hands you the caption to post with it. Two commands to install, one word to run. Here’s the setup, then five things worth knowing before your first run.
Tone presets, from polished to chaotic, plus freeform direction that overrides any of them.
Files you get back: the plan, the composition, brag.mp4, and share copy written in the video’s tone.
Screenshots, URLs or design assets you need to supply. It reads the source.
“Argue with the plan, not with the render. Fixing a hook in the plan costs a sentence; fixing it after the render costs the render.”From Step Three · Getting A Good One
/brag isn't mine. I have no relationship with the people who make it or with Hyperframes. I just use it.
The 11 most-starred skill repos for Claude Code and Codex, ranked by GitHub stars. For each one you get what it does, what makes it good, and the exact command to install it. This one's a web page, not a PDF, so the Copy buttons work.
Stars on No.01, Matt Pocock's skills.
What every one of them costs.
Ways to install almost anything on the list.
How to build a command-line tool that reads the systems your business actually runs on, with the worked example I built against HubSpot, QuickBooks and Gmail, the seven prompts that produce it, and the part everyone gets stuck on: getting the tokens.
Runtime dependencies. Everything else is the standard library.
Servers, databases, containers, or things that can be down at 8am.
Word you have to remember to use it.
“A tiny surface over messy systems is worth more than a big one. One word plus a company name beats a dashboard with forty filters.”From The Guide
Ten things to check before you upgrade, in the order I’d check them. Most people running out of tokens are not doing too much work. They are carrying too much furniture into every single message.
Input-price gap between Haiku 4.5 and Opus 5. Same dollar, five times the volume.
How often your skills, instructions and tool list get resent. Not once. Every turn.
The one-time audit in Part two. It’s the highest-return half hour here.
“A fresh session that opens at 40,000 tokens isn’t a fresh session. It’s a bill you agreed to before you started working.”From The Guide
Copy these three prompts into muse.ai once your Instagram account is connected. One reads your competitors, one audits your last twenty posts, one takes apart how your videos end. Paste them as-is.
“Every claim needs a post and a number attached to it. That single rule is what separates a useful audit from a horoscope.”From The Guide
Twelve things to check the night before your first App Store submission. Three of them are mine, learned by arguing with Apple. The other nine are the ones that catch everybody else.
Of submissions reviewed within 24 hours, per Apple. Rejections are cheap in money, expensive in days.
The guideline number for account deletion. Memorise it; it’s the one that got me.
The device they’ll test on that you almost certainly haven’t.
“The reviewer isn’t hostile and isn’t on your team. They’re a stranger with a queue, and everything ambiguous resolves against you.”From The Guide
Cloudflare built a toll booth for AI crawlers and left the pricing logic empty on purpose. Eleven businesses that could grow in that gap, what each one actually requires to work, and the specific reason each one might not.
of global web traffic sits behind the company running the toll booth
worst reported crawl-to-referral ratio for a major AI bot
businesses here, each with the reason it might not work
“The interesting part isn’t that a toll booth exists. It’s that nobody has decided what anything costs.”From The Guide
OpenAI shipped a model that can operate software for forty minutes at a stretch and still fails most of the way through six out of ten professional automations. Seven businesses that work anyway, because in each one checking the answer costs less than producing it. Each also gets the specific reason it might not.
gap between the headline ARC-AGI-3 score and the independent harness’s
the direction frontier token prices moved this month. Up.
businesses here, each with the reason it might not work
“Every company has work worth doing that nobody does, because sending a human to go and get it costs more than the work returns.”From The Guide
One block of text you paste above any real request. It forces the model to interview you first, show you its plan, and wait for approval before it writes a word.
questions, delivered at once, ranked by consequence
places it has to stop and wait for you
minutes of answering that saves an hour of rewriting
“A model never says “I don’t know enough to start yet.” It just starts.”From The Guide
How to move a career you already have into the job companies are creating right now: getting real people to actually use the AI they already bought. What the work is, which door you walk in, and the thirty days that make you credible.
case studies that outweigh any certificate
credential actually worth paying for
days to a portfolio, a rewritten profile, and a real story
“The hard part was never the software. It’s the ninety people who have to change how they work.”From The Guide
Ten free courses, in the order that actually works, plus what to build after each one. Four weekends, about twenty five hours, and one small agent at the end that does a real piece of your job.
parts every working agent has
weekends, if you want a schedule
to start. Free tiers cover all of it.
“The hard part was never the code. It is deciding what the agent is allowed to do.”From The Guide
Ninety days, no computer science degree, and a portfolio you can build on your own time. A practical route into the job companies are quietly desperate for and have mostly forgotten to hire.
more likely to report ROI with full visibility into AI operating costs
have delayed or scaled back agent rollouts on cost
have “very clear” rules for when a human overrides AI
“An AI agent manager is not the person who builds the agent. It is the person who makes the agent trustworthy enough to run inside a real business.”From The Guide
Ten ways to put two AI models on the same problem so the second one catches what the first one missed. Why each works, and the one rule that decides whether you get better answers or just more expensive ones.
distinct reasons a second pass helps at all
rule that decides whether any of them work
extra subscriptions required. A second window counts.
“The second model isn’t there to be smarter. It’s there to be uncommitted.”From The Guide
How to make sure the AI-assisted work leaving your hands is real work. And what to do, without starting a fight, when someone hands you the other kind.
average time lost dealing with a single instance
estimated annual cost per 10,000 employees
don’t want to work with the sender again
“AI produces drafts. People produce work. You are not finished until the draft is something you can stand behind in a room.”From The Guide
I add a guide here whenever I finish writing one. Same deal every time: free, readable on the web or as a PDF, and the one email you already gave me gets you in.
If there's a decision you keep getting stuck on, email hi@davecto.com. The best guides start as someone else's question.
$ ls ~/resources | wc -l 40 $ ls -t ~/resources | head -3 ai-verification-checklist/index.html web vibe-coding-rules/index.html web solo-founder-mistakes/index.html web next-guide.pdf writing