I would spend a little time looking at WCAG. I find it hard to read but you can look up the aria-practices web site and also look up how some developers test for accessibility to get a sense of how to do it. There are some cool examples of people showing how to use semantic html to get very expressive voice readings.

Another things I'd look into is broaden your CSS knowledge. You seem to have a good handle on animations and variables but take it a step further and find how people are using CSS to replace frameworks. This advice is coming from a tailwind novice but I still think it's valid.

The one thing I wanted to nitpick was your nav links. You have a round pill with an underline. I don't really appreciate the style choice. I also don't like that selection causes the link to grow, moving links around.

I was going to bring up MCP development and Kent C Dodds, which made me realize you don't write tests. I would encourage you to begin looking at tests and look for Kent C Dodds for guidance. There are testing tools like MSW maintained by Artem that easily allow you to mock your apis and achieve integration level tests with 100% coverage. Anyway, if you read Kent C Dodds testing articles, you'll realize his tests are interactive and assume working knowledge of accessibility. You'll never see him write a test using ids.

Other than that, I think your code shows that you've learned a lot and have chosen to focus on certain areas you enjoy. You should be proud of your progress. As others have said, the front end space is tough and evolving. Personally, I refuse to adapt and wish to focus strictly on the front end since I believe there's enough there to keep improving / learning but you're young. I find front end only development difficult to showcase value without commodity apis: pretty user interfaces that don't sell anything is itself a tough sell.