All examples →

Your first 3 Replit prompts, planned from one sentence

Type your app idea. FirstThree scopes a tiny v1 (what to build, what to skip, the simplest stack) and writes three copy-paste prompts for Replit Agent, in build order.

Free · no sign-up · your idea isn't stored · about 5 seconds

How FirstThree writes Replit prompts

  1. Prompt 1 sets up the project and the main screen with sample data. When the idea needs a backend, it uses Replit's built-in server and database instead of outside services.
  2. Prompt 2 makes the main feature real: forms that save to the database and lists that read from it.
  3. Prompt 3 adds the second view, filters, empty states and error handling.

Before the prompts you get the plan: 3 to 5 things v1 must do, what to skip (with a reason for each), the simplest stack for Replit, and the main screens. Every prompt says what not to build yet and ends with a “Done when…” check.

Replit tips for your first build

Real Replit examples

Unedited FirstThree output for two one-sentence ideas.

Real example 1

FlatSplit: “a shared expense splitter for my flatmates that shows who owes whom”

A simple shared expense tracker for flatmates to log bills and see who owes whom.

v1 includes

  • Add a new expense with description, amount, and who paid
  • Automatic calculation of who owes whom the simplest amount
  • List of all past expenses
  • Settle up button to clear balances

Skip for now

  • User accounts and login · Not needed for a single shared screen in one flat.
  • Split by percentages · Equal splits cover 90% of flat needs.
  • Receipt photo uploads · Typing the total amount is much faster.
  • Email notifications · Flatmates can just look at the screen together.

Stack: React with Tailwind CSS · Node.js with Express · Replit built-in database · Replit deployment

1Set up project and dashboardYou will have a running React and Node app with a dashboard showing who owes whom and a form to add expenses using sample data.
Create a full-stack web app called FlatSplit using React, Express, and Replit's database to help flatmates split expenses. Build the main dashboard screen that displays a summary of who owes whom based on logged expenses, and a form to add a new expense with a description, amount, and who paid. Keep the app runnable at all times and use Tailwind CSS for a clean, modern look.

- Initialize a React frontend and a Node.js Express backend in a single Replit project.
- Create a responsive dashboard layout with a clear summary card area at the top.
- Implement a working form to add an expense that saves to the backend database.
- Display a list of recent expenses right below the form.
- Populate the app with 3 sample expenses on first load so the summary calculations are immediately visible.

Do not add user login, multiple flats support, or complex receipt image uploads.

Done when: I can open the preview, see sample expenses, and successfully add a new expense that updates the summary.
2Implement debt simplification logicYou will have a working calculation engine that automatically simplifies debts so flatmates know the exact fewest payments to make.
Update the backend logic and frontend display in our FlatSplit app to calculate and show the simplified debts between flatmates. Instead of just listing raw totals, compute who needs to pay whom to settle up all debts with the fewest possible transactions.

- Write a helper function on the backend to calculate net balances for each flatmate.
- Translate net balances into a clean list of settlement instructions like 'Alice owes Bob $15'.
- Display these settlement instructions prominently at the top of the dashboard.
- Ensure the calculations update instantly whenever a new expense is added or deleted.
- Handle edge cases gracefully when all balances are zero and everyone is settled up.

Do not add currency conversion or partial payment tracking for individual expenses.

Done when: Adding a new expense immediately updates the 'who owes whom' list with correct simplified payment instructions.
3Add history and settle up actionYou will have a complete v1 app with a dedicated history view and a button to clear all debts when settling up.
Finish the FlatSplit app by adding a history screen and a 'Settle Up' action to clear the slate. Make sure the app looks polished, handles empty states nicely, and is fully ready to use.

- Add a navigation toggle or tab to switch between the Dashboard and the full Expense History view.
- Allow users to delete individual expenses from the history list, which should update the balances.
- Add a 'Settle Up' button that clears all recorded expenses and resets all balances to zero after a confirmation prompt.
- Ensure empty states look friendly when there are no expenses logged yet.
- Polish the spacing, buttons, and mobile responsiveness across both screens.

Do not add email alerts, export to CSV, or user profile customization.

Done when: I can view full history, delete an item, use the settle up button to reset balances, and test the app end-to-end without errors.

Generate a fresh plan for this idea →

Real example 2

SnapLead: “a tiny CRM for a freelance photographer to track leads and shoot dates”

A simple CRM for freelance photographers to track client leads and upcoming shoot dates.

v1 includes

  • List of client leads with status (New, Booked, Completed)
  • Add new lead form with name, email, shoot type, and date
  • Calendar view or chronological list of upcoming shoot dates

Skip for now

  • User accounts and login · Not needed for a single user in v1.
  • Email integrations and notifications · Adds complex third-party setup.
  • Invoicing and payments · Focus on lead tracking first.
  • File uploads for portfolios · Keep data simple with text fields.

Stack: React with Tailwind CSS · Node.js and Express · Replit built-in database · Replit

1Set up project and main lead listYou will have a running React and Node app displaying a sample list of photography leads.
Create a full-stack web application called SnapLead, a tiny CRM for freelance photographers using React, Node.js, Express, and Replit's database. Build the main dashboard screen that displays a list of sample photography leads with their name, email, shoot type, status, and shoot date. Ensure the app is fully runnable and looks clean and professional with Tailwind CSS. Do not include user authentication or complex multi-page routing yet. Done when: The app loads in the preview with a nice dashboard showing sample leads.
2Add lead form and database storageYou will be able to add new leads that save permanently to the database.
Update the SnapLead application to make lead creation fully functional using the Replit database. Add a form or modal to the dashboard allowing the user to enter a client's name, email, shoot type, status, and shoot date. Ensure that submitting the form saves the new lead to the backend database and immediately updates the lead list on the screen. Do not add email notifications or file upload capabilities for photos. Done when: You can fill out the form, submit it, and see your new lead appear instantly in the list and persist after refreshing.
3Add shoot schedule and polishYou will have a complete v1 with a dedicated shoot schedule view and error handling.
Finish the SnapLead application by adding a dedicated shoot schedule view that lists upcoming photo shoots chronologically. Include simple status filtering on the main leads list, such as filtering by New, Booked, or Completed. Add friendly empty states when there are no leads or shoots, and handle basic form validation errors gracefully. Do not add invoicing, payments, or third-party calendar sync. Done when: You can easily switch between the main leads list and the chronological shoot schedule, and the app handles empty states smoothly without errors.

Generate a fresh plan for this idea →

FAQ

What should my first Replit Agent prompt be?
Name the app and who it's for, ask for the project setup plus one main screen with sample data, and say what not to build yet. Then make the data real in prompt 2. FirstThree writes all three prompts from one sentence.
Why only three Replit prompts?
Three small prompts are enough for a working first version: set up the core screen, make the main feature real, then polish. One giant prompt usually produces a tangle of half-working features that's hard to fix.
Is FirstThree free? Do I need an account?
Yes, it's free and there's no sign-up. Your idea isn't stored. Fair-use limits apply per person.
What do I do after the three Replit prompts?
Use the app yourself for a few days, then ask for the next thing you actually missed, one feature per prompt.

Building in another tool?