| name | message-system-architect |
| slug | aaron-message-system-architect |
| displayName | Message System Architect · 品牌消息体系 |
| summary | 品牌消息屋/主叙事/三支柱/标语·一句话的持久 canon |
| description | Use when the user asks to "author our durable brand message hierarchy", "build the brand message house that seeds the canon", or "define the main narrative, three pillars, and tagline for the whole brand"; produces the DURABLE brand message system — main narrative, three value pillars, per-persona proof points (each labeled Measured / User-provided / '[needs source]'), and the tagline/one-liner — that seeds the narrative-registry canon and from which every per-launch house derives. Not for a single launch's message house or PR-FAQ — use message-house-builder; not for claim adjudication — use offer-claims-registry; not for the change-narrative arc itself — use strategic-narrative-designer. 品牌消息屋/主叙事/三支柱/标语/持久叙事 canon |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when authoring the durable, brand-level message hierarchy that outlives any single launch: the main narrative, three value pillars each traceable to a positioning value theme, per-persona proof points, and the tagline/one-liner. The core of the TALE Architect phase and the seed of the narrative-registry canon — the per-launch message-house-builder is reused and derives from this durable house. Not the per-launch house itself and not claim substantiation. |
| argument-hint | <product / brand> [personas] [positioning truth set path] [narrative arc path] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"narrative","phase":"architect","geo-relevance":"low","hermes":{"tags":["marketing","narrative","architect"],"category":"narrative"},"openclaw":{"emoji":"📖","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Message System Architect
Authors the durable brand message hierarchy — the main narrative, three value pillars, per-persona proof points, and the tagline/one-liner — that outlives any single launch and seeds the narrative-registry canon. It is the anchor of the TALE Architect phase and the upstream of the A1 canon-integrity veto: the auditor judges canon exists and its hierarchy does not contradict itself against the record this skill proposes. It feeds several TALE-A sub-items directly — message house complete (tagline, one-liner, three value pillars, per-persona proof points), each pillar traces to a positioning value theme (no orphan pillar), and per-persona proof points each labeled Measured / User-provided / [needs source]. The per-launch message-house-builder is reused, not replaced — it derives its launch PR-FAQ from this durable house, and its output must not contradict the canon this skill seeds.
Scope guard: this skill authors the brand-level message system only. It does not build the per-launch message house or PR-FAQ (reuse message-house-builder — it reads the canon this seeds), design the old-world→new-game→promised-land change-narrative arc (strategic-narrative-designer owns the arc; this skill consumes it), codify brand voice, tone, or the naming tax (brand-language-codifier is the primary next step), write the canon of record (narrative-registry is the sole writer of memory/narrative-registry/ — this skill submits candidates only), adjudicate any product or comparative claim (unsubstantiated ones are marked [needs source] and submitted to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py; offer-claims-registry is the sole adjudicator), or compute the TALE profile result (only the gate scores TALE). It works one lever — the durable message hierarchy — and hands off.
