A key part of increasing the ease of use of polymer workflows is wide availability of preexisting monomer templates. Large libraries of self-consistent default monomer templates could be gradually compiled through adoption of tools built upon the approaches described here, yielding databases of templates for diverse polymer chemistries. The example directory located at includes the first version of a database (monomer generation/combined substruct dict.json) that can load all but two of the polymer systems discussed in this paper (Table ). There are some potential cheminformatic issues with such databases, as some smaller templates may overlap with others, which will require some resolution in terms of how many different non-overlapping monomer lists may be required. During the creation of the combined database for this pa-per, all monomer templates were cross-checked with each other to enforce homogeneity in the chemical information, resulting in an ion template for iron(II) being excluded due to disagreement with an iron(III) and the polyphenylene templates being excluded due to disagreement with the conjugated aromatic rings in the SN6 template for RNA 144d. In the future, the Open Force Field initiative will seek to generalize, validate, and distribute larger databases for specific chemical environments to accelerate chemical information and charge assignment for common molecules and lighten manual workload for users.