All examples →

Your first 3 Cursor 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 Cursor's agent, in build order.

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

How FirstThree writes Cursor prompts

  1. Prompt 1 scaffolds a small local project (usually Vite + React + Tailwind) in an empty folder, writes a short PLAN.md with what's in and out of v1, builds the core screen and tells you how to run it.
  2. Prompt 2 makes the main feature real: saved data, real logic, no more sample data.
  3. Prompt 3 polishes: empty states, error handling, a final checklist.

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 Cursor, and the main screens. Every prompt says what not to build yet and ends with a “Done when…” check.

Cursor tips for your first build

Real Cursor examples

Unedited FirstThree output for two one-sentence ideas.

Real example 1

EtsyPulse: “a dashboard for my small Etsy shop that shows which products sold best each month”

A simple dashboard for small shop owners to track monthly top-selling products using sample data.

v1 includes

  • Monthly sales summary cards
  • Top products ranking list
  • Basic month selector dropdown
  • Sample Etsy data so it works instantly

Skip for now

  • Etsy API Integration · Requires complex OAuth setup and tokens.
  • User Accounts · Not needed for a single-user local dashboard.
  • Database · Sample mock data in a JavaScript file is enough.
  • Export to CSV · Can be added later once the core view works.

Stack: React with Vite and Tailwind CSS · None · Local mock data array in the project · Local machine

1Set up project and dashboard layoutYou will have a running React app with a nice Tailwind layout and sample Etsy product data.
Create a new Vite React app in the current folder using Tailwind CSS for styling.

- Write a PLAN.md file outlining our v1 scope: monthly summary cards, top products list, and a month dropdown, while skipping Etsy API integration, user accounts, and databases.
- Create a sample data file with mock Etsy products, monthly sales counts, and revenue for the last three months.
- Build the main dashboard screen with a clean sidebar, a header, summary metric cards, and a data table for top products.
- Populate the table and cards using the sample data.
- Explain how to install dependencies and run the dev server in the terminal.

Do not add external backend servers or complex charting libraries yet; keep everything in pure React components with Tailwind.

Done when: I can run the dev server and see a styled dashboard populated with mock Etsy sales data.
2Add filtering and detail viewYou will be able to filter products by month and click into items for more details.
Update the EtsyPulse dashboard so the user can interact with the data.

- Add a functional month selector dropdown at the top of the dashboard.
- Make the summary cards and top products table update dynamically based on the selected month.
- Add a click handler to any product row that opens a simple modal showing more details about that product's sales.
- Ensure the UI looks clean and handles empty states gracefully if a month has no sales.
- Keep changes small and modular, updating existing files cleanly.

Do not connect any external APIs or databases; keep using the local mock data file.

Done when: Changing the month dropdown updates the stats and clicking a product opens its detail modal.
3Polish and testing guideYou will have a polished app with clear instructions on how to test every feature.
Add final polish and documentation to the EtsyPulse dashboard.

- Improve the visual styling with subtle hover effects, clean badge colors for top sellers, and responsive spacing.
- Add a README.md file explaining what the app does, how it works with mock data, and step-by-step instructions on how to test it.
- Verify there are no broken imports or console errors in the code.
- Ensure the layout looks great on both large screens and smaller browser windows.

Do not add new major features or pages outside the agreed v1 scope.

Done when: The app looks polished, runs without errors, and has a clear README testing guide.

Generate a fresh plan for this idea →

Real example 2

FretFlow: “a habit tracker for guitar practice that logs minutes per day and shows a streak”

A simple guitar practice habit tracker that logs daily minutes and displays your current streak.

v1 includes

  • Daily practice time logging
  • Current streak counter
  • Practice history list
  • Local browser storage

Skip for now

  • User accounts · Not needed for single-player local tracking.
  • Backend database · Browser localStorage is enough for v1.
  • Detailed analytics charts · A simple streak counter proves the core value.
  • Dark mode toggle · Stick to one clean theme to save time.

Stack: React with Vite and Tailwind CSS · None · Browser localStorage · Vercel or local only

1Project Setup and DashboardYou will have a working React app skeleton with a basic dashboard and sample data.
Please set up a new React project with Vite and Tailwind CSS in this current folder. Create a file named PLAN.md listing our v1 includes (daily logging, streak counter, history list, localStorage) and skips (accounts, database, charts, dark mode). Build the main Dashboard screen with a nice guitar-themed layout, a form to log practice minutes, a streak counter, and sample practice history data. Keep changes small, use clean functional components, and explain how to run the app at the end.
2Make Data Real with LocalStorageYou will have a working practice tracker that saves your logged sessions in the browser.
Update the app so that submitting the practice form actually saves the minutes and today's date to the browser's localStorage. Calculate the real streak based on consecutive days of practice and display it dynamically on the dashboard. Ensure the practice history list updates immediately when a new session is added. Keep changes small, handle empty states gracefully when no sessions exist, and explain how to test the app.
3History View and PolishYou will have a polished v1 app with a history screen and a quick testing checklist.
Add a simple navigation or tab system to switch between the Dashboard and a History Log screen. On the History screen, show all saved practice sessions with an option to delete an entry. Add friendly empty states and basic error handling if someone tries to log invalid minutes. Create a short checklist at the bottom of PLAN.md on how to test the app. Keep changes small and explain how to run the final app.

Generate a fresh plan for this idea →

FAQ

What should my first Cursor prompt be?
Ask for the project setup plus one working screen, not the whole app. Name the stack, list what v1 includes and what it should not build yet, and end with a check you can verify (for example: "Done when: npm run dev shows the dashboard with sample data"). FirstThree writes that prompt for you from one sentence.
Why only three Cursor 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 Cursor 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?