First, a reality check - it’s great that you can ship defect-free code, but that’s table stakes for a good senior engineer. You’re locally a 10x engineer because you wrote most of the code, so you’re naturally going to be a lot more effective than the other people on your team. This probably won’t translate to new projects.

If you joined a new project where someone else had written 80% of it, it would take you years to catch up to their productivity; if they were controlling and continued to write 80% of everything, it would be impossible. The next step in becoming a better engineer for this project is figuring out what you need to do differently for everyone else to be more productive; for example, if other people are pushing bugs, you need to add tests to make that impossible. If people take a long time to ramp up, you need to refactor the code so that someone doesn’t need to understand -all- of it to start contributing; you might also need onboarding docs.

The next step in becoming a better engineer generally is to switch teams and learn new skills. If you enjoy hard technical work, miss feeling challenged, and genuinely feel like you’re a much better dev than average, try switching to a hard field that’s new to you: distributed systems, ml, performance engineering, etc.