| name | artifact-landing-page |
| description | Use when asked to build a campaign landing page. Generates a 7-section wireframe with copy, a design-generation prompt for a visual mockup, and optionally deploy-ready HTML, from the messaging canon and visual identity. |
Artifact: Landing Page
Generates a campaign landing page draft from approved context: a 7-section wireframe with
copy, a design-generation prompt for the visual mockup, and (when asked) deploy-ready
single-file HTML with embedded CSS. A human reviews it before it ships.
Reads from context
From the canon, by component ID:
positioning, value-proposition: the hero and value sectionsicp (the champion's job to be done): the problem section, in the customer's wordsunique-attributes, how-it-works: the solution bridgecustomer-proof, key-metrics: the social proof section- the objections in
icp and buying-committee: the objection-handler / FAQ section; answer the real objections the canon records, directly, not in marketing-speak
offers: the conversion offer, when a trial or free tier is the destinationbuying-committee: who the page is qualifying for
And the full visual identity for both outputs, plus
brand-writing-identity for voice, guardrails, and lexicon.
If a section's component has no canon entry, mark the section as a gap. Never invent proof,
objections, or claims.
Asks the human
One at a time, and only what context cannot hold:
- Conversion goal. Demo request, free trial, content download, or webinar registration? This selects the hero formula.
- The offer. What exactly does the visitor get?
- Traffic source. Paid clicks, organic, or outbound links? This sets how much context the hero must carry.
- Output. Wireframe plus visual mockup prompt, deploy-ready HTML, or both?
- Form fields. Which fields are non-negotiable for sales? Default to the minimum; every field costs conversion.
Workflow
- Read the canon components and visual identity listed above. Note any gaps.
- Ask the five questions.
- Pick the hero formula by goal (see landing-page-patterns.md) and draft the 7 sections, each doing its one job, copy from canon language.
- Present the wireframe with copy per section.
- Build the requested outputs: the design-generation prompt with visual identity inlined, and/or the single-file HTML (semantic markup, mobile-first, no external dependencies beyond fonts).
- Run the checklist.
Checklist
- Hero answers "am I in the right place" in 3 seconds; clear before clever
- One primary CTA above the fold; at most one secondary
- The FAQ answers the objections the canon records directly
- Proof is specific: named customers or quantified outcomes, no "trusted by leading companies"
- Form asks only the agreed fields
- Mobile: H1 readable at 375px, CTA tappable at 44x44px minimum and above the fold, fields stacked
- All copy comes from canon language; nothing invented
- HTML output (if any) is a single file, renders above-the-fold content fast, no hero video
