Claude Code skills vs prompts: I measured 15 real skills
I measured 15 production Claude Code skills, file by file. 81% of the library stays out of the context window until it fires.
Build
July 27, 2026 · 6 min read
I gave the same job to three AI build tools: a working tip-split calculator you can use on your phone, built in one afternoon. I only ran one of them end to end and measured it, because two of the three need an account I won't create, so this is an honest contest where one contestant is on the stopwatch and two are judged on what they're documented to do. By the end you'll know which one to hand your next small app, whether you write code or not.
The three: Claude Code (a coding agent that lives in your terminal), v0 (Vercel's React generator), and Lovable (a no-code full-app builder). Same brief, three very different starting points. The honest catch: the tool I could actually run turned out to win on the part nobody talks about, and it's not the pretty screen.
The short version: pick the tool that matches how close to the code you want to sit. Here's who I'd hand the job to, before any detail.
That split holds up across every comparison guide I read, and it held up in the one build I actually measured. The rest of this piece is why, and where each one bites you.
I built the app for real with only one of the three, and I'm telling you which. The brief was a single-page tip-split calculator: enter a bill total, tap a tip percentage, set how many people, and see the per-person amount update live. I built it end to end with a terminal coding agent (the Claude Code side), because that's the only one of the three that needs no login and no account to run.
The result: one index.html file, 83 lines of plain HTML, CSS, and JavaScript, no build step and no dependencies. I checked the math outside the browser to be sure it wasn't just pretty: an $80 bill at 20 percent split four ways came back as exactly $24.00 each, and $53.50 at 15 percent across three people gave $20.51. The find that mattered came from testing the ugly input. When I set the number of people to zero, the app returned a plain "Need at least 1 person" instead of dividing by zero and printing $Infinity. That guard is the whole difference between a screen and an app, and building in the terminal is what let me add and verify it in one pass.
v0 and Lovable I did not run, and I won't pretend I did. Both put a login wall in front of the build, so for those two I'm reporting documented behavior from their own docs and from the comparison work others have published, and I'll flag every claim as documented rather than measured. If you want the fully-measured side of a same-brief experiment, my colleague did exactly that in our piece where two of us built the same website; this one is a hybrid on purpose, and I'd rather say so than fake two afternoons.
Claude Code wins when the app has real logic and you want to own the files. What is it: an agentic coding tool that runs in your terminal, where you describe what you want in plain English and it writes the code, creates the files, and runs the checks. What I did with it: built the entire calculator as one file in an afternoon, including the divide-by-zero guard that I verified returns an error message instead of $Infinity.
What it costs: Claude Code is not on the free Claude tier. You need at least Pro at $20/month (or $17/month billed annually) before you can run it, with Max plans starting higher for heavier use (check current pricing at claude.com/pricing, since the Max tiers weren't cleanly split when I last verified). Who it's for: anyone comfortable opening a terminal who wants code they fully control and can deploy anywhere. Who it's not for: someone who has never seen a command line and wants a visual editor, because there isn't one here.
Verdict: 8.5/10 for this job. It's the only contestant I measured, it produced a working app with a real edge-case fix, and the output is plain files with no lock-in. The $20 floor and the terminal are the price of that control.
v0 wins time-to-first-screen. What is it: Vercel's generator that turns a text prompt into working React UI, with a visual Design Mode to tweak the result and one-click deploy to Vercel. For a tip calculator, this is documented to be its home turf: a clean, accessible screen in minutes with no local setup.
What it costs: as of July 2026 the free plan gives $5 in monthly credits with a 7-message daily cap, which is documented as thin for a full afternoon of building. The paid Plus tier is $30/user/month, with Business at $100. There is no $20 "Premium" tier: I checked the live pricing page and it lists only Free, Plus, Business, and Enterprise. Who it's for: front-end folks already on Next.js and Vercel, and anyone who wants a good-looking screen without touching CSS. Who it's not for: someone who wants to keep the app off Vercel or needs deep custom logic in one file.
Verdict: 8/10, on documented behavior. For that money you get the smoothest path from prompt to deployed UI I've seen described, as long as you live in the Vercel world.
Lovable wins when the builder doesn't write code at all. What is it: a no-code tool that builds a full web app from plain English, front-end UI, a Supabase database, authentication, and even Stripe payments in one flow. For our calculator it's documented as overkill in the best way: it would happily add accounts and saved history you never asked for. This is the tool I'd hand a non-developer founder; our guide to building a website with AI walks the no-code route in general.
What it costs: the free plan gives 5 daily build credits (up to 30/month), enough to test and build a small demo but not to ship a product, per multiple reviews. Pro is $25/month (or $21 billed annually) with 100 monthly credits. The documented catch is credit burn: costs scale with request complexity, and credits get spent on failed attempts and bug fixes too, with one user reporting 30 credits for a single fix. Who it's for: non-developers who want the whole app, database and login included. Who it's not for: anyone who needs to import an existing project, since it only builds new apps from scratch.
Verdict: 7/10, on documented behavior. The reach is real and the no-code promise is genuine, but the unpredictable credit meter is the tax you pay for never opening a code editor.
Side by side the split is simple: Claude Code owns the logic, v0 owns the fastest polished screen, and Lovable owns the no-code reach.
| Claude Code | v0 | Lovable | |
|---|---|---|---|
| Type | Terminal coding agent | React UI generator | No-code app builder |
| I ran it? | Yes, measured | No, documented | No, documented |
| Free tier | No (Pro $20/mo min) | $5 credits, 7 msgs/day | 5 daily credits |
| Paid entry | $20/month | $30/user/month | $25/month |
| Best at | Real logic, owned code | Fast polished UI | Full app, no code |
| You need | Terminal comfort | A Vercel account | No code skills |
Prices as of July 2026. Check each tool's current pricing before you commit.
Pick by how close to the code you want to sit, not by which has the longest feature list. If you write even a little code and the app has logic that has to be right, start with Claude Code: it's the one I measured, and it's the one that caught the bug the brief was hiding. If you want a sharp-looking screen live on the web this afternoon and you're happy on Vercel, v0 is documented to get you there fastest. If you don't code and you want the whole thing, database and login and all, Lovable is the one to open first, with one eye on the credit meter.
The tools that lost my scenario didn't lose because they're bad. They lost because I asked for an app with a nasty edge case, and the tool I could open and inspect line by line is the one I could prove had handled it.
I measured 15 production Claude Code skills, file by file. 81% of the library stays out of the context window until it fires.
I built the same website three ways with AI in one afternoon. Here's the real decision tree for picking a coding agent, UI generator, or no-code builder.
AI vs human web development: I hand-built a one-page site, measured a real client tweak, and set it against what AI builders are documented to do.