Base44 Prompts: 25 Copy-Paste Prompts to Build Apps Faster

Build a landing page for [product name], a [one-line description] for [audience].
Sections in this order: navbar, hero with one headline and one primary button "[button text]", 3 feature cards, how it works in 3 steps, pricing, FAQ with 5 questions, footer.
Style: [dark/light] background, one accent color [hex], rounded cards, generous spacing, one font.
Use my real copy below and invent nothing else.
[paste your copy or bullet points]

Rewrite only the hero section. Headline: max 8 words about [main benefit]. Subheadline: one sentence that says who it is for and what they get. Keep the existing button, layout, colors and every other section exactly as they are.

Add a pricing section above the FAQ with 3 plans: [Plan 1] [price]/mo, [Plan 2] [price]/mo, [Plan 3] [price]/mo. Each card lists 4 features and has one button. Highlight [Plan 2] as "Most popular". Add a monthly/yearly toggle that shows [discount]% off yearly. Match the existing card style.

Check every section of the landing page at 390px wide and fix only layout problems: no sideways scrolling, text never overflows its card, buttons are full width under 640px, and images scale down. Do not change any copy or colors. List what you changed.

Add an FAQ section before the footer with these questions and answers, as an accordion where one item opens at a time and the first one starts closed:
[question 1] / [answer 1]
[question 2] / [answer 2]
[question 3] / [answer 3]
Use the same heading size and spacing as the other sections.

Add a waitlist form under the hero: one email field and a "[button text]" button. Save each signup to a new Waitlist data table with fields email and created_at. Reject invalid emails and duplicates with a short inline message, and show "You're on the list" after a successful signup.

Create a dashboard page with a left sidebar (links: Overview, [Entity name], Settings), a top bar with the page title and user menu, and a main area. On phones the sidebar becomes a menu button that opens a drawer. Keep it empty for now except a page title in each section.

On the Overview page add 4 KPI cards in a row: total [records], new this month, [metric 3] and [metric 4]. Calculate each value from the [Entity name] data, not hard-coded numbers. Show the change versus last month as a small up or down label. Stack the cards 2 by 2 on phones.

Add a line chart under the KPI cards showing [metric] per day. Add a date range filter above it with options Last 7 days, Last 30 days and Last 12 months, defaulting to Last 30 days. The KPI cards and the chart must both update when the range changes.

Add a table of [Entity name] records with columns [col 1], [col 2], [col 3] and created date. Add a search box that filters by [col 1], sortable column headers, and pagination with 20 rows per page. On phones, show each row as a card instead of a wide table.

When I click a row in the [Entity name] table, open a detail page for that record showing all its fields, an Edit button and a Delete button with a confirmation dialog. Add a Back link to the table that keeps the search and page I was on.

For every list, chart and card on the dashboard, add three states: a loading skeleton while data loads, an empty state with one short sentence and a button to create the first [record], and an error message with a Retry button. Do not change the layouts otherwise.

Before building any screens, plan the data model for this app: list each data table, its fields with types, and how the tables relate. The app is [one-line description] and users need to [main actions]. Show me the plan first and wait for my OK before creating anything.

Make every page except the landing page require login. Logged-out visitors who open a protected page go to the login page, and after logging in they return to the page they asked for. Add a Log out item to the user menu.

Add two roles: admin and member. New users are members. Only admins can see the Settings page and delete [records]; hide those buttons for members instead of showing an error. Make [your email] an admin.

Change the access rules so each user can only view, edit and delete the [Entity name] records they created. Admins can see all records. Add an owner field set automatically to the current user when a record is created.

Create one form used for both creating and editing a [record] with fields [field 1] (required), [field 2] (required, email), [field 3] (number, min [x]) and [field 4] (optional). Show errors under each field as the user types, disable Save until the form is valid and show a success message after saving.

Add 25 realistic sample [Entity name] records for testing, spread over the last 90 days, with varied values in every field. Mark them with a sample flag so I can delete them all later with one Delete sample data button on the Settings page.

Add a Settings page with two tabs. Profile: name, avatar upload and email shown read-only. Preferences: email notifications on or off and default date range for the dashboard. Save changes to the current user and show a short confirmation.

This error appears when I [what you did]:
[paste the exact error message]
First explain in 2 or 3 sentences what causes it and which file or step is involved. Do not change any code yet. Wait for my OK before fixing it.

The "[button text]" button on the [page name] page does nothing when clicked. Find out why, fix only that button's behavior so it [expected result], and do not change its styling or any other part of the page.

When I [action], the [record] does not appear in [where it should appear]. Check whether it is being saved, whether the access rules allow the current user to see it, and whether the list refreshes after saving. Tell me which one it was, then fix only that.

On phones (390px wide) the [section or page] is broken: [describe what you see]. Fix it so it fits the screen with no sideways scrolling. Do not change the desktop layout, the copy or the colors.

Your last change to [feature] broke [what broke]. Undo only that change and restore how [feature] worked before. Keep every other change from your last edit. Tell me which files you reverted.

Review the app for problems left by earlier edits: unused pages or components, duplicate styles, buttons that link nowhere and text that doesn't match the rest of the app. List what you find first, then fix only the items I approve.