Getting started — Marai Neesu AI Prompts
The pack builds Marai Neesu one prompt at a time. Each prompt describes one part of the site exactly — sizes, spacing, text styles, motion, content — and names the screenshots that show how it should look. This guide takes you from the download to a finished site.
What you need
Section titled “What you need”- An AI tool that writes and runs a website: a chat builder (Lovable, Bolt, v0, Replit) or a coding agent (Cursor, Claude Code, Codex, Windsurf). Notes for each are in Notes for each tool.
- A plan with room for about 30 to 40 messages: the 22 prompts, plus a few follow-ups to fix details. Free plans usually run out before the end.
- A web browser to open
Prompts.html.
What is in the pack
Section titled “What is in the pack”| Folder or file | What it is for |
|---|---|
Prompts.html |
Open this first: every prompt with a Copy button, the screenshots to attach, and your progress |
prompts/ |
The same prompts as Markdown files (01-foundation.md … 22-finish.md) |
references/ |
Screenshots of every page layout: home-desktop-1.png (1200 px wide, top to bottom), home-tablet-1.png (810 px) and home-phone-1.png (390 px wide, strips side by side) |
content/ |
The demo text as JSON: site.json, pages/*.json, collections/*.json |
assets/ |
images/ (placeholders at the right sizes, the tool logos, the sample client logos and the social icons) and icons/ |
checklist.md |
Section heights per page, for agents that can measure what they built |
DESIGN.md |
The design tokens and style rules in one file, for coding agents |
The order of the prompts
Section titled “The order of the prompts”| # | Prompt | What it builds |
|---|---|---|
| 1 | Foundation | The project, the design tokens (colours, text styles, spacing, motion), the rules for breakpoints, images and the two forms, and the icons |
| 2 | Components | Buttons, the e-mail roll, the menu links, Go Back, the logo, the hamburger, breadcrumbs, the social tiles, section titles and dividers, the project, product, post, service, testimonial, course, module, experience, stack and CV cards, the status chip, the ticker, the slideshow, the accordion, rich text, form fields, checkboxes and the submit button, the clock and the year — everything the pages are made of |
| 3 | Layout | Header (with its desktop scroll look and the phone menu) and footer, the site details (site.json) and the words several pages share (pages/shared.json) |
| 4–8 | Content | The collections: social profiles, projects, services, testimonials and products; tools and work experiences; the posts (in four parts) |
| 9–21 | Pages | One prompt per page layout: Home, About, Projects, Project, Services, Courses, CV, Products, Product, Blog, Post, Contact, 404 |
| 22 | Finish | Browser titles and descriptions, tab icon, share image, sitemap and robots, a last check of every page |
Each prompt builds on the ones before it, so keep the order. The Product and Post prompts use page copy saved by the Products and Blog prompts before them.
With a chat builder
Section titled “With a chat builder”
- Open
Prompts.htmland choose Lovable, Bolt, v0, Replit at the top. - Start a new, empty project in your tool.
- Copy prompt 1. In the tool’s message box, attach the screenshots listed on the card (drag them from the
referencesfolder, or use the attach button), paste the prompt and send it. - Wait until the tool has finished and the preview works. Compare it with the screenshots; if something is off, ask for that one fix in a short message (“On desktop, the Contact button should sit at the right end of the header, as in the screenshot”).
- Tick the prompt in
Prompts.htmland go on with the next one.
Before the page prompts, add the pack’s images to the project: upload the assets/images folder into
public/images/. The prompts expect them there, and the pages only take the right shapes once they are.
The Content prompts (4–8) are long on purpose: they carry the demo text of every project, service, testimonial, product, tool, job and post. Send them as they are. The tool saves them as files and shows nothing new yet — that is expected. So is this after the Layout prompt: the footer’s links lead to pages that later prompts build, so until then they open the 404 placeholder.
Some page prompts list more screenshots than a tool takes in one message (Home has four desktop slices and three phone images). Attach the desktop ones first; if your tool has a limit, send the rest in a short follow-up (“Here are the phone screenshots for the same page”).
With a coding agent
Section titled “With a coding agent”- Copy the whole pack into your project folder and name it
marai-neesu/. - Open
Prompts.html, choose Cursor, Claude Code, Codex, Windsurf at the top, and copy the kickoff prompt. - Send it to the agent. It copies the content, the images and the icons into the project, then works through the prompts in order, opening the screenshots for each page. The Content prompts are skipped — the files are already there.
- Check each page as it lands, in the browser, at phone and desktop width. Agents that can run a browser can also
compare their result with
marai-neesu/checklist.md;marai-neesu/DESIGN.mdgives them the design rules in one file.
Checking a page
Section titled “Checking a page”- Put the site next to the page’s screenshots at 1200, 810 and 390 px wide: same sections, in the same order, with the same alignment and spacing.
- Resize the window slowly from phone to desktop: the layout changes at 810 px and 1200 px and never scrolls sideways.
- On a computer, hover the buttons, menu links, footer links, the e-mail, the social tiles and the cards; on Home, wait for the roles to roll and watch the service photos move under the pointer; on desktops, scroll down and up to see the header step aside and come back; open the course modules and the questions; press “Load More” on the Blog; send each form in demo mode; use Go Back on a project, product or post page.
Photos are grey placeholders until you add your own — see Making it yours. Nothing on the site rises or fades in as you scroll, and pages change without a transition: that is the design.