Explains what the project is about. It’s the first thing visitors see.
Lists files/folders Git should not track (like node_modules/, .env, or build outputs)
Defines how others can legally use your code. Without it, your repo defaults to “all rights reserved.”
Optional, but useful if you expect collaborators. It explains how to submit changes.
Sets community standards for behavior.
Tracks version history and updates
[!Notice] The most useful starting point is usually README.md (to explain your project) and .gitignore (to keep clutter out). After that, you can add a LICENSE if you want others to use your code.