Assemble production-ready website files from scaffold data and design tokens.
npx skills add https://github.com/calebaero/website-factory --skill build-site
Please help me install this Agent Skill. Skill: build-site Source: https://github.com/calebaero/website-factory/tree/main/skills/build-site Command: npx skills add https://github.com/calebaero/website-factory --skill build-site
Takes a scaffolded project and turns it into a coherent, production-ready website by implementing routes, sections, content structure, nav/footer, design tokens, forms, gallery, FAQ, local SEO, motion, and interactive elements — while resolving all [REPLACE_WITH_*] tokens and upgrading placeholder content when the brief allows AI drafting.
Initiate the build-site workflow against a scaffolded site directory to generate complete site artifacts.
High-intent search queries and answers about installing and using this skill.
To build a production-ready website from a scaffold, coordinate the site marker, manifest, content-seed, design-tokens, and brief data to generate routes, sections, tokens, and SEO defaults. This process assembles deploy-ready files while respecting starter contracts and feature flags.
Resolving placeholder tokens involves sweeping the brief and design-tokens to replace [REPLACE_WITH_*] markers with production copy. AI drafting upgrades placeholders only when the contentSource feature flag permits it; otherwise, seed TODOs are preserved on disk.
Yes, design tokens are swept and integrated responsively to maintain design system consistency. The site build process supports multiple starter archetypes and applies the appropriate routing, page structure, and content model while honoring archetype constraints.
No, this site build process is CMS-agnostic and does not wire CMS, run QA, or handle deployment. It focuses strictly on generating code and on-disk content artifacts, leaving external integrations and deployment to other pipeline stages.
The best way to apply local SEO defaults is by consuming the site manifest and brief data to generate routes, sections, and SEO defaults for each page. This ensures the starter-specific routing and content model are correctly applied during the site assembly.
Seed TODOs should be preserved when the contentSource configuration does not allow AI drafting. The build process respects this constraint by keeping placeholder content intact rather than upgrading it to production copy automatically.
calebaeroOrchestrate the website-factory pipeline with validate, build, QA, and deploy phases.
gautam-lullaConvert Figma designs into Next.js websites with a headless CMS.
ExpeditoJAutomate UX/UI design tasks from research to quality assurance.
nielsmadanUpgrade Flutter SDK and project dependencies to specified stable versions.
