One idea
State is component memory. Use it for data that changes over time because of user interaction, like a selected tab, a counter, or a saved draft title.
Do not store data that comes from props or can be calculated during render. Less state means fewer bugs.
What state is for
In a React app, your component runs, returns JSX, and React shows it. When the user clicks, types, or selects something, the UI may need to remember a new value. That is when you reach for useState.
For your HackIndia repo, reviewers should see state that has a reason. A filter button, a like count, an active project idea, or a form draft is clear. A duplicate value that can be calculated is clutter.