But what i am saying is like what if i showed the director that i can do the work that a team has taken months/years to do. And is still failing to do. Seems like best way to proceed is just put my head down which sucks and makes me want to leave
Want to really be a senior? Think this way: Everything I build as a senior developer is an attempt to make myself obsolete. I should be able to give a two weeks notice and walk away with no harm to the company. When I build things at work, I never worry about job security, not even a little. If there is something I built that they can't support without me, I've failed.
And you will ultimately know you failed when you can't even go on vacation without carrying the company laptop with you. I know you're proud of that thing you built and how you're the only one who knows how it all works, but that's the core problem.
If the project is not failing, talk about how you would have done things differently in your next one-on-one and make it be known you'd like to be part of the planning next time.
It's normal to wish things were tailored more to your preference, it's normal to look back on how something was done and see a better way it could have been done. If you have retrospectives that's another good place to talk about these thoughts.
The way to effect this change is to psy-op your teammates/bosses into thinking they came up with it.
It sounds like a bad culture fit for you, to be honest. Nothing wrong with looking for another job; you're not likely to be able to steer this ship around, if nobody is interested in supporting you.