creator-metalisted

# Creator Meta The portable substrate behind every creator-specific operating system. Defines the 6-layer model, the "where does X go?" decision tree, and the brand-discipline framework — abstractly, with placeholders, so any creator can inherit and specialize. `creator-meta` is to creator operating systems what `arcanea-meta` is to Arcanea or `frankx-meta` is to FrankX: the self-describing layer that makes the system bootable. ## When to use this skill - Designing a new creator's Claude Code project structure (any creator, not just Frank) - Asking "where should this live?" in any creator-tooling context - Booting a fresh creator project with the proven layer model - Comparing two creator setups for drift or convention divergence - Generalizing a project-scope skill (like `frankx-meta`) into a portable plugin - Reasoning about creator-tooling architecture independent of specific paths or brand ## When NOT to use this skill - When you have a specific creator-meta child available (e.g., `frankx-meta`) — use that instead, it has concrete paths - For domain work (writing code, content, music) — use the domain-specific skill - For ACOS-internal questions — use `acos-meta` instead ## The 6-layer model (abstract) ``` L0 RAW INTAKE {creator}/intake/ inbound, unprocessed L1 SECOND BRAIN {creator}/docs/ long-form prose L2 COMMAND CENTER {creator}/.claude/ skills, commands, agents, hooks L3 OPERAT