7 Things You Can Build With One Prompt

Here are seven prompts, copy any one of them, paste it in your chat panel, and you'll have the thing running in a few minutes.

One quick tip before we get started.

Describe the thing, not the task

Here's a prompt that fails, and it fails so quietly that most people never work out why:

Log a workout: exercise, sets, reps, weight, date.

Read it as an instruction and you'll see it. You've just asked the assistant to go and log a workout. Not to build you something that logs workouts. It might guess what you meant. It might also hand you a page with one fake workout typed into it, which is a strange thing to receive and hard to explain.

Now the same idea, fixed:

Build a workout log where I can record exercise, sets, reps, weight and date.

Two words — Build and I can — and there's nothing left to misread. You're describing a thing that should exist, and who uses it.

That's the whole rule. Every prompt below starts with what to build and describes each feature from your side: where I can, let me, it should. Once you've noticed it you'll spot the broken version everywhere, including in your own drafts.

1. A landing page

The obvious one, so let's get it out of the way. It takes about four minutes and it's the least interesting thing on this list.

Build a one-page site for Ridgeway Mobile Dog Grooming, a one-van business in Austin. It needs the services with prices, a short bit about me, and a big Book button that's visible without scrolling. Warm and friendly — cream background, deep green accents, big photos, rounded corners. Not corporate.

Swap in: your business, your town, your one action. The named business matters more than you'd think. "A dog grooming site" gets you a template with a placeholder name in it. "Ridgeway Mobile Dog Grooming, one van, Austin" gets you something that reads like a real company.

2. A task board that remembers

Build a task board with To do, Doing and Done columns. I want to drag cards between them, add a new task with a title and a note, and delete one I'm finished with. My tasks should still be there when I close the tab and come back tomorrow.

Why the last sentence is there: without it you get a board that looks perfect and forgets everything the moment you reload. Saying "still be there when I come back" is how you ask for storage without knowing the word for it.

3. A movie watchlist

Build a watchlist where I can add films with a title, the year, and where they're streaming. Let me mark one as watched, give it a score out of 10, and filter to show only the ones I haven't seen yet. Make it dark and poster-led, like a cinema listing.

Swap in: books, restaurants, albums, places to visit. It's the same shape every time — add a thing, mark it done, rate it, filter it. Change the nouns and you've got a different app.

4. A workout log with a chart

Build a workout log where I can record an exercise, sets, reps, weight and the date. It should chart my total weekly volume over time and show my best lift for each exercise. I'll be entering this on my phone at the gym, so keep the form short.

Why the chart is worth asking for: a list of numbers is a spreadsheet. A line going up is a reason to keep using it. Ask for the chart explicitly — you'll rarely get one otherwise.

5. A food diary

Build a food diary where I can add a meal with what I ate, rough calories, and how I felt afterwards. Show me today's running total and the last seven days. I'm using this one-handed while I'm eating, so make the buttons big and the form quick.

Why "one-handed" earns its place: it's a design brief disguised as a fact about your life, and it does more than "make it mobile friendly" ever will. Telling the assistant how you'll use something shapes the layout far more than telling it what device you're on.

6. An actual arcade game

Build a game of Snake. Arrow keys on a computer, swipe on a phone. It should speed up as the snake gets longer, and keep a top five high score table where you enter three initials, like an arcade cabinet.

Try this next: Breakout, Tetris, Simon, Connect Four, a typing speed test. All of them are the same request with different rules, and all of them work.

7. A 3D game

Build a 3D game: a ball rolling down a neon tunnel. Arrow keys to steer left and right, obstacles to dodge, and score me by how far I get before I hit one. Speed it up the longer I survive.

Notice what isn't in there: any mention of how 3D works. You describe the game; the assistant handles the rest. There's nothing to download and nothing to install — it opens in a browser like any other page. It just happens to be in 3D.

This is the one people don't believe until they've done it, so if you only try one, try this one.

The bit after you build it

All seven of these are only half finished while they're sitting in a tab. Publish it — it goes live on your own address with the padlock already on, and you can send someone the link. Every edit is saved as you go, so publishing early costs you nothing. If tomorrow's version is worse, you go back to today's.

That's genuinely the part most people skip, and it's the only step on this list that changes anything.

Two things worth knowing

Ask for one thing at a time. Every prompt above is a first message, not a whole project. Get it built, look at it, then ask for the next change on its own. Ten requests in one message gets you nine half-finished ones.

Say what's wrong, specifically. "Make it better" gives the assistant nothing to work with. "The buttons are too small on my phone and the date field is above the exercise name, swap them" gets fixed in one go.

All seven of these run on the free plan — one site, no card, and enough credits to build something and change your mind a few times.

Start free at gledit.app →