BackGuides

Base44 prompt guide: templates for building websites and apps

Build a clearer Base44 brief with seven complete prompt templates for websites, dashboards, booking flows, internal tools, prototypes, and focused fixes.

Panagiotis Visilias

Nov 17, 2026 · 9 min read

Answer in 2 sentences

You can use Base44 to build websites and apps by describing the result you want in natural language, then reviewing and iterating on the generated result. Strong Base44 prompts specify the audience, screens, data, interactions, constraints, and observable checks instead of relying on a visual adjective or a list of features alone.

What should every Base44 prompt include?

Whether you searched for “base44 prompts” or “base 44 website builder,” start with one complete user journey. A site that looks finished may still have buttons that do nothing, forms without error handling, or screens populated with invented business claims.

Use this structure checklist before generation:

  • Purpose and audience: who uses the result and what they need to accomplish.
  • Pages and navigation: the first screen, destinations, and primary action.
  • Data: fields, example records, ownership, and which values are placeholders.
  • Behavior: what happens after each important click or submission.
  • Design: specific layout and style constraints, including narrow screens.
  • States: empty, loading, invalid input, success, and failure.
  • Boundaries: what to defer and which integrations need confirmation.
  • Checks: a short journey you can perform to judge completion.

The templates below describe desired outputs, not promises about built-in capabilities. If a requested integration or backend behavior is unavailable, ask the builder to identify the gap and leave a clearly labeled prototype rather than simulate a working service invisibly.

What is a complete landing-page prompt?

Copy this prompt: Build a responsive landing page for a fictional appointment reminder service called ClearSlot, aimed at independent tutors. The primary action is joining a waitlist. Include a headline explaining the service, three practical benefits, a three-step workflow, an FAQ, and a waitlist form with name and email. Use calm blue accents, readable type, generous spacing, and a single-column mobile layout. Do not invent customer logos, testimonials, usage numbers, or pricing. Label all business copy as draft content for owner review.

The form must validate email and explain success and failure. If no real submission destination is configured, show a clearly labeled demo state and do not claim registration succeeded. Keep navigation links connected to real sections. Check that the primary action reaches the form, keyboard focus is visible, and no content overflows on a narrow screen. Defer payment, accounts, and analytics.

Replace the fictional brand and audience with your own details. Supply approved copy when factual claims matter, especially for testimonials or regulated services.

Which prompt works for a SaaS dashboard prototype?

Copy this prompt: Create a SaaS dashboard prototype for a small customer-support team. Include an overview, ticket list, and ticket detail screen. Use synthetic tickets with subject, status, priority, owner, and created date. Mark the data as demo data. The overview should show counts derived from those same records, with labels explaining what is counted. Let users filter by status and owner, open a ticket, change its status locally, and return to the filtered list.

Use a compact sidebar on wide screens and accessible navigation on mobile. Include empty-filter results and an obvious reset action. Preserve filter choices while opening and closing details. Do not add authentication, production persistence, or third-party helpdesk connections yet. Show which interactions are temporary prototype behavior. Verify that changing a ticket updates the list and overview consistently, and that resetting filters restores all demo records.

This prompt links the summary cards to underlying records. That gives you a concrete check instead of accepting decorative numbers as a functioning dashboard.

How do you prompt a booking site without hiding scheduling rules?

Copy this prompt: Build a booking-site prototype for a fictional pottery studio. Visitors choose a class, view a date and available time, enter their name and email, and review a booking summary. Classes have a title, duration, capacity, and location. Use synthetic availability and visibly label the flow as a demo. Show the studio timezone wherever times appear. Include a class list, booking form, review step, and confirmation preview.

Require class, time, name, and valid email before the review step. Allow users to go back without losing values. Display unavailable sessions as unavailable rather than allowing selection. Do not collect payments or send emails. Do not claim a seat is reserved until a real booking backend exists. Explain what production work remains for capacity checks and concurrent bookings. Verify invalid email, changing a class after selecting a time, and an empty availability state.

For a live booking system, settle capacity enforcement, cancellation rules, and timezone handling before launch. A convincing confirmation screen does not establish that inventory is protected.

What should an internal-tool prompt say about permissions?

Copy this prompt: Prototype an equipment request tool for an office team. Include a request list, new-request form, request details, and a reviewer queue. Each record has requester, item, reason, requested date, status, and reviewer note. Use synthetic names and records. Let a requester draft and submit a request; let a reviewer approve or decline it with a note. Include filters for pending, approved, and declined requests and a clear empty state.

For this prototype, use a visibly labeled role switcher to demonstrate the two views. State clearly that the switcher is not authentication or access control. Do not connect company systems or use personal employee data. Keep submitted requests readable after review and prevent accidental duplicate submission in the interface. Verify the requester journey, reviewer journey, and a declined request with an explanatory note. List the server-side authorization and persistence work required before real use.

Use a role demonstration to clarify requirements, then test actual authorization separately when implementing production access.

How can you scope a game prototype?

Copy this prompt: Build a small browser memory-card game prototype with six matching pairs. Use simple geometric symbols and no external assets. Include a start screen, game board, move count, restart button, and completion message. A move consists of revealing two different cards. Matching pairs remain visible; unmatched pairs turn back after a short pause. Prevent a third selection during that pause. Shuffle the board for each new game.

Make cards usable by keyboard with visible focus and descriptive labels. Use a layout that fits a narrow screen without horizontal scrolling. Include brief rules before play and keep the restart action available. Do not add accounts, leaderboards, purchases, multiplayer, or tracking. Verify that clicking the same card twice does not count as a pair, all pairs can be completed, restarting resets progress, and the completion message appears only after the final match.

Small rules create useful test cases. Start with one playable loop before asking for effects, levels, or additional modes.

What does a focused fix-and-iterate prompt look like?

Copy this prompt: Fix the booking form's date-change behavior. Reproduction: select a class, date, and time, then change the date. The previously selected time remains in the summary even when unavailable on the new date. Expected behavior: clear an incompatible time selection, explain that a new time is needed, and prevent continuing until a valid time is chosen. Inspect the current implementation before making changes.

Preserve the existing layout, colors, class data, and other form behavior. Do not rebuild the page or add integrations. Change the smallest relevant area. Check changing to a date with available times, a date with no times, and returning to the original date. Report what changed and any behavior you could not verify. If the selected time is already cleared correctly, investigate the summary state instead of applying a second unrelated reset.

Describe the observed result precisely. A screenshot can support the report, but include the steps and expected behavior in text too.

Which prompt helps improve an existing page's accessibility?

Copy this prompt: Review the current landing page for keyboard and form usability, then make focused improvements. Preserve its content, visual direction, and section order. Check that navigation, buttons, and the waitlist form work without a mouse; focus remains visible; fields have understandable labels; and validation explains the problem near the field. Check mobile overflow and text readability. Reuse existing components where possible.

Do not add new sections, invented claims, or third-party services. Report the specific issues found and changed. Verify moving through the page with the keyboard, submitting an empty form, correcting invalid email, and reaching the primary action on a narrow screen. Identify any checks you could not perform. Treat this as a focused usability pass rather than a claim of complete accessibility compliance.

How should you iterate after the first generation?

Review one journey at a time and keep a short issue list. Separate behavior bugs from visual preferences so you can judge whether a change solved the requested problem. After each fix, repeat the original reproduction and one nearby successful case.

PromptDC for Desktop can help organize a rough Base44 brief using its universal editable Code profile prompt, but it cannot establish missing business rules. Enhancement requires sign-in, a network connection, and a paid plan. The Base44 prompt generator guide, website-building guide, and Base44 integration page provide related workflows.

FAQ

Can I use Base44 to build a website?

Yes. Start with the audience, sections, primary action, and expected form behavior, then review the result before using it publicly.

What is the best Base44 prompt template?

Use a template matched to the user journey. Include data, behavior, constraints, and checks, then remove features your first version does not need.

Should one prompt describe my entire app?

Give the overall purpose, but build and verify a small coherent flow first. Add additional journeys after the first behaves correctly.

Why does a generated page look complete but fail checks?

Visual completeness and working behavior are separate. Verify destinations, validation, persistence, and failure handling rather than relying on appearance.

Can these prompts guarantee production readiness?

No. Real data, authorization, payments, integrations, and operational requirements need their own implementation and validation.

More from the blog

Write better with AI

Enhance any text you select in any app on desktop, in browsers, in your editor or terminals.

Download PromptDC