At CFEngine we have a policy starter kit that comprises two parts:
You import the cfengine standard library into your CFEngine policy. This is a lingua franca of standard nuts'n'bolts definitions that you can use to build up solutions within cfengine. It is an interface layer that brings industry-wide standardization of CFEngine configuration scripting and hides awkward technical details.
Include it like this:
body common control
{
inputs => { "cfengine_stdlib.cf" };
}
And then go on to this:
This is a collection of `recipes' or solution bundles for solving common configuration problems. Many of them can be used `out of the box' and others can be treated as examples that you modify for your own use. Look in particular for Deployment Examples and (Orion) Cloud Examples.