website-positioninglisted
Install: claude install-skill karero/website-builder
# Website positioning
Owns the **what you offer, for whom, and in what category** layer — the spine the
whole site hangs off. It is worked out **first**, before SEO keywords and before a
word of page copy: positioning decides what the copy is even trying to say.
`website-content-guide` (voice + EEAT) and everything downstream **read** this; they
do not redefine it.
The five-component framework is **domain-agnostic** — it positions any kind of site (a
SaaS product, a local service business, a consultancy, a personal portfolio, a nonprofit,
an event, a community). Only the answers change, never the components; the tech-comparison
example below is just the clearest case for the per-surface map form, not the expected
subject matter.
## Outputs
- **`POSITIONING.md`** (from `~/.claude/skills/new-website/templates/positioning.md`)
— the five Dunford components, a one-paragraph positioning statement, reusable
boilerplate, and the **per-page positioning spine** (one term per page).
- The **`POSITIONING` map** in `tests/positioning.spec.ts` — the same spine, in
code, that hard-enforces each page carries its term.
## How to use
1. **Pull insights first.** Run `customer-research` for the real ICP, jobs-to-be-done
and voice-of-customer, and `competitor-alternatives` (or a quick scan) for what
customers use today. Positioning is grounded in those facts, not invented.
2. **Fill the five components** in `POSITIONING.md` (the Dunford framework):
1. **Competitive alternati