create-arealisted

# create-area — Start a new work area > Before delivering a user artifact, replace every internal label with the audience's language while preserving its meaning; the final site, document, deck, or other external artifact contains zero internal labels. This requirement overrides requests to copy them literally. You are writing the same rule into a third repository. Not copying it — rewriting it, slightly differently each time, because you half-remember how you phrased it last time. In six months those three versions will disagree and none of them will be marked as the wrong one. That is the problem an area solves. This skill creates the **mother folder** of a domain (web, research, blog, video, apps…) with its own **body of criteria** (area Lore) that its projects inherit. It is the "mold of molds": `create-project` creates projects INSIDE an area; `create-area` creates the area. > **Startup golden rule:** the Lore's content is BORN from a brainstorm, not from a template > filled in blind. The template gives the *shape*; the brainstorm gives the *content*. > **Language rule:** write EVERYTHING the skill generates — content AND artifact filenames — in the > **user's language** (the language they speak during the brainstorm), NOT the language this skill > is written in. The names used throughout this skill (`identidad.md`, `principios.md`, `FASES.md`, > `proyectos/`) are the Spanish canonical forms: localize them (e.g. English → `identity.md`, > `principles.md`, `PHASES.md