You currently put (release) binaries into your git source code repository. (tghe SVGs basically) This is not a good practice.
You should consider usingreleases to attach these large binary files to these there, instead of committing them it into the repository, because then these always need to be cloned (by each fork/contributor/…).
Then you can also link to them in the Readme and make it clear one does not have to follow the installation steps, but can also just download the SVG and print it.
You currently put (release) binaries into your git source code repository. (tghe SVGs basically) This is not a good practice. You should consider using releases to attach these large binary files to these there, instead of committing them it into the repository, because then these always need to be cloned (by each fork/contributor/…).
Then you can also link to them in the Readme and make it clear one does not have to follow the installation steps, but can also just download the SVG and print it.