// Normalize raw extract or manual brief into a page strategy artifact: mechanism, offer, audience, proof provenance, CTA, preservation plan, and review flags. Mandatory before copy or build.
| name | page-strategy |
| description | Normalize raw extract or manual brief into a page strategy artifact: mechanism, offer, audience, proof provenance, CTA, preservation plan, and review flags. Mandatory before copy or build. |
| metadata | {"openclaw":{"emoji":"🧭","user-invocable":true,"requires":{"env":[]}}} |
This is the missing operator layer.
site-extract collects facts.
page-strategy decides what must be preserved, what can change, what proof is safe to use, and what page type should be built.
No strategy artifact, no page.
Required:
workspace/brand/extract.md or manual briefOptional:
Write both:
workspace/pages/[page-name]/strategy.mdworkspace/pages/[page-name]/strategy.json# Page Strategy: [page-name]
Brand:
Page type:
Built:
Confidence:
## 1. Core decision
- Product / service:
- Offer:
- Audience:
- Awareness stage:
- CTA action:
- CTA destination:
- Conversion goal:
## 2. Mechanism map
- Primary buyer job:
- Primary pain:
- Failed alternatives:
- Unique mechanism:
- Why the mechanism works:
- What must be shown visually:
- What must be explained verbally:
## 3. Claims control
### Allowed claims
- [claim] — provenance class
### Forbidden claims
- [claim]
### Claims requiring proof near them
- [claim]
## 4. Proof plan
| Proof item | Class | Provenance | Where it should appear | Shippable? |
|---|---|---|---|---|
## 5. Preservation plan
### Trust cues to preserve
-
### Visual conventions to preserve
-
### Language to preserve
- exact phrases
- category terms buyers expect
- differentiators in source wording
### Deviations allowed
- what can be improved safely
## 6. Page routing
- Recommended page type:
- Hero structure:
- Proof structure:
- CTA strategy:
- Objection strategy:
- Required sections:
- Optional sections:
## 7. Visual requirements
- Visual preservation class: exact product / branded environment / concept support
- Screenshot handling: required / optional / forbidden
- Packaging fidelity needed? yes/no
- UI fidelity needed? yes/no
- Product silhouette fidelity needed? yes/no
## 8. Review flags
- compliance-sensitive claims
- thin proof
- missing CTA destination
- visual asset gaps
- any human approval needed
Use these branches, not vibes.
Use product-led route when:
Hero must include:
Use screenshot-led route when:
Hero must include:
Use friction-managed route when:
Above fold must include:
Use compliance-limited route when:
Rules:
Stop if:
Continue with downgrade if:
Downstream order:
/brand-profile/page-copy/page-visuals/page-buildEvery downstream skill must read strategy.json first, then other artifacts.
Top-level operator skill for Landing Page Factory. Classifies requests, chooses stage order, enforces prerequisites and hard stops, manages variant pages, reruns changed stages, and handles page-package admin.
Build a deployable landing page from strategy, copy, visuals, and brand profile using category-aware routing, preservation hierarchy, and explicit QA. Single-file HTML output.
Final landing-page QA pass against strategy, proof provenance, mechanism clarity, trust preservation, accessibility, and anti-slop. Gates whether a page is shippable or draft-only.
Plan and generate visuals by preservation class: exact product, branded environment, or concept support. Uses strategy-driven shot selection and visual QA instead of generic vibe prompting.
Extract operator-grade source facts from a website or manual brief: claims, proof, CTAs, mechanism language, trust cues, visual patterns, and page structure with provenance. First stage of Page Factory.
Write mechanism-preserving, proof-disciplined landing page copy from strategy, brand profile, and extract language bank. Includes mandatory sharpness audit and claim control.