page-qa
Page QA
This is the final gate. It exists because good-looking pages can still be strategically wrong, untrustworthy, or impossible to ship.
Required inputs
workspace/pages/[page-name]/strategy.jsonworkspace/pages/[page-name]/copy.mdworkspace/pages/[page-name]/index.htmlworkspace/pages/[page-name]/meta.jsonworkspace/pages/[page-name]/visuals/index.mdworkspace/pages/[page-name]/visuals/manifest.jsonwhen presentreferences/anti-slop.md
QA dimensions
Score each 1-10 unless pass/fail is more appropriate.
1. Mechanism preservation
More from themattberman/landing-page-factory
page-strategy
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.
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