Full Prompt Guide
What kind of prompt actually works well on BanglaCodes?
A good prompt covers four things: who it is for, what it should contain, how it should look, and any special conditions. Write in Bengali, but keep technical terms in English. When asking for a change, say exactly which part you mean, so you keep control and nothing gets lost.
Why this chapter
The previous chapter covers the essentials of a good Prompt. This one is the full list: everything BanglaCodes can do, with the way to ask for each and a sample. Look things up as you need them, there is no need to read it all in one go.
1. The shape of a Prompt
To get the best result, tell it four things:
| What | Example |
| Who it is for | "For my sweet shop" |
| What goes in it | "6 sweets with prices, phone number at the top" |
| How it should look | "Red and white colours, round buttons" |
| Any special condition | "It should look good on mobile" |
Sample:
Build a one page site for my sweet shop "Modhubon". The shop name and phone number at the top. In the middle, 6 sweets with their names, a spot for a photo and the price. At the bottom, the address and a map. Colours red and white, round buttons. It should look nice on mobile.
2. Language: Bengali or English?
Say it in Bengali. The whole system was built for Bengali. Technical words are better written in English, like button, form, database, API. Mixing the two is completely fine:
Build a contact form with fields for name, email and message.
Say separately which language the text inside the site should be in, otherwise it will be in Bengali:
Put the text in English, just keep the design in a Bengali style.
3. What you can ask it to build
Anything that runs in a browser. BanglaCodes builds with vanilla HTML, CSS and JavaScript, so nothing needs installing.
Websites: portfolio, shop page, restaurant menu, wedding invitation, event page, coaching centre, landing page, blog layout
Tools: calculator, ledger, invoice maker, prayer timetable, unit converter, QR code generator, timer, budget tracker
Games: Snake, quiz, memory game, tic tac toe, cricket scoreboard, 3D games (with three.js)
Other things: slides, animations, SVG logos, charts and graphs, flashcards, CV
What it cannot do yet: server side code (PHP, Python backend), a database of your own to run, a login system that stores passwords, taking payments. If you need those, you can ask it to plug in an outside service such as Google Form or Firebase. Keeping the app's own records the same on every device needs nothing extra, though: the Business plan has cloud data.
4. Prompts for editing
When you ask for a change after it is built, say which part you mean:
| Weak | Better |
| "Make it nicer" | "Make the name at the top bigger and bolder" |
| "It doesn't work" | "Nothing happens when I press the add button" |
| "Change the colour" | "Change the button colour from green to orange" |
If you ask for many things at once it will do them all, but asking one at a time gives you more control.
A few handy editing Prompts:
Fix how it looks on mobile Add a menu bar at the top Make the image spots round Increase the text size a little, it is hard to read Switch the whole thing to dark mode Add a contact form at the bottom
5. Prompts about images
Asking for an image (the "Build" tab of the image panel): describe the scene, and say what style you want too.
Sunrise over a green paddy field, flat vector illustration A cup of tea on a wooden table, shot from above A simple logo for a bookshop, cream coloured background
Showing a screenshot: paste the image and say how much of it to take.
Build a layout like this image, but keep my colours Fix the part that looks broken in this screenshot
6. Prompts for plan mode
For a big job, pick "Plan" above the writing box and write out the whole request in one go. The AI will show you the steps, and then you can ask for changes:
Drop step 3, I don't need it Swap 2 and 4 Looks good, go ahead and build it
7. How to write app rules
In the "rules" box, write short instructions, each on its own line:
All headings should be dark green Buttons are always round As few English words as possible Every page has the phone number at the bottom
Write the lasting design decisions here, not one off jobs.
8. Prompts for learning in chat
"Explain what a for loop is in the simplest way, with an example" "Why am I getting this error: Uncaught TypeError..." "What is this part of my code doing, line by line" "Make me a 7 day routine for learning HTML"
9. Mistakes everybody makes
Saying too little: leaving it to the AI's guesswork with "build a site". Two extra lines gives you a ten times better result.
Twenty jobs at once: if you ask for everything in one Prompt, something may get left out. Break it up.
Assuming it forgot: the AI remembers what came before. Unless you clearly say "forget the last one and build it fresh", it will keep working on top of the old one.
Vague adjectives: "professional", "nice", "modern" mean different things to different people. Name the colours, fonts and spacing and the result is certain.
10. When you get stuck
- Press the "Tidy up my Prompt" (✨) button and the AI will organise what you wrote
- Go to chat and ask "what do I need to say to build this?"
- Start from a ready made template and keep changing it
- Go back to an earlier version and try saying it a different way
Beginner questions
Do I have to memorize these prompts?
No. They are samples, change them into your own words. Copy one, swap the names, prices and colors, and it becomes yours.
What if I want something not in the samples?
Of course it works. Samples only help you start. Write whatever is in your head, and if more detail is needed the AI asks for it.
Should I say everything at once or in pieces?
Break big things up: the core first, then the rest one by one. Small steps mean fewer mistakes and less Token.