AEM cloud: which directories needed to sync content between envs via packages?

We create the content on production, then sync the content down to UAT / test / dev cloud AEM envs.

The problem is that its easy to miss items (such as policies), or take too much (and cause issues).

We tried the following:

/content/our-web
/content/dam/our-web
/content/experience-fragments/our-web
/conf/our-web

as /conf/ourweb contains several important dirs, including templates, template types and policies.

However, when we try to deploy the above package to another of our envs, we get:

"Package (or it's subpackage(s)) contains application content which isn't supported at runtime."

Any suggestions on directories we should and should not include as part of a complete content sync package?