build with ai

40 articles · newest first

Hand-drawn editorial illustration of a table with eight different small tools laid out, a hand hovering undecided above them

Which vibe coding tool? Here's what each one says it is, in its own words.

Lovable, Bolt, v0, Replit, Google AI Studio, Cursor, Claude Code and Antigravity all get lumped together. Their own documentation describes two different kinds of tool. A table of each one's own words, and two questions that narrow the choice.

Aliteq Team · Oct 3 · 7 min

Flat illustration of a person speaking a sentence that turns into a three-layer stack of a screen, a server and a database

Build

You typed a sentence into Lovable and an app appeared. Here's where your code, data and bill actually live.

Lovable describes itself as a platform that builds and deploys web apps from plain English. Its own docs say where the app is hosted, what the built-in backend is, where your code sits and how you pay. A plain-language tour, from the docs.

Aliteq Team · Oct 3 · 6 min

Hand-drawn editorial illustration of one large key with many fine threads fanning out to a crowd of small figures, each holding a glowing orb

Build

Google AI Studio will vibe code a full app for you. Two lines in its docs to read before you share it.

Google's own documentation uses the words "vibe code" for AI Studio's Build mode. It also says what happens to your API key when you deploy, and who can see your code when you share. Here's what it builds, and the checks Google's pages leave to you.

Aliteq Team · Oct 3 · 7 min

Flat illustration of a person with a magnifying glass over a wall of small identical app windows, a few marked with a coral open padlock

Build

Someone scanned 30,998 vibe-coded apps. Here's what the 57% "open Supabase" number really means.

A headline says more than half of vibe-coded apps leave their database open. The report behind it is more careful than the headline, and so is the number: what it measured, what it didn't, and the one check that matters for your app.

Aliteq Team · Oct 3 · 8 min

Hand-drawn editorial illustration of a blueprint sheet pinned above a workbench where a small robot assembles a simple app following it

Build

Spec first, then prompt: the one-page plan for when your AI keeps rewriting your app

GitHub says the fix for "it looks right but doesn't quite work" isn't a better prompt, it's a spec. Here's what spec-driven development means in plain words, and a one-page template you can use in any builder.

Aliteq Team · Oct 3 · 7 min

Flat illustration of a person at a crossroads looking up at three signposts, each topped with a different simple icon

Build

Your Lovable app works. Should you move to Cursor or Claude Code?

Three tools get compared constantly, but they aren't three versions of the same thing. Here's what each one says it is in its own docs, the real decision hiding underneath, and when staying put is the right call.

Aliteq Team · Oct 3 · 7 min

Hand-drawn editorial illustration of a long scroll unrolling past a small spotlight that only lights a narrow stretch of it

Build

Your AI forgot how your app works an hour in. That's a context problem, and it's fixable.

It contradicts a decision from earlier, re-breaks something it fixed, renames things you never asked it to rename. It isn't being careless — it can't see the early part of the conversation anymore. Tap the meter, then fix it the way the pros do.

Aliteq Team · Oct 3 · 7 min

Flat illustration of a person peeling an old sticker off a laptop and holding a fresh coral one — a new name for the same machine

Build

Is vibe coding dead? What Karpathy's "agentic engineering" means if you don't code

The man who coined "vibe coding" now calls it passé and has a new name for the grown-up version. Before you wonder whether what you're doing is wrong: here's what he actually said, in his own words, and what it changes for you.

Aliteq Team · Oct 3 · 6 min

Hand-drawn editorial illustration of a wall of labelled term cards pinned up like a glossary, one card highlighted

Build

Vibe coding or vibecoding? And the other words for building with AI in 2026

Two words or one? And what do "agentic engineering," "context engineering" and "spec-driven development" actually mean? A plain glossary of every AI-coding term in circulation, each with who coined it and when.

Aliteq Team · Oct 2 · 6 min

Hand-drawn editorial illustration of a person speaking a sentence that turns into a small finished app on a screen

Build

What is vibe coding? The 2025 word of the year, explained

You describe an app in plain English and an AI writes it — that's vibe coding, the term Collins named its 2025 Word of the Year. Here's where it came from, what it looks like in a tool like Lovable, and the one thing the definition quietly warns about.

Aliteq Team · Oct 2 · 7 min

Build

Claude Code for vibe coders: what it does that Lovable and Bolt don't

In the US, people search "claude code" about ten times more than "vibe coding" — but if you've only used a visual builder, it's not obvious what it even is. Here's Claude Code explained for someone who started in Lovable.

Aliteq Team · Oct 2 · 7 min

Hand-drawn editorial illustration of two figures at a screen of code — one with eyes closed, one reading closely with a magnifier

Build

Vibe coding vs agentic engineering: the difference is whether you read the code

"From vibe coding to agentic engineering" is one of the fastest-rising searches of 2026. The honest difference between the two terms is smaller — and more useful — than the jargon makes it sound.

Aliteq Team · Oct 2 · 7 min

Hand-drawn editorial illustration of a pencil laid down beside a glowing terminal, a small robot taking over the writing

Build

The creator of Rails stopped writing code by hand. What "pencils down" means if you vibe code in Lovable.

In late September, DHH told a room of 1,200 developers that writing code by hand is now the exception. If you build apps by describing them to Lovable or Bolt, here's what actually changed for you — and what didn't.

Aliteq Team · Oct 2 · 7 min

Hand-drawn editorial map of a vibe coder's journey from a built app to launch, with signposts along a winding path

Build

You vibe-coded an app. Here's everything to check before real people use it.

You built it by describing it to Lovable, Bolt, Cursor, Replit or v0 — the hard part's done. This is the map of the rest: understand what the AI built, fix the errors you'll Google, ship it so strangers can't break it, and handle the day a real customer shows up.

Aliteq Team · Oct 2 · 9 min

Flat illustration of a person holding two keys, a small public one and a large master key kept in a pocket

Build

Your Supabase anon key is visible in the browser. Is that a problem?

Short version: the anon (publishable) key is meant to be public — as long as Row Level Security is on. The key that must never leak is the other one. Here's how to tell which you're looking at.

Aliteq Team · Sep 26 · 6 min

Isometric diorama of data flowing through pipes, one narrow section causing a backup

Build

Your Lovable app got slow as the data grew. Three usual reasons.

It was snappy with ten rows and crawls with ten thousand. Almost always it's one of three things — a missing index, fetching everything then filtering in the browser, or no caching — and none needs you to read code.

Aliteq Team · Sep 26 · 6 min

Editorial illustration of a document being turned away at a guarded doorway into a filing cabinet

Build

Your app says "new row violates row-level security policy". Here's what it's protecting.

It's not a bug — it's your database refusing to let the wrong person write a row. Why the error shows up the moment security is on, and the right way to fix it (never "disable RLS").

Aliteq Team · Sep 26 · 6 min

Flat illustration of a person standing beside a large padlock and shield, ticking a short checklist

Build

The 6 things to fix in your Replit app before anyone sees it

Before you share a Replit app, six things to check so strangers can't read each other's data or run up your bill — including the one backup check behind Replit's most infamous 2025 data-loss story.

Aliteq Team · Sep 26 · 7 min

Editorial illustration of a hand over a generated app-interface mock ringed by six small padlock and shield check marks

Build

The 6 things to check in your v0 app before you ship

v0 turns a prompt into a real Next.js app on Vercel — but who's allowed to see your data is a setting you have to confirm. Six things to check before you ship, starting with the one Next.js setting that quietly puts keys in the browser.

Aliteq Team · Sep 26 · 7 min

Editorial illustration of a large text cursor beside a shield while a hand reviews lines of AI-written code

Build

The 6 things to check in your Cursor-built app before you ship

Cursor works in the project you bring, and what that project connects to is your call — so every security check is yours. Six things to confirm before you ship, and the one (reading the code) that matters most.

Aliteq Team · Sep 26 · 7 min

Flat illustration of a person beside a freshly built app running a checklist of padlocks on a workbench

Build

The 6 things to fix in your Bolt app before anyone sees it

Bolt built it and its scan catches two of the big risks — but four checks are still yours before you share the link, so nobody can read each other's data or run up your AI bill.

Aliteq Team · Sep 26 · 7 min

Editorial illustration of a person holding a magnifier over an app window ringed by small padlock and shield check marks

Build

The 6 things to fix in your Lovable app before anyone sees it

You built it by describing it to Lovable — now, before you share the link, six things to check so strangers can't read each other's data or run up your bill. Lovable helps with some; these are the rest.

Aliteq Team · Sep 26 · 7 min

Editorial infographic of a wide desktop layout reflowing into a tall phone layout with a viewport tag highlighted, near-black background with indigo-violet and a coral accent

Build

"Make this page work on phones": the one tag most prompts forget

Ninety percent of "it's tiny on mobile" is one missing tag. Here's "make this page work on phones" three ways, with the real code — from a lonely media query to a proper mobile-first layout.

Aliteq Team · Sep 26 · 6 min

Realistic painterly illustration of a single glowing envelope rising into a dawn sky over a quiet skyline, deep indigo with a warm coral sunrise accent

Build

"Send a daily summary email": the prompt that avoids the spam list

A naive "send a daily email" loop fires at the wrong time, breaks on one bad address, and can email someone a hundred times. Here's the request three ways, with the real code, and the guards that keep you off spam lists.

Aliteq Team · Sep 26 · 6 min

Isometric diorama of a grid of table rows each with its own small lock, one row highlighted, near-black background with indigo-violet and a coral accent

Build

"Write the RLS policy for my users table": three prompts, three outcomes

Row Level Security is deny-by-default, so the danger isn't forgetting to lock a table — it's a lazy policy that quietly unlocks all of them. Here's the request three ways, with the real SQL each produced.

Aliteq Team · Sep 26 · 6 min

Editorial infographic of a safe checkout flow: browser to a server holding a locked key, then a verified webhook, near-black background with indigo-violet and a coral accent

Build

"Add a Stripe checkout button": the prompt that leaks your secret key

The naive way to vibe-code a Stripe button puts your secret key in every visitor's browser. Here's the same request three ways, with the real code — and the one rule that separates a demo from a safe checkout.

Aliteq Team · Sep 26 · 6 min

Isometric diorama of a glowing key turning in a login card, near-black background, indigo-violet with a small coral accent

Build

"Add login with Supabase": the same prompt, three ways

Every vibe coder types "add login with Supabase" and gets working code. Here's what changes when you ask for it vaguely, specifically, and with the guardrails spelled out — with the real code each version produced.

Aliteq Team · Sep 26 · 6 min

Isometric illustration of a workshop pegboard holding hand tools arranged from a tiny screwdriver up to a large drill, a hand reaching to choose the right-sized one

Build

You're paying for the smartest model to rename a button

Most AI tools let you pick a model, and the wrong pick burns time and money. When a fast, cheap model is plenty, and when a slow, thinking one earns its keep.

Aliteq Team · Sep 26 · 5 min

Realistic painterly illustration of a lone figure at a fork in a trail at dusk, one path overgrown and tangled, the other a clean fresh road ahead

Build

Stop prompting patch-on-patch — sometimes a fresh spec beats a fifth fix

The vibe-coder trap is fixing AI code until it's a knot. When a clean rewrite wins over another patch, shown with a real before-and-after and a simple rule for deciding.

Aliteq Team · Sep 26 · 5 min

Flat illustration of a calm person holding a large magnifying glass over a screen of code, one line gently highlighted

BuildInteractive

The AI says "I fixed the login." Here's how to check what it actually changed

You don't need to write code to vibe code, but you do need to read it. Three things to look for in a diff — logged secrets, scope creep, silent data changes. Try reading one.

Aliteq Team · Sep 26 · 5 min

Isometric diorama of a small workbench where a draft page moves under a magnifying glass and comes out stamped with a green check, arrows looping back to the start

Build

The AI's first answer is a draft, not a verdict — make it attack its own code

The habit that separates people who ship safe apps from people who ship bugs: generate, then ask the model to break what it just wrote. Shown with a real before-and-after.

Aliteq Team · Sep 26 · 5 min

Editorial infographic showing a vague scribbled sticky note on the left transformed by an arrow into a neat numbered specification checklist on the right

BuildInteractive

The words you add to a prompt are the product — watch one go from vague to shippable

The single biggest upgrade to vibe coding is treating a prompt as a spec. See the same request go vague → specific → constrained, with the real code each version produced. Try building one.

Aliteq Team · Sep 26 · 5 min

Isometric diorama of a turnstile gate letting a small, steady number of figures through per minute while a crowd waits their turn behind it

BuildInteractive

One script, 10,000 fake signups overnight: the guardrail most vibe-coded apps ship without

A rate limit caps how many requests someone can fire in a window, so bots, bugs and abuse can't swamp your app or your bill. Why every public endpoint needs one. Tap to watch it hold.

Aliteq Team · Sep 26 · 4 min

Photographic wide shot of a dark, hazy data-center hall, rows of server racks lit only by small green and red indicator lights, conveying large scale

BuildInteractive

It worked with ten users. Then a hundred showed up at once.

What happens to a vibe-coded app when it suddenly gets popular, the two ways to handle it, and why "works for ten" isn't "works for ten thousand". Tap to add users.

Aliteq Team · Sep 26 · 4 min

Flat illustration of a friendly worker taking numbered task tickets from a tidy waiting line and completing them one by one at a desk

BuildInteractive

Don't make the user wait for the slow part — hand it to a queue

Why a vibe-coded app should push slow work to a background job instead of freezing the user, and how queues keep an app responsive when traffic spikes. Tap to load it up.

Aliteq Team · Sep 26 · 4 min

Editorial infographic contrasting a slow first request that computes an answer with a fast repeat request served instantly from a labelled cache box

Build

You fixed the typo. Visitors still see the old version. Here's why.

A cache keeps a ready-made copy so pages load instantly — most of the web's speed, and the classic bug where old data won't go away. What its lifetime (TTL) controls.

Aliteq Team · Sep 26 · 4 min

Realistic painterly illustration of a lone courier racing along a very long winding road at dusk, a distant city glowing far ahead

BuildInteractive

Your app is fast for you and slow for everyone else — the reason is geography

Latency is the wait between a request and its answer, and distance is the biggest cause. Why far-away users feel the lag, and the one thing that fixes most of it. Tap the ladder.

Aliteq Team · Sep 26 · 4 min

Isometric diorama of a small monitoring desk with a screen showing a scrolling list of log lines, one highlighted in red, and a magnifier beside it

Build

Your app broke and you have no idea why. It left you a note.

When a vibe-coded app suddenly fails, the error log is the first place to look. How to read one, and why "it just broke" almost never means what it says.

Aliteq Team · Sep 26 · 4 min

Isometric diorama of an open drawer holding neatly labelled cards of data, one card lifted out to show it is made of tiny numbered blocks

Build

Every photo, row and document your app saves is one thing: a named box of bytes

What a file actually is, why its type matters, and how it differs from memory that forgets the instant the power goes off.

Aliteq Team · Sep 26 · 4 min

Editorial infographic of the fetch, decode, execute loop as three labelled stages in a circle with arrows returning to the start

Build

The chip reading every instruction, billions of times a second

The CPU does the actual work while you vibe code. The tiny fetch-decode-execute loop it runs, how it differs from a GPU, and why it's where speed and cost come from.

Aliteq Team · Sep 26 · 4 min