@michaelcompton, can you share here that schema builder that you have on github separating the auth from the schema. I think it sort of applies to the OP in making schema easier to handle. I don’t have that link on hand.
I also hookup my VS Code setup to my development GraphQL instance. That means I get graphql editing help for the is-this-user.auth.graphql file and if the schema changes, I get a red squiggle.
Then I have a node.js file that deploys to Slash GraphQL for me. It takes the schema.graphql file, substitutes the contents of is-this-user.auth.graphql wherever it sees rule: "<<is-this-user>>" and so on for other rules and uploads to slash.
It works really nicely for me because it removes any magic strings and I never have to repeat my auth rules.
It could be expanded to accept multiple files as the schema … I think one of the VS Code graphql extensions lets you #include ... other graphql files so you get editing help across multiple schema files, but no 100% sure how that works.