Last active
March 14, 2025 21:47
-
-
Save dennisedson/416e9731f19e7a2f8df4e4c43290b6c3 to your computer and use it in GitHub Desktop.
Cursor commands
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deep research topic idea: replace the following with whatever you are building. be as specific as possible. useful to use AI to help refine this initial prompt. | |
I would like to create an app using vercel and supabase that creates matches for pickleball the flow should looks something like this, but i am open to changes 1. a person navigates to a website where they can create an event. An event would be considered a series of games 2. when the user chooses create an event, they are then asked to input the players. after inputting the players, we should store them in a database so we can quickly add them for future events. 3. when inputting players, we will add name and pickleball rank which will be a number in .5 increments between 1 and 5. 4. after adding players, the user will submit this list and the app should generate a series of games. the games will be a combo of 4 players playing 2 versus 2. The app should attempt to make the play time for each player equivalent and try to make sure everyone plays with everyone. 5. after the games are generated, the user should have the option to reorder the games and manually edit who is playing a game. 6. To start a game, user should activate the game. 7. after a game is played, the user should be able to input the score and select "end game". 8. If all games have been played, the user should have the option to generate more games. 9. at the end of the event, the user should be able to conclude the event which will be stored in an archive. in a future iteration, we will use the scores to add an option for the user to select the most competitive game play | |
After deep research, we ask it to break it down into tasks | |
perfect now i would like to create a markdown file with a numbered list for major tasks. under major tasks there should be unchecked checkboxes for each subtask. subtasks should be valued at 1 story point. Be sure that all tasks and substeps are as detailed as possible for an AI coding agent to complete. Each subtask should be opinionated and actionable. | |
There should be two sections for this list 1 for the front end and a second for the backend. Again, this should be very detailed and as specific and actionable as possible. For the front end, create a storybook that contains all of the components and the pages | |
In cursor, create a directory and add 3 files: | |
.cursor-tasks. — This is where we will add the markdown file | |
.cursor-updates — This is where we will have cursor create a simple summary of what it completed after each tasks is completed and it waits for review | |
.cursorrules — this is where you will add any specific rules that you want to make sure that it always executes | |
Example of cursorrules: | |
- Keep code short; commits semantic. | |
- Reusable logic in `src/lib/utils/shared.ts` or `src/lib/utils/server.ts`. | |
- Use `tsx` scripts for migrations. | |
- If an installation (such as tailwind) requires user input, stop and allow the user to complete the setup before moving on. | |
IMPORTANT: | |
- After all changes are made, ALWAYS build the project with `npm run build`. Ignore warnings, fix errors. | |
- Always add a summary of changes to `.cursor-updates` file in markdown format at the end of every agent interaction. | |
- If you forget, the user can type the command "finish" and you will run the build and update `.cursor-updates`. | |
- Finally, update git with `git add . && git commit -m "..."` Replace ... with an actual relevant message | |
- Don't push. | |
Go through each story and task in the .cursor-tasks.md file. Find the next story to work on. Review each unfinished task, correct any issues or ask for clarifications (only if absolutely needed!). Then proceed to create or edit files to complete each task. After you complete all the tasks in the story, update the file to check off any completed tasks. Run builds and make git commits after each story. Run all safe commands without asking for approval. Continue with each task until you have finished the story, then stop. Update the .cursor-updates file with what has been completed and wait for me to review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment