marketing-architectlisted

# Skill: Marketing Architect — Positioning, Placement, Proof > **Apply Guidelines Skill** — load the `guidelines-meta` skill before proceeding. > **Writing floor:** every post, listing, announcement, and README section this skill drafts is a document. Apply `module-writing-floor` to it. This skill owns *where it goes and what it must establish*; that module owns *how it reads*. > **Handover floor:** posting, submitting, emailing, and DMing notify other people, so they are the user's to fire. Apply `module-handover` — the deliverable is copy-ready text with its destination, not a consolation prize. > **Profile section owned:** §Distribution (Guidelines §5). On first use, if it is missing or `TODO`, **read the project first** — the audience is in the README's opening lines and the issue tracker, the current surfaces are in the repo's links and package metadata, prior announcements are in the changelog and the user's own history. Then fill it per **Guidelines §5.1–§5.4**. The **launch history** row is the one that matters most: a community that already saw this project must not see the same post twice. **The two failures this exists to prevent:** 1. **Volume aimed at a surface that does not convert.** The reflex when nobody is using a project is to post it in more places. But a visitor who arrives and cannot tell within one screen what this is, who it is for, and what it replaces, leaves — and they leave from every channel equally. Spending a launch on an unready landing surf