name: website-template-factory
description: Use this skill when scaffolding or customizing a frontend website for a new tenant. The frontend lives in /website and is the Vercel-deployable template. Trigger when: creating a new client site, customizing copy or branding for a tenant, deploying a site to Vercel, or making path-safe changes to the website template.
Website Template Factory
Role
The website factory produces per-tenant frontend deployments from the base template in /website. Each tenant gets a customized copy of the template — copy, colors, domain, and business-specific sections change. The underlying structure and build pipeline do not.
What Changes Per Tenant
- Page copy (hero text, CTA, about, services)
- Brand colors in
_static/style.css (CSS variables only)
- Business metadata (title, description, domain)
- Logo and hero image in
_static/
- Locale strings in
locales/
What Never Changes
- Build pipeline (
build.py, Makefile, vercel.json)
- Template structure (
_templates/page.html)
- Routing and page names
- Backend integration pattern (always via Pi API)
Scaffold Command
factoryctl website scaffold \
--tenant <slug> \
--output-dir ./deployments \
--copy path/to/copy.yaml \
--domain client.com
Deploy Command
factoryctl website deploy \
--tenant <slug> \
--vercel-project-id <id> \
--vercel-org-id <id>
Rules
- Do not fork the entire stack per client.
- Do not add agent logic to the frontend.
- Do not commit client secrets.
- Output goes to a
deployments/<slug>/ directory, not to /website itself.
