Repository navigation
Template Quality
Leonard Ramminger edited this page Aug 22, 2026
·
1 revision
Checklist before publishing a template.
tempify validate <id> # manifest, questions, files
tempify lint <id> # style & conventions
tempify inspect <id> # show merged manifest
tempify test <id> # snapshot fixtures-
idunique and stable (no renames without migration) - Semver in
version- see Versioning & Reapply -
descriptionshort and clear -
output.pathsensible (usually{{ project_slug }})
- Sensible defaults and
slugifyfor slugs -
validatefor namespaces, paths, licenses -
sensitive = truefor tokens/secrets - No empty groups in
order
-
.pbtonly where variables are needed - No secrets in
files/ -
.envonly for template defaults, not user secrets
- Hooks idempotent where possible (re-render scenarios)
- No writing outside build root
- Short
execcalls; respect timeout
-
file_conflictsexplicit for intentional overrides -
drop_pathsfor removed base files - Avoid cycles
- README in generated project explains next steps
- Tags/category when distributed via ReqPack
Tempify · Repository · Issues · Releases
Documentation lives in this wiki. For a build quickstart, see the README in the repository.
Prebyte (template engine) is a separate project bundled by Tempify.
- CLI Reference
- Questions & Answers
- Configuration
- Render Options
- Hooks (Users)
- Reapply & Diff
- Shared Template Store
- Prebyte Passthrough
- Shell Completion