product-communicationslisted
Install: claude install-skill SandRiseStudio/musterd
# product-communications
This skill teaches craft, not message. The message lives in the authoritative
sources below; if anything in this file appears to disagree with them, they win
and this file has a bug — fix it with a PR, do not follow it.
## Authoritative sources (read before writing anything public)
1. `docs/design/brand.md` — voice and tone (§4), terminology glossary (§5),
marks and color (§1–§3, ADR 154). The glossary's five terms — Team, Member,
Presence, Surface, Act — are load-bearing and must be used with their exact
meanings; never introduce synonyms ("room", "user", "session", "platform",
"event"). ADR 296 makes the glossary a generated, gated artifact — treat
drift as a build failure, not a style preference.
2. `PRODUCT.md` — register, users, product purpose, brand personality
(engineered, luminous, quiet-confident), anti-references.
3. `SPEC.md` — the normative definitions behind the glossary.
4. `docs/wiki/positioning.md` + `docs/design/landscape.md` — brand
architecture (SandRise Studio is maker, never product brand) and the
competitive line (coordination of independent actors, not intra-task
orchestration; "Band connects your agents; musterd makes them a team").
**The positioning decision is not yours.** It is made in the positioning ADR;
you execute the decided message and keep every surface telling the same story.
Until that ADR lands, treat `docs/wiki/positioning.md` as current direction and
flag — don't resolve — any tens