hackathon-Checklist

Inspiration

So that it is easy for hackathon users to understand what their actual action items are, what action they need to take and what they need to take care of, etc., so that they waste less time understanding the rules and instructions and spend more time on project development.

There are a lot of stories. Once it happened that we were told to make the repo public, and we submitted with a private repo. But we had submitted 4 days early, and it was good that we checked again 1 day before: they had asked for the repo to be public, and we had not made it public. This happened only because the rules page was big, and while reading it we missed some rules.

What it does

It is a very good web app that reads a hackathon's rules and instructions and makes a submission checklist for the user, which removes the user's confusion, clears doubts and helps, etc.

How we built it

I built it with Claude by designing the spec, doing grill-me, doing proper planning, doing proper development with Claude and doing proper testing.

Challenges we ran into

The rules page is quite long, and important instructions can be missed in it. It happened with me too that the repo had to be made public, but we kept it private. So understanding all the rules accurately and identifying the important action items was challenging.

Accomplishments that we're proud of

I am happy that I built a web app that converts a hackathon's lengthy rules into a clear submission checklist. With it, participants know what to do, what to submit, and which important rules to keep in mind.

What we learned

I got to learn a lot in this process. While I was building it, I explored and understood a lot of hackathon projects. A hackathon is a very good platform that gives anyone the chance to explore and present their skills, and it also automatically makes you improve yourself to keep yourself upgraded with what is going on in the market these days.

What's next for hackathon-Checklist

If we take this app further, we will add an auto AI agent to it that will help with such problems. Many participants these days do their work using AI, so I would give an AI-to-AI option, meaning submission using an API, if I have to add something special. Because almost everyone works using AI, a lot of time can be saved if we automate this process. With good financial support, we can also build this AI agent; this is our future planning.

Built With

• claude-code
• css
• html5
• javascript