The four shipped skills
A fresh scaffold installs four Claude Code skills — content model, collections, custom modules, personalization — each loaded at its own moment.
Every scaffolded project ships the same four Claude Code skills under .claude/skills/, one file each, identical text regardless of whether the project runs coupled, headless, or decoupled. A skill loads itself automatically once its trigger matches what you're asking the agent to do.
The four, and when each one fires
kywi-content-model before building anything — design the model, get owner sign-off
kywi-collections adding any collection — folder + feed + Feed Display, end to end
kywi-custom-modules the built-in module palette falls short — defineModule, SSR/JS-off hazards
kywi-personalization the owner wants personalization or A/B — confirm the use case firstkywi-content-model is meant to fire before a build starts, not partway through one, which is why the build-order playbook makes it step 0 — though the skill frames itself as guidance rather than a hard gate: a one-page brochure site only needs a sentence of confirmation, not a full model document. The other three are narrower — each waits for the specific situation named in its trigger rather than firing on every prompt.
Where to look if a skill didn't fire
All four are plain files an agent's skill-loading mechanism reads from disk, so a skill that should have triggered and didn't is usually a missing or edited file, not a server-side setting. If the project wasn't scaffolded fresh — or the files were deleted or hand-edited since — see retrofitting an existing project for how to put them back.