scaffold-site

To automate project scaffolding from a site brief, invoke the orchestrator with a brief path to copy a starter, apply patches, and emit artifacts like site-manifest.json, content-seed.json, and build-status.md.

Scaffolding a site from a plan generates site-manifest.json, content-seed.json, design-tokens.json, and build-status.md artifacts. These files coordinate input validation and provide structured inputs for downstream build phases.

Scaffolding from a site brief does not generate page code or upgrade placeholder copy. It copies starters, writes marker files, and emits artifacts, leaving page-building to the subsequent build-site phase.

You can use a site-plan instead of a site-brief to scaffold a workspace. The orchestrator accepts either validated format to select an appropriate starter, render the manifest, and run smoke checks.

The best way to stand up a project directory from a brief is using an end-to-end scaffolding orchestrator that validates inputs, patches a starter template, and emits structured content-seed and design-tokens artifacts for immediate downstream work.

A site scaffold stops before generating page code because the pipeline explicitly avoids page-code generation during the scaffold phase. It only emits artifacts and sets up the directory, deferring code generation to the build-site phase.