Boilerplate or framework are industry terms for standardized project code; as CDO defines it
text that can be copied and used in legal documents or in computer programs, with only very small changes
LDOCE and ODO mark it as an Americanism.
I am less inclined to recommend framework as it is used loosely, and can mean different things in different contexts. Broadly, it is a abstraction of code which offers predefined code for handling complex operations in a systematic way, but is also used to refer to any development environment or platform.
While template would also be acceptable, and perhaps better understood if writing for a general audience— HTML5Boilerplate calls itself "web's most popular front-end template"— I think of a template as a skeleton for an individual page or page component, and a snippet as a small piece of re-usable code that is itself rarely modified. At the project level, a boilerplate would be composed of multiple templates and snippets organized into patterns.
Certainly, boilerplate is a term front-end developers are accustomed to: Mashable has its list of 20 boilerplates and frameworks, among which Skeleton calls itself "a beautiful boilerplate…" and Goldilocks offers "boilerplate CSS and HTML files based on current best practices"— though I hesitate to point out Gridless being "an optionated HTML5 and CSS3 boilerplate" as I don't care to help popularize "optionated" if I can avoid it.