page-strategy
Page Strategy
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.
Inputs
Required:
workspace/brand/extract.mdor manual brief
Optional:
- source screenshots
- product images
- existing brand profile
- operator notes about page goal
More from themattberman/landing-page-factory
page-qa
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.
2page-visuals
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.
2page-copy
Write mechanism-preserving, proof-disciplined landing page copy from strategy, brand profile, and extract language bank. Includes mandatory sharpness audit and claim control.
2brand-profile
Build an evidence-backed brand profile from site extract and page strategy. Separates observed facts from synthesis so downstream skills preserve the brand instead of rewriting it.
2site-extract
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.
2page-build
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.
2