> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rushedai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create And Iterate

> The core Rushed workflow from first prompt to a usable project.

## Your three starting points

You can begin from:

* A prompt on the home page
* A blank project from the dashboard
* A GitHub import

Each path is useful for a different kind of work.

## 1. Start from a prompt

This is the fastest way to explore an idea.

Good for:

* new product concepts
* landing pages
* MVPs
* feature spikes
* fullstack product ideas that need real sign-in or saved data

Rushed creates a new project, opens a conversation, and starts generating immediately.

## 2. Start blank

Create a blank project when you already know the structure you want to build or when you want to guide the first steps manually.

This is useful if:

* you want full control over the first files
* you plan to import structure later
* you want to avoid spending credits before asking the AI to do work

## 3. Import from GitHub

Import is the right move when the project already exists and you want Rushed to help inside the current codebase.

This is usually the best path for:

* redesigns
* bug fixing
* feature additions
* code cleanup

## How to iterate well

The strongest loop inside Rushed is:

1. Ask for a clear change.
2. Review the files that changed.
3. Open Preview.
4. Tighten the result with a second request.

Examples of strong follow-ups:

* Make the layout feel less cramped on mobile.
* Keep the structure, but improve the copy.
* Simplify this flow and reduce the number of clicks.
* Use the same visual language as the existing dashboard.
* Replace the mock data with real saved data.
* Add sign-in and keep the setup user-friendly.

## Conversations are project memory, not just chat

Each project can have multiple conversations. This is useful when you want to separate:

* design exploration
* bug fixing
* refactors
* feature work

Rushed also auto-generates conversation titles after the first real message, which makes history easier to scan.

## When to connect a backend

Do not reach for a backend just because the app might need one later.

Connect live backend features when the product actually needs:

* sign-in
* persistent data
* uploads
* realtime updates
* server-side workflows

When you ask for those features, Rushed can provision a managed backend and wire the app to it.

## Useful shortcuts

* `Cmd/Ctrl + J` creates a new blank project from the dashboard
* `Cmd/Ctrl + I` opens GitHub import
* `Cmd/Ctrl + K` searches projects

## A simple workflow that works

If you are not sure where to start, use this:

1. Prompt Rushed with the product and audience.
2. Let it build the first pass.
3. Use `@` to point it at exact files.
4. Use Preview to spot what still feels off.
5. Export to GitHub once the direction is solid.