Automate site-brief validation, starter patching, and artifact emission into a project scaffold.
npx skills add https://github.com/calebaero/website-factory --skill scaffold-site
Please help me install this Agent Skill. Skill: scaffold-site Source: https://github.com/calebaero/website-factory/tree/main/skills/scaffold-site Command: npx skills add https://github.com/calebaero/website-factory --skill scaffold-site
Take a validated site-brief (or site-plan) and stand up the project directory under the workspace root — copy the correct starter, write the marker file, apply brief-driven patches, and emit the site-manifest / content-seed / design-tokens / build-status artifacts. A thin orchestrator around scripts/create-site.mjs; does not generate page code or upgrade placeholder copy — that is build-site's job.
Invoke the scaffold-site skill with a path to a site-brief or site-plan to produce the workspace scaffold and artifacts.
High-intent search queries and answers about installing and using this skill.
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.
calebaeroCreate canonical client site-brief JSON validated against the site-brief schema.
calebaeroAssemble production-ready website files from scaffold data and design tokens.
Kilo-OrgScaffold SKILL.md frontmatter and starter directories for new skills.
IntegralistGenerate a complete Go API service project with templates and observability tools.
