kiss-ssg

Verify that a kiss-ssg site builds cleanly without publishing the output, and read the resulting report. Use after writing or editing a kiss site's build script, models, controllers or views, before declaring a build done, and when asked to "check the site builds", "verify the kiss build", "verify the kiss-ssg build", or "why is this page missing".

Add a new page to a kiss-ssg site that is already set up, or update an existing page's content, model or controller. Use when asked to "add a page", "add a new page to the site", "add a blog post", "update this page", "change what's on this page", or when editing a `.hbs` view, a `.json` model or a controller in a project that already has `node_modules/kiss-ssg` installed. Not for scaffolding a brand-new site or adding a whole new section with its own model/controller pattern (use kiss-site-new for that), and not for a v1-to-v2 upgrade (use kiss-site-migrate).

Convert an existing web page into a structured kiss-ssg site — a Claude or ChatGPT artifact (often given as a link to the published artifact or share), a page that is already live, an exported page, a hand-written HTML file — keeping what it looks like while giving it a layout, partials and models. Use when someone arrives with a working page rather than a description, or asks to "turn my artifact into a real site", "convert this HTML to kiss", "make this page maintainable", "I built a site in Claude, now what", "here's the link to my artifact", "import an existing page", or "get this off a chat and onto a host". For a site described rather than supplied, use kiss-site-new; for moving a site across kiss-ssg versions, use kiss-site-migrate.

Upgrade a site built on kiss-ssg across any version boundary — a v1 to v2 migration, or a minor release that changed what a folder or a default means. Use when a project's build script targets an older kiss-ssg than the installed one, when an upgrade fails with an unhandled AggregateError or silently empty output, or when asked to "upgrade kiss", "migrate to kiss-ssg v2", "migrate kiss-ssg", "update kiss-ssg", or "why did my kiss site break after the upgrade".

Build a new static site with kiss-ssg from a description of what it should contain, or add a whole new section to an existing site (its own model, controller and view pattern). Use when scaffolding a kiss-ssg site from scratch, doing kiss-ssg initial setup, or when asked to "make a site with kiss", "set up kiss-ssg", "initialise a kiss-ssg site", or "write the build script for this site". For adding or updating a single page on a site that is already set up, use the kiss-page-add skill instead. If the person already HAS a working page — a Claude or ChatGPT artifact, an exported page, a hand-written HTML file — they want kiss-site-import, which keeps what it looks like rather than rebuilding it from a description.

Review a kiss-ssg site for launch readiness — read the build's launch-readiness audit, then look at the built pages in a browser — and report what is unfinished before fixing anything. Use when asked to "review the site", "is this site ready to launch", "is it ready to go live", "does this look finished", "run a launch checklist", "do a polish pass", "why does this look AI-generated", "why does this look templated", or when a kiss build passes but the site still looks rough. For a build that fails, use kiss-build-check first.