← ClaudeAtlas

vantage-messaginglisted

TRIGGER when the user wants to build or sharpen THEIR OWN positioning & messaging — "our positioning", "messaging house", "value proposition", "our one-liner", "homepage copy", "how should we position", "messaging framework", "what's our narrative". Part of the `vantage` (Vantage.os) Positioning Studio pack. Produces a positioning statement, messaging house, hero copy, and narrative. DO NOT trigger for analyzing a COMPETITOR's positioning (use vantage-positioning) or writing long-form content (use vantage-content-plan / copywriting).
macmenes/vantage · ★ 0 · AI & Automation · score 71
Install: claude install-skill macmenes/vantage
# Vantage — Positioning Studio (your messaging house) The "now what" after a competitive teardown: turn the white space you found into **your own** positioning and a complete messaging house. This is a *creation* skill — it builds the brand's strategic messaging, ideally informed by a prior Vantage competitive run (the white space, the shared clichés to avoid, the rivals' claims). Deliverable: **`MESSAGING-HOUSE.html`** (shared design system — `../vantage/references/html-report.md`; Vantage-purple accent permitted on this "build" deliverable). Working frameworks below. ## Intake (one question at a time — see the console rules in `../vantage/SKILL.md`) Ask each as its own message, waiting between each. Skip anything already known from a prior Vantage run or the user's input. 1. **"What's your brand or website?"** 2. **"In one breath, what do you sell and to whom?"** 3. **"Who's the ideal customer — and what do they use today instead of you?"** (the *competitive alternative*, incl. "do nothing / spreadsheets") 4. **"What can you do that the alternatives can't?"** (unique attributes) 5. **"What does that let the customer achieve?"** (the value/outcome) 6. **"Any non-negotiables?"** — words to own, words to avoid, tone (optional) If a competitive teardown exists, pull white space + rivals' one-liners + shared clichés from it instead of re-asking. ## Method ### 1. Positioning (Dunford "Obviously Awesome" sequence) Work in this order — positioning is *derived*, not declar