NC
How to write a good AI prompt — 7 rules with examples
✍️
Guides7 Jun 2026 · 8 min read

How to write a good AI prompt — 7 rules with examples

The difference between 'make me a website' and an app that actually works is the prompt. 7 concrete rules we learned from thousands of generations.

The same AI tool gives two people completely different results — one a half-baked site, the other a working app. The difference isn't luck, it's the prompt: how clearly you describe what you want. Here are 7 rules we distilled from thousands of generations on nocodeon.

1. Say WHAT it does, not HOW to build it

You don't need to know coding. Don't write “use React and Firebase.” Write what the user sees and does: “A page where I enter an expense, the app sums it and shows totals per category.” We pick the tech.

2. List the screens and buttons

An app is a set of screens. List them and you get exactly that:

Three screens:
1. Home — "New measurement" button
2. Entry — fields: date, weight (kg), note
3. History — list of all entries + monthly chart

3. Say where the data lives

If you want data to survive moving from phone to laptop, say it explicitly: “Data in the database (nocodeon.db), not just the browser.” Otherwise the AI picks the simplest option — localStorage — and the data disappears on another device.

4. Ask for it to work on mobile

Most people open the app on a phone. Add one sentence: “Must work on mobile too — touch controls, buttons big enough for a finger, no horizontal scroll.” For games ask for on-screen buttons, not just the keyboard.

5. Give example content

Instead of “a general knowledge quiz,” give 2-3 real questions. Instead of “an image gallery,” say how many images and the layout. A concrete example beats ten adjectives.

6. One feature per message

Don't do everything at once. Basic version first, then build up: “Now add that each entry can be deleted.”That way it's easier to see where something went wrong and act precisely.

7. Say what's wrong, specifically

If the result isn't good, don't just write “it doesn't work.” Write exactly what: “The Save button doesn't respond on mobile” or “The list doesn't refresh after adding.” The more precise, the faster the fix.

Bad vs good prompt — example

BadGood
Build me a gym appA workout tracker: an entry screen (exercise name, kg, reps), history by day, a progress chart. Data in the database. Works on mobile.

A good prompt isn't longer because it's more complicated — it's longer because it's clearer. Next time try writing three sentences instead of one, and the difference will surprise you.