> ## 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.

# What Rushed Is Good At

> Use Rushed where it has leverage: rapid product iteration, code-aware edits, and shipping momentum.

## Best-fit use cases

Rushed works best when you want to move quickly from idea to working product.

It is especially strong for:

* Starting a new app from a natural-language prompt
* Iterating on existing UI and flows inside a real codebase
* Refactoring or extending files with project context
* Fixing local issues by targeting the right files
* Connecting real backend features when the product needs sign-in, saved data, or uploads
* Importing a repo, making changes, and exporting back to GitHub

## Where it shines most

### Product iteration

You can go from:

* rough idea
* to generated project
* to visual preview
* to refinements in chat

without switching tools constantly.

### Fullstack app setup

Rushed is moving beyond frontend-only generation.

When the request needs real product behavior, it can now set up a managed backend flow and keep environment setup inside the project instead of pushing the user through a long manual setup checklist.

### Code-aware collaboration

Rushed is not just a blank chat box. It can work against your project structure, read files, update files, create folders, rename things, and keep changes grounded in the current workspace.

### Fast local edits

If the change is small, highlight code and use `Quick Edit` instead of opening a full conversation loop.

## Less ideal use cases

Rushed is probably not the best first tool when you need:

* formal API documentation
* infrastructure-heavy DevOps workflows
* deep backend debugging across multiple external systems
* compliance or legal writing

It can still help, but its sweet spot is product building and code iteration.

## The best mental model

Treat Rushed like an AI teammate inside your browser:

* start with a clear goal
* keep the project in view
* iterate in short loops
* use preview to validate quickly
* export when you are ready to keep going in GitHub