landing-page-factory-orchestrator
Landing Page Factory Orchestrator
This is the control layer.
Use this skill when the request is about:
- building a full landing page pipeline
- creating one or more page variants
- rerunning selected stages after edits
- figuring out the right order of operations
- admin tasks around page package naming, artifact checks, cleanup, or memory logging
Do not replace the stage skills. This skill routes and supervises them.
What this skill owns
- request classification
- stage ordering
- artifact preflight checks
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-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.
2