Files and Prebyte

Files & Prebyte

How files/ ends up in the target project.

Scan

Tempify scans source_dir (usually files/) recursively:

• Directories → BuildPlan entries (created at render time)
• Files → output files
• .pbc → skipped during listing (Prebyte artifacts)
• .pbt → render_with_prebyte = true (.pbt suffix removed in output)

.pbt vs .pbc

Extension	Behavior
.pbt	Rendered through Prebyte; {{ variable }} replaced
other	Raw copy
.pbc	Skipped during manifest scan

Example: README.md.pbt → target README.md

Variables

All question answers are available to Prebyte as variables.

README.md.pbt:

# {{ project_name }}

Namespace: {{ namespace }}

Empty directories

An empty folder under files/ (e.g. files/empty_keep/) is kept as a directory entry and created at render time.

layout.lua

Overrides paths and render flags - see layout.lua.

Prebyte directly

To test individual files: Prebyte Passthrough

See also

Your First Template