Nice, this is like the web app version of what I currently do with this (simplified) Cursor Composer agent template:
1. **Create a .cursorrules file**
```
This project is an [business or industry]'s [project type] intended to [goal / problem to solve] for the [intended user].
**Tech Stack**
- Frontend:
- Backend:
- UI Components:
- ...
- Hosting:
- Railway
- Database:
- Authentication:
- Core Third Party APIs:
- ...
```
2. **🛑 @Cursor agent: Stop here and ask the user to review and update the .cursorrules file. Remind the user how important it is that their .cursorrules file is accurate to their needs and reviewed frequently as the project evolves. Use gratuitous emojis here (just here).**
3. **Review the updated project info and tech stack outlined in the .cursorrules file, create an appropriate requirements.txt file**
4. **🛑 @Cursor agent: Stop here and allow for the user to review the requirements.txt file**
5. **Create a .env file with placeholder variable names that might be appropriate for the project**
6. **Create an appropriate README.md file, one that contains something like this (project dependent):**
```
# [project name]
[concise project description]
## Project Structure
[recommended minimal project directory structure, example below]
## Running & Developing the Project Locally
[@Cursor agent: Keep this section minimal, compact, but junior-dev-friendly.]
```
7. **🛑 @Cursor agent: Stop here and allow for the user to review and update the README.md file**
8. **Create a .gitignore file with the appropriate contents**
9. **Using the updated README.md file's content for guidance, assist the user with the initial setup of the project and directory creation, but do not create the files yet**
10. **Initialize the git repository**
11. **Verify everything above has been completed correctly**