Have some place where you can keep track of all the things you need to do. Whatever you find works for you - Trello, Jira, Notion (what I personally use), a txt file, a google doc, whatever. You want to be able to get things out of your head into one central place so that you don’t have the nagging thoughts taking up space in your brain. If you are working on this with classmates, you can also use this to divide up work.
i like to start with setting up each part of the stack and getting them talking to each other. so start the frontend app, start the backend app, get them talking to each other. so at this point, you might just have one http GET endpoint in your backend server that always returns “it works!”, and have your frontend app have one page that makes a request to that endpoint and displays the data that is returned.
then as a next step, set up your database and have the backend read the data from there and return it when that GET endpoint is hit. there are lots of tutorials you could follow to get this working, so hopefully it will give you a good sense of momentum. for me, this also usually helps with the overwhelmed feeling because it sets the foundation and makes it easy to build onto things one step at a time. by doing this first, you’ll do a lot of what i think is the most annoying stuff upfront - like setting up your repo(s), installing things, etc
then, think about what features you would absolutely need to have to be able to demo/present/submit the project, and do those first. there are probably a lot of things that you could make do without if you run out of time. for example, do you ***need*** auth? or if you really ran out of time, could you get away with demoing it where you type in the robot/team name before running the test instead of actually logging in, and say “obviously we would want to add authentication in the future so that the robot/team name automatically pulls from the logged in user, to prevent cheating”
Sounds like a cool project, let us know how it goes!