← ClaudeAtlas

content-site-structurelisted

Scaffold the content architecture of a multilingual content site — the `text/<lang>/`, `data/` and `media/` tree, the locale manifest, the Astro rendering engine, the fallback policy and the completeness validator. **Use this skill when — and only when — the user explicitly asks for it by name, or asks for the content-site structure or template** ("תפרוס את תבנית אתר התוכן", "בנה את מבנה אתר התוכן", "scaffold the content site", "set up the multilingual content structure"). It is NOT a baseline and NOT a default: do NOT load or apply it merely because a site or page is being built, because content is multilingual, or because a site could be restructured this way — `page-builder` plans pages without it. It does NOT restructure an existing site, and it is NOT for catalog-driven sites whose content already lives in key/value i18n JSON.
yybd/app-factory · ★ 5 · Data & Documents · score 77
Install: claude install-skill yybd/app-factory
# content-site-structure Lays down the content architecture of a **multilingual content site**: prose in Markdown per language, structured records in JSON, media in one place, an Astro engine that renders all three, and a validator that says when a language fell behind. It writes files. That is the whole point of it — and the reason it must never start on its own. ## Invocation — read this before anything else **This skill runs only when the user asked for it.** Not when a page is being built, not when a site happens to have two languages, not because an existing site looks like it would be better off this way. Before the first file is written, all four must hold: 1. **The user asked for this structure**, by name or by describing it. "Build me a landing page" is not an ask. "Set up the content-site structure" is. 2. **The target repo is empty of a site, or the user said explicitly to scaffold into this one.** Check first: an existing `index.html`, `_template.html`, `package.json` with a framework, or a populated `src/` means a site is already here. Say what you found and stop. 3. **The site is not catalog-driven.** If content prose already lives in key/value i18n JSON (`i18n/<lang>.json` with paragraph-length values), this skill is the wrong shape for it. Say so and stop — converting a live site's content model is a migration the owner decides on, not a scaffold. 4. **Astro is acceptable, or the user named another engine.** The engine here is Astro;