Skip to main content

​
1. Sign in and choose how to start

There are three good starting paths:
  • Start from a prompt if you want Rushed to create the first version
  • Start blank if you want control over the first files
  • Import from GitHub if the project already exists
If you are new, start from a prompt. Example: 
Build a simple landing page for an AI sales assistant for startups.
Make it clean, modern, and mobile-friendly with pricing and FAQ sections.
If you want live features from the start, say so directly: 
Build a family calendar with sign-in, saved events, reminders, and an admin view.

​
2. Let Rushed create the first pass

When you submit a prompt from the home page or dashboard, Rushed:
  • creates a new project
  • opens a conversation
  • starts generating code immediately
Do not try to perfect the first prompt. Aim for a strong direction, then iterate.

​
3. Review the project in three places

After the first response, move through the workspace like this:
  1. Read the conversation summary.
  2. Inspect the changed files.
  3. Open Preview to see the result running.
  4. Open Backend when you need auth, saved data, or live server-side behavior.

​
4. Make the second prompt narrower

Second prompts are where quality usually jumps. Good follow-ups:
  • Tighten the copy and make it feel more premium.
  • Keep the structure, but improve the mobile layout.
  • Use larger type and clearer visual hierarchy.
  • Add a testimonial section without changing the rest of the page.

​
5. Use file-aware prompting inside the project

Once you are inside a project, type @ in the chat box to reference files directly. Example: 
Use @src/app/page.tsx and improve the hero section without changing the pricing section.

​
6. Use Quick Edit for local changes

When you highlight code in the editor, you can:
  • send it to chat
  • run Quick Edit
Use Quick Edit for surgical changes. Use chat for broader project work.

​
7. Export when the direction is solid

If you want to continue in GitHub, use Export from the project toolbar.

​
8. Add live backend features when the app needs them

When your app needs sign-in, saved data, uploads, or other real backend behavior, tell Rushed directly. Examples:
  • Add email and password sign-in
  • Connect this app to live data
  • Save user-created records instead of mock data
  • Add Google sign-in and show me any keys I still need to provide
Rushed can provision a managed backend, store platform-managed values automatically, and only ask you for third-party secrets when they are truly required.

​
What to do next